Georgi Pepelyankov
Problem
More and more of our work runs through terminal agents and wrappers: Claude Code, Codex CLI, Cursor, pi and custom orchestrators. Brain is the one assistant that actually knows our company, with workspace context, installed skills, memory, connected apps and permissions. But it only exists inside the ClickUp UI and Brain MAX. So we either keep switching between tools, or we rebuild that context badly in other agents.
The ClickUp MCP server doesn't solve this. It gives another model raw access to tasks and docs. It doesn't give us Brain itself: its skills, memory, Super Agents, connected-app search, or its judgment about our workspace.
Request
A first-party Brain CLI and agent endpoint:
  1. Auth: brain login using OAuth or a device-code flow tied to my ClickUp account. Tokens are scoped to my existing permissions, with SSO/SAML support and admin controls.
  2. Interactive mode: a brain REPL in the terminal with the same capabilities as Brain in ClickUp: skills (system and user-installed, so new skills show up automatically), memory, search across the workspace and connected apps, and write actions using the same confirmation rules.
  3. Headless mode: something like brain -p "..." --json for scripts and CI, with streaming output and structured results.
  4. Agent interoperability: expose Brain as an MCP server and/or agent-to-agent (A2A) endpoint, so Claude Code, Codex, Cursor and other harnesses can delegate work to Brain as a sub-agent. Today they can only call low-level ClickUp tools.
  5. Super Agents: invoke or chat with workspace Super Agents from the CLI.
  6. Local context bridge (opt-in): let Brain read files from the local working directory, so it can, for example, update a task with a diff summary or check a spec against the code.
  7. Governance: every CLI action shows up in the ClickUp audit log the same way UI actions do, permissions are identical to the web app, and admins can enable or disable the CLI at workspace level.
Why it matters
• Brain becomes the company's context layer for every agent, not just one more chat window.
• Skills and memory built in ClickUp become reusable everywhere, which makes the Brain seat worth a lot more.
• Without this, teams will keep piping ClickUp data into other models, and ClickUp turns into a database rather than the intelligence layer.
Example workflows
• In Claude Code: "ask Brain what the acceptance criteria are for this ticket and which compliance rules apply," then implement.
• A CI step: brain -p "summarise this release and post it to the #releases channel"
• From a terminal: brain "what's blocking the DK launch?", answered with full workspace and connected-app context.