- Modified build.yml to trigger on changes in 'src/**' and 'src-tauri/**' paths.
- Standardized quotes in package-and-publish.yml for consistency.
- Updated README.md and SUMMARY.md to reflect new branding and added new sections for platform and privacy.
- Introduced new documentation files for platform availability and privacy/security features.
- Renamed all instances of "AlphaHuman" to "OpenHuman" in various components, pages, and files.
- Updated links and email addresses to reflect the new OpenHuman branding.
- Ensured consistency in messaging and branding throughout the application.
- Updated all instances of "AlphaHuman" to "OpenHuman" in README.md, SUMMARY.md, and various overview documents.
- Adjusted links and references to the new GitHub repository for OpenHuman.
- Ensured consistency in branding and messaging throughout the documentation.
- Fixed the spelling of "reminisces" in the README.md file.
- Updated Node.js version from 20 to 24 in the GitHub Actions workflow for lander pages.
- Changed yarn install command to use --non-interactive for smoother CI execution.
- Deleted obsolete .mcp.json file.
- Updated ESLint and test configurations to reflect new file paths.
- Changed title and branding in index.html and README.md to OpenHuman.
- Adjusted package.json scripts for testing with new configuration files.
- Modified E2E test scripts to use updated WebDriverIO configuration paths.
- Added new TypeScript configuration files for E2E testing and Vitest.
- Added .gitignore to exclude unnecessary files and directories.
- Created ESLint configuration for code quality enforcement.
- Set up Next.js configuration file for project settings.
- Established package.json with dependencies for React, Next.js, and TypeScript.
- Configured PostCSS for Tailwind CSS integration.
- Developed foundational components including layout, global styles, and animated backgrounds.
- Implemented feedback system components for user interaction and feedback management.
- Added README for project documentation and setup instructions.
- Added .gitignore to exclude unnecessary files and directories.
- Created ESLint configuration for code quality and consistency.
- Set up Next.js configuration file for project settings.
- Initialized package.json with dependencies and scripts for development.
- Configured PostCSS for Tailwind CSS integration.
- Added global styles and layout components for the landing page.
- Implemented core components including AnimatedBackground, AnimatedLogo, and Feedback features.
- Established feedback management system with modals and kanban board for user interactions.
- Included README for project setup and usage instructions.
- Documented tasks including skill downloads, JSON-RPC state management, and custom MCP server integration.
- Outlined payment flow integration and various skill enhancements.
- Added checklist for upcoming Android version and background processes.
- Updated `gmailSlice` to replace `GmailEmailSummary` with `GmailEmailBatch`, enhancing email data structure.
- Modified `SkillProvider` to dispatch emails as `GmailEmailBatch | null`.
- Improved HTTP client management in `ops_net.rs` by implementing a shared client for fetch calls, optimizing connection handling and timeout management.
- Enhanced deep link handling in `desktopDeepLinkListener.ts` to trigger synchronization after OAuth completion.
Updated function and parameter formatting for better readability and maintainability. Improved documentation clarity in `TOOLS.md` and ensured code consistency across files by aligning indentation and syntax styles.
- Add clearAllSkillsData() method to SkillManager for comprehensive data clearing
- Enhance nuclear reset to clear both frontend state and skills databases
- Update confirmation modal with detailed warning about data being deleted:
• App settings and conversations
• Email data from Gmail
• Chat history from Telegram
• Cached files from Notion
• All other skills data
- Improve loading feedback: "Clearing All Data..." during operation
- Update button text to "Log Out & Clear Everything" for clarity
- Add graceful error handling for skills clearing with fallback to basic reset
- Import skillManager in SettingsHome for skills data clearing integration
The enhanced nuclear reset now provides true comprehensive data clearing
that wipes both application state and skills databases (emails, chats,
cached files) for complete fresh start experience.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add "Log Out & Clear App Data" combined button in settings page
- Implement nuclear reset using window.location.href redirect for complete state clearing
- Fix incomplete data clearing where Redux state remained in memory after logout
- Remove manual Redux dispatching and navigation in favor of page redirect approach
- Clean up unused imports (clearToken, useAppDispatch, useNavigate)
- Add confirmation modal with amber warning styling and proper error handling
- Ensure skills connections (Gmail, Telegram, Notion) show as disconnected after clearing
- Use window.localStorage and window.sessionStorage for ESLint compliance
The nuclear reset approach guarantees complete application state reset by redirecting
to login page after clearing all storage, eliminating issues where skills remained
connected in UI despite data clearing operations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Fix race condition where agent responses went to wrong threads when users switched conversations
- Add activeThreadId state to track which thread is currently sending/receiving messages
- Implement single active conversation pattern to prevent concurrent message sending
- Fix optimistic message persistence bug where user messages disappeared after conversation switch
- Replace optimistic messaging with immediate persistent storage for user messages
- Add clear UI feedback when other conversations are active with disabled inputs
- Ensure responses always go to original sending thread regardless of current selection
- Simplify addInferenceResponse logic by removing complex retroactive user message handling
- Add proper error handling for failed message sends with cleanup of persisted messages
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Updated `syncNotionMetadataToBackend` to include additional Notion data (pages and summaries) for backend integration.
- Refactored `syncNotionStateToSlice` to handle profile, pages, and summaries more effectively.
- Revised `TOOLS.md` to improve clarity and organization of parameters for Gmail and Notion tools.
- Added new entries to `.gitignore` for prebuilt TDLib files.
- Deleted `agentLoop.test.ts` as part of cleanup for deprecated agent loop service and related components.
- Reduced `TOOLS.md` size by removing documentation for 100+ outdated GitHub tools.
- Updated `forceToolsCacheRefresh` to use `async` for consistency.
- Simplified `threadSlice` message synchronization logic.
Updated OAuth provider login URLs to use "responseType=json" for development mode. Enhanced deep link handling by adding support for an additional "key" parameter to distinguish token types.
- Implemented `gmail-connection-status` tool for diagnosing Gmail OAuth connection issues, skill state, and API connectivity.
- Enhanced error handling with improved JSON parse error detection for API responses.
- Updated logging for better diagnostics and traceability in API interactions.
Commented out a redundant health monitoring log in the `alphahuman` module to reduce clutter. Additionally, fixed an issue in `package.json` where the `test:unit:watch` script had an incorrect command.
- Consolidated JSON structure in `.mcp.json` and `.claude/mcp.json` for improved readability.
- Updated `CLAUDE.md` and other documentation files to enhance formatting consistency and clarity.
- Improved the organization of agent roles and initialization procedures in `AGENTS.md`, `BOOTSTRAP.md`, and `IDENTITY.md`.
- Enhanced user understanding and personalization strategies in `USER.md` and `MEMORY.md`.
- Refined tool generation scripts for better error handling and output formatting in `discover-tools.js` and `openClaw-formatter.js`.
- Updated the inference request structure to improve type safety and added comprehensive logging for both requests and responses.
- Modified tool call execution to handle only the latest tool call while sending placeholders for previous calls.
- Implemented error handling for tool results, ensuring proper logging and formatting of error messages.
- Introduced a timeout parameter for network requests in the ops_net module to enhance request reliability.
- Introduced `AgentToolSchema` and `AgentToolExecution` interfaces to define tool registry types based on ZeroClaw compatibility.
- Added `IAgentToolRegistry` interface to provide type-safe operations for managing and executing tools.
- Updated `agentToolRegistry.ts` to explicitly map tool schemas to the `function` type for improved type consistency.
- Added detailed logging for tool schema generation, tool execution, and runtime state checks to improve traceability.
- Enhanced Gmail/Notion tool filtering with additional
- Removed unused `agent.ts` system types, agent loop service (`agentLoop.ts`), corresponding UI components (`AgentExecutionPanel.tsx`), and tests (`agentSlice.test.ts`).
- Cleaned up related imports and ensured no functionality depends on the deprecated files.
- Added new `AgentSystem` types to support enhanced agent execution, tool tracking, API compatibility, and integration with thread system.
- Developed `AgentExecutionPanel` React component for detailed real-time monitoring of agent execution status and history.
- Created comprehensive tests for `AgentLoopService` covering execution flow, tool integration, error handling, and timeout scenarios.
- Added Notion context building functionality to Conversations component, enhancing user messages with relevant Notion workspace information.
- Implemented synchronization of Notion pages and summaries in SkillProvider, ensuring state consistency with the Notion skill.
- Expanded Notion slice to include new state properties for pages and summaries, along with corresponding actions for state management.
- Enhanced type definitions for Notion-related data structures to improve type safety and clarity.
- Updated `package.json` scripts for better error handling and streamlined execution of Tauri commands.
- Added a new `gmail-skill-integration.md` document detailing the Gmail skill integration process, including OAuth2 flow and tool definitions.
- Improved formatting and consistency in `TOOLS.md` for better readability and clarity.
- Enhanced logging in skill management and transport layers for better debugging and monitoring of tool calls.
The toolset has been streamlined to eliminate the Telegram integration, reducing the total tools from 152 to 104 and integrations from 4 to 3. This change simplifies the environment by focusing on the remaining three integrations.
- Remove GitHub remote loading to eliminate 404 errors in development
- Implement automatic cache invalidation when TOOLS.md is updated
- Add file watcher system for real-time cache refresh
- Create useToolsUpdates hook for reactive UI components
- Ensure AI Config page immediately reflects updated tool data
- Auto-dispatch tools-updated events for seamless UI synchronization
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Document expected 404 behavior in AI configuration system where loaders
attempt GitHub remote fetch first, then gracefully fallback to bundled files.
Details:
- Console shows "Failed to load resource: 404" during Settings → AI Config refresh
- Affects: soul/loader.ts and tools/loader.ts GitHub URL attempts
- Fallback works correctly, 404s are cosmetic console warnings
- TODO: Setup public AI config repository for clean remote loading
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Steven Enamakel