* chore: update AlphaHuman version to 0.49.3 and configure updater plugin in tauri.conf.json - Bumped the AlphaHuman package version in Cargo.lock to 0.49.3. - Added updater configuration in tauri.conf.json to enable automatic updates with specified endpoints. * refactor: rename AlphaHuman to OpenHuman across the codebase - Updated all instances of "AlphaHuman" to "OpenHuman" in comments, tooltips, and constants to reflect the new branding. - Adjusted relevant documentation and prompts to ensure consistency with the new name. * refactor: update documentation and configurations to reflect OpenHuman branding - Replaced all instances of "AlphaHuman" with "OpenHuman" in documentation, comments, and configuration files to ensure consistency with the new branding. - Updated deep link URLs and related authentication flows to use the new "openhuman://" scheme. - Adjusted paths and references in the skills system and other related files to align with the new project name.te * refactor: standardize OpenHuman references and update configurations - Replaced all instances of "AlphaHuman" with "OpenHuman" across documentation, comments, and configuration files to maintain branding consistency. - Updated URLs and paths to reflect the new "openhuman://" scheme. - Adjusted environment variable names and related settings to align with the new project identity. - Enhanced documentation for clarity and accuracy regarding the OpenHuman framework.r * chore: update subproject commit reference in skills directory * refactor: update backend URL to reflect new service domain - Changed default backend URL from "https://api.openhuman.xyz" to "https://api.tinyhumans.ai" in both JavaScript and Rust configuration files. - Ensured consistency across the codebase regarding the new backend service endpoint. * feat: introduce identity and migration modules for OpenHuman - Added a new identity module to support AIEOS v1.1 JSON format, including structures for identity, psychology, linguistics, motivations, capabilities, physicality, history, and interests. - Implemented a migration module to facilitate data migration from OpenClaw memory, including SQLite and Markdown sources, with detailed reporting on migration statistics and warnings. - Established utility functions for handling multimodal content and image processing within the OpenHuman framework. - Enhanced the agent system with new dispatcher and classifier functionalities to improve tool management and message classification. * chore: remove Android project files and configurations - Deleted various Android project files including .editorconfig, .gitignore, build.gradle.kts, gradle.properties, and others to clean up the project structure. - Removed all related resources, layouts, and source files from the Android app directory to streamline the codebase. - This cleanup is part of a larger effort to refactor and simplify the project structure. * refactor: update login flow and remove Telegram integration - Removed the TelegramLoginButton component and its references from the OAuthLoginSection, streamlining the login options. - Updated the AppRoutes to remove the login route, reflecting changes in the authentication flow. - Enhanced the RotatingTetrahedronCanvas component with improved geometry and lighting effects for better visual presentation. - Adjusted the TypewriterGreeting component's styling for consistency. - Cleaned up the Welcome page to integrate the OAuthLoginSection directly, improving user experience. * chore: update subproject commit reference in skills directory * chore: update test configurations and improve test assertions - Modified test scripts in package.json to use a specific Vitest configuration file for consistency. - Updated assertions in loader tests to ensure loading durations are non-negative. - Enhanced tool loading tests to clarify expected behavior regarding localStorage and cache management. - Adjusted agent tool registry tests to improve error handling and ensure accurate statistics. - Refined device detection tests to reflect updated fallback URLs. * fix: enhance parameter formatting and remove unused components - Updated the `formatParameters` function to handle cases where schema properties are empty, returning a more informative response. - Deleted the `DownloadScreen` component and associated device detection utilities to streamline the codebase and remove unused functionality. - Adjusted tests to reflect changes in the tool loading and agent tool registry, ensuring accuracy in assertions. * chore: simplify Vitest configuration by removing unused include patterns - Updated the Vitest configuration to remove unnecessary test file patterns, streamlining the test setup for better clarity and maintainability. * refactor: update paths and comments for AI configuration and file watching - Modified Vite configuration to ignore only the `src-tauri` directory. - Updated logging messages to reflect the correct path for writing AI configuration files. - Adjusted fetch calls in the file watcher to use the new path for `TOOLS.md`. - Revised comments and logic in Rust code to clarify the handling of AI configuration file paths, including legacy fallback options. * chore: remove unused updater secrets from GitHub Actions workflow - Deleted UPDATER_GIST_URL and UPDATER_GIST_ID environment variables from the package-and-publish workflow, streamlining the configuration. * chore: comment out Vitest thresholds for clarity - Commented out the thresholds section in the Vitest configuration to improve clarity and maintainability, as it is currently not in use. * ran formatter * chore: update updater public key in tauri configuration - Replaced the existing public key in the updater plugin configuration with a new value to ensure proper functionality and security. * chore: update ESLint configuration and refactor components - Added `localStorage` and `sessionStorage` as readonly globals in ESLint configuration for better linting support. - Removed unused imports from `SkillsPanel.tsx` to clean up the code. - Changed the type of `watcherInterval` in `file-watcher.ts` for improved type safety. - Refactored toast management logic in `Intelligence.tsx` to enhance clarity and maintainability. - Simplified import statements in `IntelligenceProvider.tsx` for consistency. - Streamlined object property shorthand in `agentToolRegistry.ts` for cleaner code. * refactor: improve error handling and type safety in Intelligence component - Enhanced toast notification logic to defer state updates, preventing potential issues with setState in effects. - Updated the source filter dispatch to use a more specific type for improved type safety. * refactor: enhance type safety across various components and services - Updated type definitions from `any` to `unknown` in multiple files to improve type safety and prevent potential runtime errors. - Refactored state management in `TauriCommandsPanel` to use more specific types. - Adjusted context and parameters in several interfaces to ensure consistent typing. - Added ESLint directive to `polyfills.ts` for intentional global assignments. - Streamlined type handling in utility functions and API responses for better clarity and maintainability. * refactor: streamline import statements and improve code clarity - Consolidated import statements in `agentToolRegistry.ts` and `intelligenceSlice.ts` for better readability. - Simplified the `createTestStore` function in `test-utils.tsx` to enhance code conciseness. - Cleaned up the `isExecutionStepProgressEvent` function in `intelligence-chat-api.ts` for improved clarity and maintainability.
8.4 KiB
OpenHuman Tools
This document lists all available tools that OpenHuman can use to interact with external services and perform actions. Tools are organized by integration and automatically updated when the app loads.
Architecture note: All read/query operations (get-page, list-*, query-database, search, etc.) are handled by the memory layer — data is fetched from the TinyHumans Neocortex memory system and injected into context automatically. Only write, create, update, delete, and trigger operations are exposed as tools.
Overview
OpenHuman has access to 12 tools across 1 integrations.
Quick Statistics:
- Notion: 12 tools
Available Tools
Notion Tools
This skill provides 12 tools for notion integration. Data retrieval is handled by the memory layer, not tools.
append-blocks
Description: Append child blocks to a page or block. Supports various block types.
Parameters:
- block_id (string) (required): The parent page or block ID
- blocks (string) (required): JSON string of blocks array. Example: [{"type":"paragraph","paragraph":{"rich_text":[{"text":{"content":"Hello"}}]}}]
Usage Context: Available in all environments
Example:
{
"tool": "append-blocks",
"parameters": { "block_id": "example_block_id", "blocks": "example_blocks" }
}
append-text
Description: Append text content to a page or block. Use the page id (or block_id) from memory context. Creates paragraph blocks with the given text.
Parameters:
- block_id (string): The page or block ID to append to (use page id from memory context)
- content (string): Alias for text — the content to append to the page
- page_id (string): Alias for block_id when appending to a page (same as block_id)
- text (string) (required): The text to append (required). Pass the exact content to add to the page.
Usage Context: Available in all environments
Example:
{
"tool": "append-text",
"parameters": {
"block_id": "example_block_id",
"content": "example_content",
"page_id": "example_page_id",
"text": "example_text"
}
}
create-comment
Description: Create a comment on a page or block, or reply to a discussion. Provide either page_id (new comment on page) or discussion_id (reply). Requires Notion integration to have insert comment capability.
Parameters:
- block_id (string): Block ID to comment on (optional, use instead of page_id)
- discussion_id (string): Discussion ID to reply to an existing thread (use instead of page_id)
- page_id (string): Page ID to create a comment on (new discussion)
- text (string) (required): Comment text content
Usage Context: Available in all environments
Example:
{
"tool": "create-comment",
"parameters": {
"block_id": "example_block_id",
"discussion_id": "example_discussion_id",
"page_id": "example_page_id",
"text": "example_text"
}
}
create-database
Description: Create a new database in Notion. Specify parent page_id and title. Optionally provide properties schema as JSON.
Parameters:
- parent_page_id (string) (required): Parent page ID where the database will be created
- properties (string): JSON string of properties schema. Example: {"Name":{"title":{}},"Status":{"select":{"options":[{"name":"Todo"},{"name":"Done"}]}}}
- title (string) (required): Database title
Usage Context: Available in all environments
Example:
{
"tool": "create-database",
"parameters": {
"parent_page_id": "example_parent_page_id",
"properties": "example_properties",
"title": "example_title"
}
}
create-page
Description: Create a new page in Notion. Parent can be another page or a database. For database parents, properties must match the database schema.
Parameters:
- content (string): Initial text content (creates a paragraph block)
- parent_id (string) (required): Parent page ID or database ID
- parent_type (string): Type of parent (default: page_id)
- properties (string): JSON string of additional properties (for database pages)
- title (string) (required): Page title
Usage Context: Available in all environments
Example:
{
"tool": "create-page",
"parameters": {
"content": "example_content",
"parent_id": "example_parent_id",
"parent_type": "example_parent_type",
"properties": "example_properties",
"title": "example_title"
}
}
delete-block
Description: Delete a block. Permanently removes the block from Notion.
Parameters:
- block_id (string) (required): The block ID to delete
Usage Context: Available in all environments
Example:
{ "tool": "delete-block", "parameters": { "block_id": "example_block_id" } }
delete-page
Description: Delete (archive) a page. Archived pages can be restored from Notion's trash.
Parameters:
- page_id (string) (required): The page ID to delete/archive
Usage Context: Available in all environments
Example:
{ "tool": "delete-page", "parameters": { "page_id": "example_page_id" } }
summarize-pages
Description: AI summarization of Notion pages is now handled by the backend server. Synced page content is submitted to the server which runs summarization.
Parameters: None
Usage Context: Available in all environments
Example:
{ "tool": "summarize-pages", "parameters": {} }
sync-now
Description: Trigger an immediate Notion sync to refresh local data. Returns sync results including counts of synced pages and databases.
Parameters: None
Usage Context: Available in all environments
Example:
{ "tool": "sync-now", "parameters": {} }
update-block
Description: Update a block's content. The structure depends on the block type.
Parameters:
- archived (string): Set to true to archive the block
- block_id (string) (required): The block ID to update
- content (string): JSON string of the block type content. Example for paragraph: {"paragraph":{"rich_text":[{"text":{"content":"Updated text"}}]}}
Usage Context: Available in all environments
Example:
{
"tool": "update-block",
"parameters": {
"archived": "example_archived",
"block_id": "example_block_id",
"content": "example_content"
}
}
update-database
Description: Update a database's title or properties schema.
Parameters:
- database_id (string) (required): The database ID to update
- properties (string): JSON string of properties to add or update
- title (string): New title (optional)
Usage Context: Available in all environments
Example:
{
"tool": "update-database",
"parameters": {
"database_id": "example_database_id",
"properties": "example_properties",
"title": "example_title"
}
}
update-page
Description: Update a page's properties. Can update title and other properties. Use append-text to add content blocks.
Parameters:
- archived (string): Set to true to archive the page
- page_id (string) (required): The page ID to update
- properties (string): JSON string of properties to update
- title (string): New title (optional)
Usage Context: Available in all environments
Example:
{
"tool": "update-page",
"parameters": {
"archived": "example_archived",
"page_id": "example_page_id",
"properties": "example_properties",
"title": "example_title"
}
}
Tool Usage Guidelines
Authentication
- All tools require proper authentication setup through the Skills system
- OAuth credentials are managed securely and refreshed automatically
- API keys are stored encrypted in the application keychain
Rate Limiting
- Tools automatically respect API rate limits of external services
- Intelligent retry logic handles temporary failures with exponential backoff
Error Handling
- All tools return structured error responses with detailed information
- Network failures trigger automatic retry with configurable attempts
Tool Statistics
- Total Tools: 12
- Active Skills: 1
- Read/Query Tools: 0 (handled by memory layer)
- Last Updated: 2026-03-26
This file was automatically generated when the app loaded. Tools are discovered from the running V8 skills runtime.