0. Install the CLI (optional)
If you want terminal workflows, installpb: Install pb. MCP-only users skip to step 1.
1. Open your workspace
Sign in atwork.productbrain.io, open the workspace you want to connect, and use the app-provided connect command or MCP configuration.
2. Pick a connection path
Choose based on where your AI assistant runs:- Use MCP when your assistant runs in Cursor, Claude, ChatGPT, or another tool that supports connected tools.
- Use the CLI when your assistant can run terminal commands in your project and you want terminal-native control.
3. Orient before work
Before substantive work, your agent should orient from the Chain. Orientation loads the relevant decisions, tensions, standards, and active work for the task. What you say to your agent:4. Start a write session
When work will change code, product decisions, or reusable knowledge, start a session. In MCP-connected tools, the agent can do this for you. What you say to your agent:5. Capture what changed
Capture decisions, tensions, or insights as they appear. The human says what changed; the agent handles the tool call. What you say to your agent:6. Close the loop
Close the session so the next agent or teammate inherits current context. What you say to your agent:FAQ
Do I need a developer?
If your AI assistant already works inside your repo or supports MCP tools, you can usually try Product Brain yourself. Some team or company-managed AI clients may require admin permissions.Can I try this without changing my product?
Yes. Start by orienting and capturing one decision. You do not need to expose secrets or let an agent write anything just to understand the workflow.My AI client does not show Product Brain tools
Restart the AI client after changing its MCP configuration. Many clients only load tools at startup.The assistant says writes are blocked
Write tools require the right workspace key and a grounded session. Ask the agent to orient around the task and start a session before it writes.The docs show old content
Mintlify deploys from GitHub. If a docs change was committed but is not visible yet, confirm Mintlify is pointed atdocs/public, redeploy Mintlify, or wait for the deploy to finish.