google-oauth-integration

Google OAuth token storage requires configuring environment variables and following symlink setup instructions to ensure multi-package access to tokens for Calendar and Gmail APIs. This architecture allows secure token retrieval and refresh mechanics within the platform.

ToolRegistry and ToolExecutorRegistry manage Google API access differently: ToolRegistry handles tool registration while ToolExecutorRegistry manages execution. This distinction ensures new Google tools are correctly registered for execution and accessible by the agent without manual intervention.

"Unknown tool" errors during Google Calendar or Gmail access typically indicate incorrect tool registration. You need to properly register new Google tools using the ToolRegistry and ensure OAuth credentials and environment variables are correctly configured for the agent to access API data.

Yes, Google OAuth integration supports secure access to Google Tasks APIs along with Calendar and Gmail. The integration documents token file locations, symlink requirements, and environment variable configuration to enable the agent to access these Google services automatically.

Troubleshooting Google OAuth token access problems involves verifying token file locations, checking symlink requirements for multi-package access, and validating environment variable configuration. The integration architecture documents these scenarios to help resolve common token access issues.

Yes, environment variables must be configured before Google OAuth integration to ensure secure access to Google services. The OAuth architecture requires proper environment variable setup and token storage configuration to enable the agent to access Calendar, Gmail, and Tasks APIs without manual intervention.