Intent routing
The orchestrator brain parses a request and decides which of the eight arms owns it — Builder, Social, Knowledge, Automation or beyond.
Arm 02 / AI Agent
One orchestrator brain coordinating autonomous agents across the OctoPush arms. Intent is routed, tasks are dispatched, results are aggregated — all under the same row-level security as your browser session.
One brain, eight arms, four steps
Read the practical OctoPush orchestration guide →The orchestrator brain parses a request and decides which of the eight arms owns it — Builder, Social, Knowledge, Automation or beyond.
It hands the task to the right autonomous agent, passing context, scope and the credits it may spend.
Outputs flow back through the brain, which merges, validates and surfaces a single coherent result to the user.
Every agent runs with the user's own token, so row-level security limits it exactly as it limits the browser session.
First-class tools — after you approve
Publish to the community feed on the operator's behalf.
Drop a private message into a conversation.
Spin up a new AI agent conversation and send the first turn.
List feed posts, conversations, agents and threads.
OctoPush speaks the Model Context Protocol. Paste the app's MCP link into your AI client, approve the access on the OctoPush consent screen, and the agent starts working in your name — with your permissions, your data scope and your revocation at any time.
Model Context Protocol
OAuth-authorized, consent-gated, RLS-bound. The agent is never its own user — it is you, scoped and revocable.
Every agent call runs with your own session token. No service key, no bot user, no copyable secret.
What you can't see in the browser, the agent can't see either. Row-level security applies identically.
Revoke a client from settings in one click. Access stops immediately — no lingering keys.
Create an account, approve an agent, and let OctoPush coordinate across the eight arms on your behalf.