Skip to content

protoWorkstacean connects to external services through plugins and runs agents through runtimes. Both are opt-in — a plugin only activates when its required env vars are set.

Communication channels

Channels is the single interface for adding, configuring, and routing all communication channels. One workspace/channels.yaml entry connects a platform channel to an agent and gives that agent its own bot identity.

Platform integrations

IntegrationTriggersEnv var that enables it
Discord@mentions, slash commands, reactionsDISCORD_BOT_TOKEN
GitHubWebhooks — issues, PRs, org eventsGITHUB_TOKEN or GITHUB_APP_ID
LinearIssue webhooks → routing + comment replyLINEAR_API_KEY
Google WorkspaceGmail polling, Calendar polling, Drive/Docs writeGOOGLE_CLIENT_ID
SignalInbound/outbound Signal messagesSIGNAL_URL + SIGNAL_NUMBER

Agent runtimes

RuntimeWhat it doesWhen to use
DeepAgentIn-process LangGraph ReAct agentDefault for new in-process agents (Ava)
A2ADispatches to a remote agent over HTTP (JSON-RPC 2.0 + SSE)Agent lives in a separate service (Quinn, Jon, Researcher, protoPen)

See Runtimes overview for how the executor layer works and how to register a new runtime.

protoWorkstacean — a switchboard, not an agent.