brief_archive_decision
ChatGPTArchive an existing decision. Use for outdated decisions that are no longer relevant. To reject a proposed decision, use brief_reject_decision instead.
Brief helps product teams and coding agents retrieve product context, reason over strategy, find and manage decisions, browse workspace knowledge, and connect the tools their team uses.
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_search with types: 'decision' for keyword search, or brief_list_pending_decisions to list all decisions awaiting confirmation.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.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_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_search with types: 'decision' for keyword search across all statuses. Filter by assigned_to_me or created_by_me to narrow.types to narrow by entity type (comma-separated: document, decision, feature, persona, research_signal, competitor), or omit for the cross-entity default.integration: "LINEAR" — single card for one integration - category: "development" — cards for one category - no args — full grid of all integrations On-demand only — do not call automatically.category argument: "analysis" (research / synthesis), "decision" (capture / revisit), or "planning" (prioritization / shipping). Omit to show the default mixed set. Use it when the user asks for a narrower slice ("show me decision prompts"). The panel pre-seeds your next-turn context with the visible prompts, so even if the user doesn't click one you can treat the buttons as hints about what they want help with. Call at most once per orientation moment — do NOT invoke on every turn.Click any prompt to copy it.
App Stats
19
Tools
2
Prompts
ChatGPT
Platforms
Category
Work ManagementWorks with
Data refreshed daily