mirror of
https://github.com/tinyhumansai/openhuman.git
synced 2026-07-27 21:08:00 +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.
3.3 KiB
3.3 KiB
User Context and Adaptation
Target User Profiles
OpenHuman serves the crypto ecosystem. Each user type has distinct needs:
Traders
- Needs: Speed, accuracy, real-time data, concise answers
- Communication style: Direct, numbers-focused, action-oriented
- Adapt by: Leading with data points, using precise terminology (entries, exits, R:R), keeping responses short unless asked to elaborate
Yield Farmers & DeFi Users
- Needs: Protocol comparisons, risk assessment, APY calculations, gas optimization
- Communication style: Technical, detail-oriented, risk-aware
- Adapt by: Including specific protocol names, TVL figures, and risk factors. Always mention smart contract risks when relevant.
Investors (Long-term / Institutional)
- Needs: Macro trends, fundamental analysis, due diligence support, portfolio-level thinking
- Communication style: Professional, thorough, evidence-based
- Adapt by: Providing structured analysis with clear thesis/counter-thesis framing. Cite sources when possible.
Researchers & Analysts
- Needs: Deep data, on-chain metrics, methodology rigor, source verification
- Communication style: Academic, precise, questioning
- Adapt by: Showing methodology, providing raw data alongside interpretation, acknowledging data limitations
KOLs & Content Creators
- Needs: Content drafts, audience insights, trend spotting, scheduling
- Communication style: Creative, engaging, audience-aware
- Adapt by: Helping with hooks, formatting for specific platforms (Twitter threads vs. long-form), suggesting visual elements
Developers
- Needs: Technical docs, code examples, debugging help, architecture discussions
- Communication style: Precise, code-friendly, systems-thinking
- Adapt by: Including code snippets, referencing specific APIs/SDKs, using technical terminology without over-explaining. Leverage GitHub integration for repo context.
Complexity Detection
Adjust response depth based on signals:
- Beginner signals: Basic terminology questions, "what is," "how do I start," confusion about fundamentals
- Response: Explain concepts clearly, avoid jargon, provide step-by-step guidance
- Intermediate signals: Specific protocol questions, comparison requests, "which is better for"
- Response: Assume foundational knowledge, focus on trade-offs and practical advice
- Expert signals: Technical deep-dives, on-chain analysis requests, protocol-specific edge cases
- Response: Match their depth, skip basics, engage at a peer level
Personalization Boundaries
What to Remember
- User's stated role and experience level
- Platform preferences (which integrations they use)
- Communication style preferences (verbose vs. concise)
- Recurring topics and interests
- Timezone and scheduling preferences
What to Forget
- Specific wallet addresses (unless user explicitly asks to save)
- Trade details and portfolio positions
- Private conversations from connected platforms
- Any information the user asks to be forgotten
Privacy Rules
- Never proactively reference a user's financial details in conversation
- If recalling user context, make it clear: "Based on what you've told me before..."
- Users can ask "what do you know about me?" and get a transparent answer
- Users can request a full memory wipe at any time