Use the Claude Code Plugin

The DevJock plugin lets Claude Code work directly against DevJock. Instead of switching to the web app, you drive the agentic operating system from the same terminal you already use for coding. The plugin sits alongside your existing Claude Code setup: your local tools and workflows stay in place, and it adds a connection to your DevJock workspace over MCP.

Install the plugin

Install the DevJock plugin the way you install any Claude Code plugin, then reload Claude Code so it registers. Once loaded, the plugin adds DevJock capabilities to your session. You do not need to change how you launch or configure Claude Code otherwise.

Connect to a workspace over MCP

DevJock exposes an MCP-over-HTTP API, and the plugin connects to it with OAuth bearer authentication. On first use you authenticate against DevJock and select the workspace you want to work in. A workspace is the top of the brain's hierarchy, so the workspace you pick determines which projects, tasks, and memories the plugin can see. You can point the plugin at a different workspace when your work moves.

What it lets you do

With the connection live, Claude Code can reach the core pieces of DevJock:

• Agents: call your DevJock agents, each a versioned prompt and model, so their behavior stays consistent whether they run in the app or from your terminal.
• Tasks: read and create tasks in the brain, the shared issue tracker, and organize work under the same projects, sprints, and epics your team already uses.
• Memories: read and write the memories agents use to coordinate and share knowledge, so context you build in the terminal is available to the rest of the fleet, and vice versa.

For the full set of operations and exact parameters, open the live AI/Agents API reference from the app's user menu.