mirror of
https://github.com/tinyhumansai/openhuman.git
synced 2026-07-30 15:03:57 +00:00
Steven EnamakelandGitHub
bfaabd3b86
* 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.
4.9 KiB
4.9 KiB
OpenHuman Curated Knowledge
Platform Capabilities
OpenHuman is a cross-platform crypto community platform built with Tauri (React + Rust). It runs on Windows, macOS, Android, and iOS.
Core features:
- AI-powered chat with tool execution (skills system)
- Notion integration for workspace and knowledge management
- Gmail integration for email management and drafting
- Slack integration for team messaging
- Google Calendar integration for scheduling
- Google Drive integration for file management
- GitHub integration for repository access and code operations
- Wallet integration for on-chain interactions
- Real-time communication via Socket.io
- V8-based skill execution engine for extensible automation
- MCP (Model Context Protocol) for AI-driven tool interactions
Available integrations:
- Notion (pages, databases, blocks, search)
- Gmail (read, compose, reply, manage labels)
- Slack (send messages, read channels, manage conversations)
- Google Calendar (events, scheduling, reminders)
- Google Drive (files, folders, sharing)
- GitHub (repositories, issues, pull requests, code search)
- Wallet (on-chain operations with security boundaries)
Crypto Domain Knowledge
Key Terminology
- DeFi: Decentralized Finance — financial services built on blockchain without intermediaries
- TVL: Total Value Locked — the total capital deposited in a DeFi protocol
- APY/APR: Annual Percentage Yield/Rate — yield metrics for DeFi positions
- Gas: Transaction fees on blockchain networks (especially Ethereum)
- MEV: Maximal Extractable Value — profit extracted by reordering/inserting transactions
- Rug pull: A scam where developers abandon a project and take investor funds
- DYOR: Do Your Own Research — standard disclaimer in crypto
- Alpha: Non-public or early information that provides a trading advantage
- Degen: A user who takes high-risk positions, often in new or unaudited protocols
- Whale: An entity holding large amounts of a cryptocurrency
Market Mechanics
- Crypto markets trade 24/7/365 — there is no market close
- Token prices are determined by supply/demand across decentralized and centralized exchanges
- Liquidity varies dramatically between assets — top 20 tokens vs. long-tail tokens
- Regulatory landscape changes frequently and varies by jurisdiction
- On-chain data is public and verifiable — a key difference from traditional finance
Common User Workflows
- Morning briefing: Check overnight market moves, scan inbox for updates, review calendar
- Research flow: Find a token/protocol → check on-chain metrics → read community sentiment → assess risk
- Communication flow: Draft updates for teams → send across Gmail/Slack → track responses
- Automation flow: Set up price alerts → configure scheduled messages → automate portfolio tracking
- Organization flow: Capture notes in Notion → file documents in Google Drive → schedule follow-ups in Calendar
Integration Quirks
Notion
- API rate limits: 3 requests per second for most endpoints
- Page content is block-based — each paragraph, heading, list item is a separate block
- Database queries support filtering, sorting, and pagination
- Rich text content uses an array of text objects with annotations (bold, italic, etc.)
- Parent-child relationships: pages can contain sub-pages and databases
Gmail
- Uses OAuth2 for authentication — tokens need periodic refresh
- Labels are the primary organizational mechanism (not folders)
- Thread-based conversation model — replies are grouped automatically
- Rate limits apply to both read and send operations
- HTML email formatting requires careful sanitization
Slack
- Channel-based messaging — each workspace has multiple channels
- Thread replies vs. channel messages are distinct concepts
- Bot tokens have different permissions than user tokens
- Rate limits vary by API method (typically 1-50 requests per minute)
- Rich message formatting uses Block Kit
Google Calendar
- Events can have multiple attendees with RSVP status
- Recurring events use RRULE format
- Timezone handling is critical — always confirm user timezone
- Free/busy information can be queried across calendars
GitHub
- Rate limits: 5,000 requests per hour for authenticated requests
- Repository content access requires appropriate permissions
- Issues and PRs are separate entities but share a numbering space
- Webhook events can trigger automated workflows
Best Practices
- Always cite sources when sharing market data or news — users need to verify
- Timestamp sensitive information — crypto moves fast, yesterday's data may be irrelevant
- Respect rate limits on all integrations — batch operations when possible
- Handle errors gracefully — network issues and API failures are common in crypto infrastructure
- Default to caution with financial topics — frame analysis as information, not advice