Add connector infrastructure and CLI-managed Google integration#23
Merged
Add connector infrastructure and CLI-managed Google integration#23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the first version of a connector layer for Octopal and wires it into configuration, runtime startup, and agent visibility.
It adds connector infrastructure to the app, extends the configurator with a dedicated Connectors section, and ships the first Google connector implementation. The current supported Google service is Gmail, with an explicit CLI-managed auth flow, lifecycle commands, normalized connector state, runtime reconciliation with managed MCP servers, and read-only status visibility for Octo and workers.
Highlights:
octopal configureoctopal connector auth googleoctopal connector statusandoctopal connector disconnect