Brief

Archive an existing decision. Use for outdated decisions that are no longer relevant. To reject a proposed decision, use brief_reject_decision instead.

brief_archive_decision

Ask Brief — your Product Navigator — an open-ended strategic question and get a reasoned answer. Brief runs a conversational agent over your org's decisions, personas, strategy, customers, and competitive landscape. The agent can call Brief workspace tools and connected integrations while answering, so action requests can update or delete workspace or third-party data; confirm destructive actions with the user first. Use this for questions like "what should I build next", "what are my priorities", "what's next", "is this aligned with our strategy", or "what do our customers care about" — `brief_ask` will respond with an answer, not raw data. For raw workspace data (the decisions/personas/pipeline as structured objects), use `brief_get_onboarding_context` instead. Validate approaches against existing decisions (mode: check), or get fast context mid-build (mode: fast, <2s). Send codebase context here during onboarding — Brief processes it into structured product context. On the first call from a fresh coding surface, set `onboarding: true` with README/package manifest/git log in `context` and Brief will synthesise product context plus seed features. Advise/check calls without conversation_id continue the current MCP coding session by default; pass conversation_id to override it or new_conversation: true to start fresh. Stateful responses include `coding_session_key`; pass it as a decision `isolation_key` only when that decision should remain scoped to this coding session. Fast mode is stateless. CALL SHAPES: to ask a new question, send `question` (non-empty) — do NOT send `request_id`. If a long turn is still running, the response is `{status: 'processing', request_id, conversation_id}`; to fetch it, call again with BOTH `request_id` AND `conversation_id` (both required together) and omit `question`. Recovery never starts a second turn and is never charged again. When referencing the Brief web UI, use `workspace_url` from this tool's response. DO NOT guess or construct URLs.

brief_ask

Browse Brief folders and documents by path or folder ID. Returns folder contents.

brief_browse

Confirm a pending (proposed) decision, transitioning it to active. The decision must already exist in Brief with status: proposed. Use `brief_search` with `types: 'decision'` for keyword search, or `brief_list_pending_decisions` to list all decisions awaiting confirmation.

brief_confirm_decision

ESCAPE HATCH for Brief operations not exposed as direct tools (rare ops, batch ops, anything not in the flat tool list). Depending on `operation`, this tool can create, update, archive, or delete Brief workspace data; confirm destructive actions with the user before calling it. Prefer direct tools when available: brief_record_decision, brief_confirm_decision, brief_reject_decision, brief_archive_decision, brief_update_product_context, brief_search, brief_browse, brief_list_pending_decisions. Use brief_get_onboarding_context for reads of workspace/product context. Calling this tool for an op that has a direct equivalent costs an extra round-trip and gives the user a worse experience. When referencing the Brief web UI, use `workspace_url` and per-object `view_url` fields from this tool's response. DO NOT guess or construct URLs.

brief_execute_operation

Fetch the user's raw Brief workspace context — decisions, personas, features, current work pipeline — as structured data. CALL THIS FIRST on a fresh session and whenever the user says any of: "/brief-setup", "/brief-context", "brief setup", "brief context", "set me up", "catch me up", "what do you know about my product", "what's in Brief", "what's in my workspace", "tell me about my workspace", "who are my users", "what are my personas", "what decisions have been made", or any first-contact Brief question. This is the canonical first-contact tool — it is NOT `brief_search` (search is for finding one specific thing) and NOT `brief_ask` (ask is for strategic reasoning AFTER context is loaded). Call `brief_get_onboarding_context` once at session start as a PRIMER before you start reasoning about the user's product. Default scope: 'full' returns the complete strategic snapshot. scope: 'product' returns just the product context object — narrower and faster. scope: 'identity' returns just workspace id and name — use for sanity checks. When referencing the Brief web UI, use `workspace_url` and per-object `view_url` fields from this tool's response. DO NOT guess or construct URLs.

brief_get_onboarding_context

Returns live { personal, team, available } integration buckets for this workspace. Call BEFORE telling the user an integration is not supported / not available — Brief supports more integrations than the tools currently loaded in this session. `personal`: app names usable by the current chat identity (tools are loaded for these), including workspace-shared credentials. `team`: { app, connectUrl } connected in the workspace but not usable by the current chat identity; share the entry's `connectUrl` when a personal connection is needed. `available`: { app, connectUrl } registered in Brief but nobody on the team has connected yet; share the entry's `connectUrl`.

brief_get_integration_buckets

Returns the list of currently connected integration names for this workspace. Used by the integration connector panel for status polling.

brief_get_integration_status

List decisions awaiting confirmation (status: proposed). Returns pending decisions only — use `brief_search` with `types: 'decision'` for keyword search across all statuses. Filter by `assigned_to_me` or `created_by_me` to narrow.

brief_list_pending_decisions

Record a consequential decision in the user's Brief workspace. Use whenever the user makes a deliberate choice that should be remembered: architectural decisions, product direction, process choices, technology selections, etc. For proposing a decision for someone else to confirm later, set status: 'pending' and optionally assigned_to_email. Default status is 'confirmed' (recording in one shot). IMPORTANT: This renders an approval card for the user. The decision is NOT recorded until the user explicitly approves. After calling this tool, STOP AND WAIT for the next turn — do not assume success, do not call other tools, do not try to record the decision yourself.

brief_record_decision