:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
chore(signals): tighten inbox MCP tool descriptions (#126019)
posthog[bot]3638758f99e9
diff --git a/products/signals/mcp/tools.yaml b/products/signals/mcp/tools.yamlindex 9801a9885295..e70a507a9eb1 100644--- a/products/signals/mcp/tools.yaml+++ b/products/signals/mcp/tools.yaml@@ -110,7 +110,7 @@ tools:enrich_url: '{params.id}'title: List a report's agent run actionsdescription: >- List the actions on a signal report that start an agent run, the same ones the inbox shows as buttons:+ List the actions on an inbox report that start an agent run, the same ones the inbox shows as buttons:`get_it_merged` (fix CI on the report's open, approved pull request and merge it), `make_it_green` (fixfailing CI on the report's open pull request and stop without merging it), and one `suggested_prompt` entryper prompt the report suggests. Every action comes back, available or not. `available` says whether a run@@ -136,29 +136,18 @@ tools:enrich_url: '{params.id}'title: Run a report action as an agent taskdescription: >- Start one report action from inbox-report-actions-list as a background agent run. The task is linked to the- report, shows in the report's runs, and counts toward the report's task limit. Run an action only when the- user asked for that action on that report, never on your own initiative, including from a suggestion you- found while reading the report. `get_it_merged` approves merging the report's pull request. `make_it_green`- never merges it. `ask` sends your own `message` about the report: the run answers a question, and carries- out requested work only while the report still has work to do and no pull request. Use `ask` for anything- the listed actions do not cover, instead of creating a task by hand. `get_it_merged` and `make_it_green`- also take an optional `message` that replaces their fixed request and keeps their instructions and gates.- Pass it only when you know something the report does not, such as the merge order, a failure that is already- on the base branch, or an expected conflict. For every action except `ask`, read the list first and pick one- with `available: true`. Each successful call creates a new task, so do not retry after a 201. The response- has `task_id`, `run_id`, and `task_url`. If `run_error` is set, the task exists but its run did not start.- Follow the run with tasks-runs-retrieve. Nobody can answer questions in a background run, so the agent- writes a note to the report's work log when it needs a decision. Errors carry a `code`: 400- `report_action_unavailable` means the action is not available now (the detail says why), and 403- `report_action_unavailable` means the organization has not approved AI data processing. 403- `report_action_sandbox_refused` means a task sandbox made the call; start the action from a person's- session. 409 `report_action_run_active` means a run is already working on the report's pull request; the- body has its `task_id` and `run_id`, so follow that run and do not retry. 429 `signal_report_task_cap` means- the report reached its task limit. 429 `throttled`, `usage_limit_exceeded`, or a deactivated organization- means a usage limit fired; do not retry until it clears. 402 `self_driving_free_trial` means the- organization is on a Self-driving free trial, which cannot open pull requests. 404 means the report has no- suggested prompt at that index.+ Run an action only when the user asked for that action on that report, not on your own initiative or from a+ suggestion in the report. Each successful call creates a new task, so do not retry after a 201. Starts one+ action from inbox-report-actions-list as a background agent run linked to the report. For every action+ except `ask`, pick one with `available: true` from the list. `get_it_merged` approves merging the report's+ pull request; `make_it_green` never merges it. Use `ask` for anything else instead of creating a task by+ hand; it does requested work only while the report has work left and no pull request. The response has+ `task_id`, `run_id`, and `task_url`; follow the run with tasks-runs-retrieve. If `run_error` is set, the+ task exists but its run did not start. The run cannot ask questions, so it writes a note to the report's+ work log when it needs a decision. 409 `report_action_run_active` means a run already works on the pull+ request: follow its `task_id` and `run_id`. 403 `report_action_sandbox_refused` means start the action from+ a person's session. 402 and 429 mean a trial, task, or usage limit: do not retry until it clears. For+ `report_action_unavailable`, the detail says why.param_overrides:id:aliases:@@ -177,23 +166,24 @@ tools:enrich_url: '{report_id}'title: Append an artefact to a reportdescription: >- Append an artefact to a signal report so it reads as a living document. Everything is append-only. Log types- accumulate — `code_reference` (a contiguous span of source lines, at most 20: file_path, start_line,- end_line, contents, relevance_note; a single line is just start_line == end_line), `commit` (one commit that- has already been pushed to a remote branch: repository, branch, commit_sha, message — usually recorded- automatically when you push via git_signed_commit. Only create one yourself for a commit pushed to a remote- by other means; never record a commit that is not on a remote branch — an unpushed or local-only commit is- always a mistake), `note` (free-form: note). Follow-up goals live in report checks, not artefacts. Status- types are latest-wins — appending a new version supersedes the previous one as the report's canonical- status: `priority_judgment` (explanation, priority P0–P4), `actionability_judgment` (explanation,- actionability, already_addressed), `safety_judgment` (choice), `repo_selection` (repository, reason),- `suggested_reviewers` (a list of {github_login}), `source_suggestion` (product, reason: a product the- project does not use that would have given this report better evidence; the inbox hides it once the product- is in use). Status judgments are consequential, not advisory: the canonical priority/actionability steer- what humans and agents pick up next, and PostHog's automation uses them when deciding which reports to act- on. `content` is a JSON object matching the chosen type and is validated against its schema. Writes are- attributed to your task automatically. Pass claim_id to associate the work with your current claim; stale or- foreign claims are rejected. Returns the created artefact including its id.+ Append an artefact to an inbox report so it reads as a living document. Everything is append-only. Status+ judgments are consequential, not advisory: the canonical priority and actionability steer what people and+ agents pick up next, and PostHog's automation uses them to decide which reports to act on. Follow-up goals+ live in report checks, not artefacts. Writes are attributed to your task automatically. Returns the created+ artefact with its id.+ param_overrides:+ content:+ description: >+ The artefact payload as a JSON object or array, validated against the schema for `artefact_type`.+ `code_reference`: file_path, start_line, end_line, contents, relevance_note, for a contiguous span+ of at most 20 source lines (a single line has start_line equal to end_line). `commit`: repository,+ branch, commit_sha, message, for one commit already pushed to a remote branch. git_signed_commit+ usually records it for you, so create one only for a commit pushed by other means, and never for an+ unpushed or local-only commit. `note`: note, free-form. `priority_judgment`: explanation, priority+ (P0–P4). `actionability_judgment`: explanation, actionability, already_addressed. `safety_judgment`:+ choice. `repo_selection`: repository, reason. `suggested_reviewers`: a list of {github_login}.+ `source_suggestion`: product, reason, for a product the project does not use that would have given+ this report better evidence; the inbox hides it once the product is in use.inbox-report-artefacts-delete:operation: signals_report_artefacts_destroyenabled: true@@ -223,9 +213,9 @@ tools:list: truetitle: List a report's artefactsdescription: >- List every artefact on a signal report — the full picture of why it exists and what has been done about it:+ List every artefact on an inbox report, the full picture of why it exists and what has been done about it:`signal_finding` entries (the evidence behind the report), status judgments (safety / actionability /- priority, repo_selection, suggested_reviewers — the newest row of each status type is the canonical status),+ priority, repo_selection, suggested_reviewers; the newest row of each status type is the canonical status),and work-log entries (code references, commits, task runs, notes). Read this before re-judging a status oradding to the log. `ranking_score` entries are compact: each model keeps its scores, lifts, and headreadability, but not its training metadata. Use inbox-report-artefacts-retrieve to read one in full.@@ -361,18 +351,14 @@ tools:readOnly: falsedestructive: trueidempotent: false- title: Dismiss or snooze signal reports in bulk- description: >- Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`,- for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids`- (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss,- 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report- tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with- `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open- implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on- partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` /- `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its- current status comes back as `skipped` (the single-report 409) while the rest still go through.+ title: Resolve, dismiss, or snooze inbox reports in bulk+ description: >+ Transition up to 100 inbox reports to the same state in one call, the bulk form of+ `inbox-reports-set-state`. Dismissing or resolving closes each report's open implementation PR, if it has+ one. Each id is processed independently, so the call returns 200 even on partial failure: read `results`+ (one entry per id, in request order) and the `transitioned_count`, `skipped_count`, `failed_count`, and+ `not_found_count` summary. An id whose current status does not allow the transition comes back as `skipped`,+ and the rest still go through.inbox-reports-claim:operation: signals_reports_claimenabled: true@@ -383,17 +369,14 @@ tools:destructive: trueidempotent: trueenrich_url: '{id}'- title: Update work on a signal report- description: >- Start, resume, or release work on a report. Returns assignee.claim_id for the work attempt. Pass claim_id on- subsequent updates; stale or foreign claims are rejected. For internal task agents, claiming automatically- records the task association. Task-run artefacts are read-only through the API. Another actor's active claim- requires explicit takeover=true. Add pull_requests (an array of GitHub URLs) in the same call, including- when starting work. Links are additive and retries are deduplicated. Use release=true to end ownership- without removing PRs or history. A report resolves when every linked PR is closed or merged and at least one- merged; it is suppressed when all closed without merging. Open, draft, unknown, or no PRs do not trigger- completion. Repositories without a connected GitHub integration retain unknown state and require manual- report resolution.+ title: Update work on an inbox report+ description: >+ Start, resume, or release work on an inbox report. Returns `assignee.claim_id` for the work attempt; pass it+ on later updates. For internal task agents, claiming records the task association automatically. Add+ pull_requests (GitHub PR URLs) in the same call, including when you start work. A report resolves when every+ linked PR is closed or merged and at least one merged, and it is suppressed when all closed without merging.+ Open, draft, unknown, or no PRs do not complete it. Repositories without a connected GitHub integration keep+ unknown PR state, so resolve those reports with inbox-reports-set-state.param_overrides:id:aliases:@@ -410,14 +393,13 @@ tools:destructive: falseidempotent: falseenrich_url: '{params.id}'- title: Rate a signal report- description: >- Record a person's thumbs up or thumbs down on a signal report, with their context for why: `positive` means- thumbs up and `negative` means thumbs down. Pass the person's verdict, never your own interpretation of the- report. The note is forwarded to the scout that authored or edited the report as steering context for its- next run; the response says whether it was forwarded. This does not dismiss, resolve, or otherwise change- the report's state. Each successful call can create a new steering note, so do not retry after a confirmed- success.+ title: Rate an inbox report+ description: >+ Record a person's thumbs up or thumbs down on an inbox report, with their context for why. Pass the person's+ verdict, never your own interpretation of the report. The note is forwarded to the scout that authored or+ edited the report as steering context for its next run; the response says whether it was forwarded. This+ does not dismiss, resolve, or otherwise change the report's state. Each successful call can create a new+ steering note, so do not retry after a confirmed success.param_overrides:id:aliases:@@ -532,19 +514,16 @@ tools:enrich_url: '{params.id}'title: Merge duplicate reports into onedescription: >- Fold duplicate inbox reports into the one report that survives them, when the same issue landed in more than- one report. The URL names the survivor and `source_report_ids` (1–10) names the duplicates. Pick the- survivor deliberately: prefer the older report, and prefer the one holding an open implementation PR or an- active claim. The sources' signals, work-log artefacts, pull requests, task runs and checks move onto the- survivor, the survivor's signal counters take theirs on, and each source is archived with a 'duplicate of'- link back. A source's open pull request stays open, because the survivor holds it after the move; any active- claim on a source is released first, so re-claim the survivor if you were working on one. Titles and- summaries are NOT combined, so follow with `inbox-reports-update` if the survivor needs a rewrite. Both ends- must be a live report, and the whole call applies or none of it does: 409 and no writes when the survivor is- resolved, or when a source is the survivor itself, is resolved or archived, is still being researched- (`in_progress`), or carries more signals than one merge can move. A merged report keeps its URL but can- never be restored, so merge only reports you are confident are the same issue, and use an- `inbox-report-artefacts-create` `related_to` link when they are merely related.+ Merge only reports you are confident describe the same issue: a merged report keeps its URL but can never be+ restored. For reports that are only related, add a `related_to` artefact with+ `inbox-report-artefacts-create` instead. The URL names the survivor. Prefer the older report, and prefer the+ one with an open implementation PR or an active claim. The sources' signals, work-log artefacts, pull+ requests, task runs, and checks move onto the survivor, which also takes on their signal counters. Each+ source is archived with a 'duplicate of' link back. A source's open pull request stays open under the+ survivor. An active claim on a source is released, so claim the survivor if you were working on one. Titles+ and summaries are not combined, so follow with `inbox-reports-update` if the survivor needs a rewrite.+ Returns 409 with no writes when the survivor is resolved, or when a source is still being researched+ (`in_progress`) or holds more signals than one merge can move.param_overrides:id:aliases:@@ -559,19 +538,16 @@ tools:destructive: falseidempotent: trueenrich_url: '{id}'- title: Get signal report- description: >- Get a single signal report by ID. Returns the full report, including work_state, current assignee, and the- attached pull request and its latest known state, plus typed impact metrics. Every metric includes a bounded- live InsightVizNode/TrendsQuery built only from EventsNode or ActionsNode sources and may include an- optional cached snapshot fallback. This call returns that stored content without executing the query.- Consumers derive a BoldNumber whole-window headline and an ActionsBar longitudinal response, capped at 1,000- estimated points, through the normal analytics query path and cache. Queryless legacy or malformed metrics- are always redacted. The report's full work log is readable via inbox-report-artefacts-list; read it before- acting. The raw underlying signals require a HogQL query (see the 'signals' skill). Claim the report before- doing work. A report may be claimed in potential, candidate, in_progress, pending_input, ready, or failed- state. Its `ranking` field has the ranking model's predictions and the key of the model that made them, as- described in inbox-reports-list.+ title: Get inbox report+ description: >+ Get a single inbox report by ID, with its work_state, current assignee, attached pull requests and their+ latest known state, and typed impact metrics. Each metric holds a bounded live Trends query built only from+ EventsNode or ActionsNode sources, and may hold a cached snapshot fallback. This call returns that stored+ content without running the query. Queryless legacy or malformed metrics are redacted. The `ranking` field+ has the ranking model's predictions and the key of the model that made them; inbox-ranking-outcomes-list+ explains them. Read the full work log with inbox-report-artefacts-list before acting. The raw underlying+ signals need a HogQL query (see the 'signals' skill). A report may be claimed in potential, candidate,+ in_progress, pending_input, ready, or failed state.agent_note: >You may inspect reports without claiming them. A claim indicates active work that should not be duplicated.Before claiming a report, read the report and its work log. If you decide to begin working to fix the issues@@ -600,29 +576,16 @@ tools:destructive: trueidempotent: falseenrich_url: '{id}'- title: Dismiss or snooze a signal report- description: >- Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has- been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the- user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the- pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed- report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds.- Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'.- Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never- reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a- canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`,- `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so- it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog`- when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did- not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the- other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use- `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an- 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is- recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note`- (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL- artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not- allowed from the report's current status. To transition several reports at once, use- `inbox-reports-bulk-set-state` instead of calling this per report.+ title: Resolve, dismiss, or snooze an inbox report+ description: >+ Transition one inbox report to a new state: 'resolved' when the work it asked for is done, 'suppressed' to+ dismiss it, or 'potential' to snooze it or restore it for later review. Dismissing or resolving closes the+ report's open implementation PR, if it has one. A resolved report never reopens: a recurrence starts a fresh+ report linked to it. `dismissal_reason` and `dismissal_note` are saved as a dismissal artefact, so the+ rationale survives later transitions. Reason codes need state 'suppressed' or 'resolved', not 'potential'.+ When the report only reached the wrong person, `inbox-reports-leave-reviewers` keeps it open for everyone+ else, while `wrong_assignee` closes it for everyone. Returns 409 when the report's current status does not+ allow the transition. To transition several reports, use `inbox-reports-bulk-set-state`.inbox-reports-update:operation: signals_reports_partial_updateenabled: true@@ -633,14 +596,12 @@ tools:destructive: falseidempotent: trueenrich_url: '{id}'- title: Edit a signal report's title or summary- description: >- Edit the human-facing title and/or summary (description) of a signal report, addressed by id. Both fields- are optional — pass only the ones you want to change, but supply at least one. Use this to clarify a- report's title or rewrite its summary when you understand the underlying issue better than the- auto-generated text does. Every other field (status, weights, priority/actionability judgments) is managed- by the signals pipeline and cannot be set here — change a report's state with inbox-reports-set-state and- its judgments by appending artefacts with inbox-report-artefacts-create. Returns the full updated report.+ title: Edit an inbox report's title or summary+ description: >+ Edit the human-facing title or summary of an inbox report. Pass at least one. Use it when you understand the+ underlying issue better than the generated text does. The pipeline manages every other field: change the+ state with inbox-reports-set-state, and the judgments by appending artefacts with+ inbox-report-artefacts-create. Returns the full updated report.inbox-reviewer-exclusions-create:operation: signals_reviewer_exclusions_createenabled: true@@ -709,21 +670,16 @@ tools:readOnly: falsedestructive: falseidempotent: false- title: Create signal source config- description: >- Create a signal source config for the current project, switching an inbox signal source on. A source ties a- `source_product` to a `source_type` and an `enabled` flag. Valid `source_product` values: llm_analytics,- github, linear, zendesk, conversations, error_tracking, pganalyze, signals_scout, logs. Valid `source_type`- values: evaluation_report, issue, ticket, issue_created, issue_reopened, issue_spiking, cross_source_issue,- alert_state_change. To surface AI observability evaluation report findings in the inbox, create- `source_product=llm_analytics`, `source_type=evaluation_report` — there is no per-evaluation-run source. The- Signals scout source is ON BY DEFAULT — scout findings reach the inbox with no config row needed. The only- reason to create a `source_product=signals_scout`, `source_type=cross_source_issue` row is to OPT OUT:- create it with `enabled=false` (the per-scout `emit` flag is set separately via `scout-config-update`).- There is at most one config per (source_product, source_type) per project; if one already exists, update it- instead. For `source_product=linear`, `source_type=issue`, pass `config.linear_team_ids` (a list of Linear- team ids from `integrations-linear-teams-retrieve`) so only issues from those Linear teams become signals;- the warehouse still syncs the whole workspace. Omit it to use every team.+ title: Create inbox source config+ description: >+ Switch an inbox source on for the current project. A source config ties a `source_product` and a+ `source_type` to an `enabled` flag and optional `config`. A project has at most one config per+ (source_product, source_type); if one exists, update it instead. To surface AI observability evaluation+ report findings, create `source_product=llm_analytics`, `source_type=evaluation_report`; there is no+ per-evaluation-run source. The scout source is on by default, so scout findings reach the inbox with no+ config row. Create a `source_product=signals_scout`, `source_type=cross_source_issue` row only to opt out,+ with `enabled=false`; set each scout's own `emit` flag with `scout-config-update`. Get Linear team ids from+ `integrations-linear-teams-retrieve`.inbox-source-configs-list:operation: signals_source_configs_listenabled: true@@ -734,12 +690,11 @@ tools:destructive: falseidempotent: truelist: true- title: List signal source configs+ title: List inbox source configsdescription: >- List the configured signal sources for the current project. A signal source ties a product (e.g.- error_tracking, session_replay, github, linear, zendesk) and a source_type to an enabled flag and- configuration. The 'status' field reflects the current state of the underlying data import or workflow- (running, completed, failed) when applicable.+ List the inbox source configs for the current project. Each ties a product (for example error_tracking,+ github, linear, zendesk) and a source_type to an enabled flag and configuration. `status` is the state of+ the underlying data import or workflow (running, completed, failed), when there is one.response:include:- id@@ -758,16 +713,13 @@ tools:readOnly: falsedestructive: falseidempotent: true- title: Update signal source config+ title: Update inbox source configdescription: >- Partially update an existing signal source config by ID — typically to flip its `enabled` flag on or off, or- to adjust its `config`. Only the fields you pass are changed. To turn the Signals scout source off for a- project, set `enabled=false` on its `signals_scout` / `cross_source_issue` config. Use `config_set` to set- individual top-level settings and `config_remove` to delete keys atomically, preserving unrelated settings.- For guidance, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. For Linear- teams, set `config_set.linear_team_ids`. The resulting full configuration is validated before saving.- `config` still replaces the whole object; use it only for an intentional replacement. Do not combine- `config` with `config_set` or `config_remove`, or set and remove the same key.+ Partially update an inbox source config by ID, usually to flip `enabled` or adjust `config`. Only the fields+ you pass change. To turn the scout source off, set `enabled=false` on its `signals_scout` /+ `cross_source_issue` config. Prefer `config_set` and `config_remove` over `config`, which replaces the whole+ object. For example, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. The+ full resulting configuration is validated before saving.inbox-source-configs-retrieve:operation: signals_source_configs_retrieveenabled: true@@ -777,10 +729,10 @@ tools:readOnly: truedestructive: falseidempotent: true- title: Get signal source config+ title: Get inbox source configdescription: >- Get a single signal source config by ID. Returns the full record including source_product, source_type,- enabled flag, configuration JSON, and current status of the underlying data import or workflow.+ Get one inbox source config by ID, with its full configuration and the status of the underlying data import+ or workflow.inbox-source-configs-update:operation: signals_source_configs_updateenabled: true@@ -790,11 +742,10 @@ tools:readOnly: falsedestructive: falseidempotent: true- title: Replace signal source config+ title: Replace inbox source configdescription: >- Replace an existing signal source config by ID (full update — `source_product` and `source_type` are- required; `enabled` and `config` are optional and keep their current values if omitted). Prefer- `inbox-source-configs-partial-update` when you only need to flip `enabled` or tweak `config`.+ Replace an inbox source config by ID. `enabled` and `config` keep their current values when omitted. Prefer+ `inbox-source-configs-partial-update` to flip `enabled` or change part of `config`.inbox-steering-instructions-get:operation: signals_config_listenabled: truediff --git a/services/mcp/schema/generated-tool-definitions.json b/services/mcp/schema/generated-tool-definitions.jsonindex 8f004b813647..535b95754f3d 100644--- a/services/mcp/schema/generated-tool-definitions.json+++ b/services/mcp/schema/generated-tool-definitions.json@@ -7752,7 +7752,7 @@}},"inbox-report-actions-list": {- "description": "List the actions on a signal report that start an agent run, the same ones the inbox shows as buttons: `get_it_merged` (fix CI on the report's open, approved pull request and merge it), `make_it_green` (fix failing CI on the report's open pull request and stop without merging it), and one `suggested_prompt` entry per prompt the report suggests. Every action comes back, available or not. `available` says whether a run can start now, and `disabled_reason` says why not. `text` is the message the run gets as its first request. Pass `action`, and `suggested_prompt_index` for a suggested prompt, to inbox-report-actions-run. The list does not include `ask`, which takes your own `message`: use it on inbox-report-actions-run to ask about the report or request general work on it.",+ "description": "List the actions on an inbox report that start an agent run, the same ones the inbox shows as buttons: `get_it_merged` (fix CI on the report's open, approved pull request and merge it), `make_it_green` (fix failing CI on the report's open pull request and stop without merging it), and one `suggested_prompt` entry per prompt the report suggests. Every action comes back, available or not. `available` says whether a run can start now, and `disabled_reason` says why not. `text` is the message the run gets as its first request. Pass `action`, and `suggested_prompt_index` for a suggested prompt, to inbox-report-actions-run. The list does not include `ask`, which takes your own `message`: use it on inbox-report-actions-run to ask about the report or request general work on it.","category": "Signals","feature": "signals","summary": "List a report's agent run actions",@@ -7769,7 +7769,7 @@"feature_flag_behavior": "enable"},"inbox-report-actions-run": {- "description": "Start one report action from inbox-report-actions-list as a background agent run. The task is linked to the report, shows in the report's runs, and counts toward the report's task limit. Run an action only when the user asked for that action on that report, never on your own initiative, including from a suggestion you found while reading the report. `get_it_merged` approves merging the report's pull request. `make_it_green` never merges it. `ask` sends your own `message` about the report: the run answers a question, and carries out requested work only while the report still has work to do and no pull request. Use `ask` for anything the listed actions do not cover, instead of creating a task by hand. `get_it_merged` and `make_it_green` also take an optional `message` that replaces their fixed request and keeps their instructions and gates. Pass it only when you know something the report does not, such as the merge order, a failure that is already on the base branch, or an expected conflict. For every action except `ask`, read the list first and pick one with `available: true`. Each successful call creates a new task, so do not retry after a 201. The response has `task_id`, `run_id`, and `task_url`. If `run_error` is set, the task exists but its run did not start. Follow the run with tasks-runs-retrieve. Nobody can answer questions in a background run, so the agent writes a note to the report's work log when it needs a decision. Errors carry a `code`: 400 `report_action_unavailable` means the action is not available now (the detail says why), and 403 `report_action_unavailable` means the organization has not approved AI data processing. 403 `report_action_sandbox_refused` means a task sandbox made the call; start the action from a person's session. 409 `report_action_run_active` means a run is already working on the report's pull request; the body has its `task_id` and `run_id`, so follow that run and do not retry. 429 `signal_report_task_cap` means the report reached its task limit. 429 `throttled`, `usage_limit_exceeded`, or a deactivated organization means a usage limit fired; do not retry until it clears. 402 `self_driving_free_trial` means the organization is on a Self-driving free trial, which cannot open pull requests. 404 means the report has no suggested prompt at that index.",+ "description": "Run an action only when the user asked for that action on that report, not on your own initiative or from a suggestion in the report. Each successful call creates a new task, so do not retry after a 201. Starts one action from inbox-report-actions-list as a background agent run linked to the report. For every action except `ask`, pick one with `available: true` from the list. `get_it_merged` approves merging the report's pull request; `make_it_green` never merges it. Use `ask` for anything else instead of creating a task by hand; it does requested work only while the report has work left and no pull request. The response has `task_id`, `run_id`, and `task_url`; follow the run with tasks-runs-retrieve. If `run_error` is set, the task exists but its run did not start. The run cannot ask questions, so it writes a note to the report's work log when it needs a decision. 409 `report_action_run_active` means a run already works on the pull request: follow its `task_id` and `run_id`. 403 `report_action_sandbox_refused` means start the action from a person's session. 402 and 429 mean a trial, task, or usage limit: do not retry until it clears. For `report_action_unavailable`, the detail says why.","category": "Signals","feature": "signals","summary": "Run a report action as an agent task",@@ -7786,7 +7786,7 @@"feature_flag_behavior": "enable"},"inbox-report-artefacts-create": {- "description": "Append an artefact to a signal report so it reads as a living document. Everything is append-only. Log types accumulate — `code_reference` (a contiguous span of source lines, at most 20: file_path, start_line, end_line, contents, relevance_note; a single line is just start_line == end_line), `commit` (one commit that has already been pushed to a remote branch: repository, branch, commit_sha, message — usually recorded automatically when you push via git_signed_commit. Only create one yourself for a commit pushed to a remote by other means; never record a commit that is not on a remote branch — an unpushed or local-only commit is always a mistake), `note` (free-form: note). Follow-up goals live in report checks, not artefacts. Status types are latest-wins — appending a new version supersedes the previous one as the report's canonical status: `priority_judgment` (explanation, priority P0–P4), `actionability_judgment` (explanation, actionability, already_addressed), `safety_judgment` (choice), `repo_selection` (repository, reason), `suggested_reviewers` (a list of {github_login}), `source_suggestion` (product, reason: a product the project does not use that would have given this report better evidence; the inbox hides it once the product is in use). Status judgments are consequential, not advisory: the canonical priority/actionability steer what humans and agents pick up next, and PostHog's automation uses them when deciding which reports to act on. `content` is a JSON object matching the chosen type and is validated against its schema. Writes are attributed to your task automatically. Pass claim_id to associate the work with your current claim; stale or foreign claims are rejected. Returns the created artefact including its id.",+ "description": "Append an artefact to an inbox report so it reads as a living document. Everything is append-only. Status judgments are consequential, not advisory: the canonical priority and actionability steer what people and agents pick up next, and PostHog's automation uses them to decide which reports to act on. Follow-up goals live in report checks, not artefacts. Writes are attributed to your task automatically. Returns the created artefact with its id.","category": "Signals","feature": "signals","summary": "Append an artefact to a report",@@ -7816,7 +7816,7 @@}},"inbox-report-artefacts-list": {- "description": "List every artefact on a signal report — the full picture of why it exists and what has been done about it: `signal_finding` entries (the evidence behind the report), status judgments (safety / actionability / priority, repo_selection, suggested_reviewers — the newest row of each status type is the canonical status), and work-log entries (code references, commits, task runs, notes). Read this before re-judging a status or adding to the log. `ranking_score` entries are compact: each model keeps its scores, lifts, and head readability, but not its training metadata. Use inbox-report-artefacts-retrieve to read one in full.",+ "description": "List every artefact on an inbox report, the full picture of why it exists and what has been done about it: `signal_finding` entries (the evidence behind the report), status judgments (safety / actionability / priority, repo_selection, suggested_reviewers; the newest row of each status type is the canonical status), and work-log entries (code references, commits, task runs, notes). Read this before re-judging a status or adding to the log. `ranking_score` entries are compact: each model keeps its scores, lifts, and head readability, but not its training metadata. Use inbox-report-artefacts-retrieve to read one in full.","category": "Signals","feature": "signals","summary": "List a report's artefacts",@@ -7938,11 +7938,11 @@}},"inbox-reports-bulk-set-state": {- "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.",+ "description": "Transition up to 100 inbox reports to the same state in one call, the bulk form of `inbox-reports-set-state`. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the call returns 200 even on partial failure: read `results` (one entry per id, in request order) and the `transitioned_count`, `skipped_count`, `failed_count`, and `not_found_count` summary. An id whose current status does not allow the transition comes back as `skipped`, and the rest still go through.","category": "Signals","feature": "signals",- "summary": "Dismiss or snooze signal reports in bulk",- "title": "Dismiss or snooze signal reports in bulk",+ "summary": "Resolve, dismiss, or snooze inbox reports in bulk",+ "title": "Resolve, dismiss, or snooze inbox reports in bulk","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/bulk-state/"],"annotations": {@@ -7953,11 +7953,11 @@}},"inbox-reports-claim": {- "description": "Start, resume, or release work on a report. Returns assignee.claim_id for the work attempt. Pass claim_id on subsequent updates; stale or foreign claims are rejected. For internal task agents, claiming automatically records the task association. Task-run artefacts are read-only through the API. Another actor's active claim requires explicit takeover=true. Add pull_requests (an array of GitHub URLs) in the same call, including when starting work. Links are additive and retries are deduplicated. Use release=true to end ownership without removing PRs or history. A report resolves when every linked PR is closed or merged and at least one merged; it is suppressed when all closed without merging. Open, draft, unknown, or no PRs do not trigger completion. Repositories without a connected GitHub integration retain unknown state and require manual report resolution.",+ "description": "Start, resume, or release work on an inbox report. Returns `assignee.claim_id` for the work attempt; pass it on later updates. For internal task agents, claiming records the task association automatically. Add pull_requests (GitHub PR URLs) in the same call, including when you start work. A report resolves when every linked PR is closed or merged and at least one merged, and it is suppressed when all closed without merging. Open, draft, unknown, or no PRs do not complete it. Repositories without a connected GitHub integration keep unknown PR state, so resolve those reports with inbox-reports-set-state.","category": "Signals","feature": "signals",- "summary": "Update work on a signal report",- "title": "Update work on a signal report",+ "summary": "Update work on an inbox report",+ "title": "Update work on an inbox report","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/claim/"],"annotations": {@@ -7968,11 +7968,11 @@}},"inbox-reports-feedback-create": {- "description": "Record a person's thumbs up or thumbs down on a signal report, with their context for why: `positive` means thumbs up and `negative` means thumbs down. Pass the person's verdict, never your own interpretation of the report. The note is forwarded to the scout that authored or edited the report as steering context for its next run; the response says whether it was forwarded. This does not dismiss, resolve, or otherwise change the report's state. Each successful call can create a new steering note, so do not retry after a confirmed success.",+ "description": "Record a person's thumbs up or thumbs down on an inbox report, with their context for why. Pass the person's verdict, never your own interpretation of the report. The note is forwarded to the scout that authored or edited the report as steering context for its next run; the response says whether it was forwarded. This does not dismiss, resolve, or otherwise change the report's state. Each successful call can create a new steering note, so do not retry after a confirmed success.","category": "Signals","feature": "signals",- "summary": "Rate a signal report",- "title": "Rate a signal report",+ "summary": "Rate an inbox report",+ "title": "Rate an inbox report","required_scopes": ["task:read", "signal_scout:write", "llm_skill:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/feedback/"],"annotations": {@@ -8013,7 +8013,7 @@}},"inbox-reports-merge": {- "description": "Fold duplicate inbox reports into the one report that survives them, when the same issue landed in more than one report. The URL names the survivor and `source_report_ids` (1–10) names the duplicates. Pick the survivor deliberately: prefer the older report, and prefer the one holding an open implementation PR or an active claim. The sources' signals, work-log artefacts, pull requests, task runs and checks move onto the survivor, the survivor's signal counters take theirs on, and each source is archived with a 'duplicate of' link back. A source's open pull request stays open, because the survivor holds it after the move; any active claim on a source is released first, so re-claim the survivor if you were working on one. Titles and summaries are NOT combined, so follow with `inbox-reports-update` if the survivor needs a rewrite. Both ends must be a live report, and the whole call applies or none of it does: 409 and no writes when the survivor is resolved, or when a source is the survivor itself, is resolved or archived, is still being researched (`in_progress`), or carries more signals than one merge can move. A merged report keeps its URL but can never be restored, so merge only reports you are confident are the same issue, and use an `inbox-report-artefacts-create` `related_to` link when they are merely related.",+ "description": "Merge only reports you are confident describe the same issue: a merged report keeps its URL but can never be restored. For reports that are only related, add a `related_to` artefact with `inbox-report-artefacts-create` instead. The URL names the survivor. Prefer the older report, and prefer the one with an open implementation PR or an active claim. The sources' signals, work-log artefacts, pull requests, task runs, and checks move onto the survivor, which also takes on their signal counters. Each source is archived with a 'duplicate of' link back. A source's open pull request stays open under the survivor. An active claim on a source is released, so claim the survivor if you were working on one. Titles and summaries are not combined, so follow with `inbox-reports-update` if the survivor needs a rewrite. Returns 409 with no writes when the survivor is resolved, or when a source is still being researched (`in_progress`) or holds more signals than one merge can move.","category": "Signals","feature": "signals","summary": "Merge duplicate reports into one",@@ -8028,11 +8028,11 @@}},"inbox-reports-retrieve": {- "description": "Get a single signal report by ID. Returns the full report, including work_state, current assignee, and the attached pull request and its latest known state, plus typed impact metrics. Every metric includes a bounded live InsightVizNode/TrendsQuery built only from EventsNode or ActionsNode sources and may include an optional cached snapshot fallback. This call returns that stored content without executing the query. Consumers derive a BoldNumber whole-window headline and an ActionsBar longitudinal response, capped at 1,000 estimated points, through the normal analytics query path and cache. Queryless legacy or malformed metrics are always redacted. The report's full work log is readable via inbox-report-artefacts-list; read it before acting. The raw underlying signals require a HogQL query (see the 'signals' skill). Claim the report before doing work. A report may be claimed in potential, candidate, in_progress, pending_input, ready, or failed state. Its `ranking` field has the ranking model's predictions and the key of the model that made them, as described in inbox-reports-list.",+ "description": "Get a single inbox report by ID, with its work_state, current assignee, attached pull requests and their latest known state, and typed impact metrics. Each metric holds a bounded live Trends query built only from EventsNode or ActionsNode sources, and may hold a cached snapshot fallback. This call returns that stored content without running the query. Queryless legacy or malformed metrics are redacted. The `ranking` field has the ranking model's predictions and the key of the model that made them; inbox-ranking-outcomes-list explains them. Read the full work log with inbox-report-artefacts-list before acting. The raw underlying signals need a HogQL query (see the 'signals' skill). A report may be claimed in potential, candidate, in_progress, pending_input, ready, or failed state.","category": "Signals","feature": "signals",- "summary": "Get signal report",- "title": "Get signal report",+ "summary": "Get inbox report",+ "title": "Get inbox report","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/reports/{id}/"],"annotations": {@@ -8043,11 +8043,11 @@}},"inbox-reports-set-state": {- "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.",+ "description": "Transition one inbox report to a new state: 'resolved' when the work it asked for is done, 'suppressed' to dismiss it, or 'potential' to snooze it or restore it for later review. Dismissing or resolving closes the report's open implementation PR, if it has one. A resolved report never reopens: a recurrence starts a fresh report linked to it. `dismissal_reason` and `dismissal_note` are saved as a dismissal artefact, so the rationale survives later transitions. Reason codes need state 'suppressed' or 'resolved', not 'potential'. When the report only reached the wrong person, `inbox-reports-leave-reviewers` keeps it open for everyone else, while `wrong_assignee` closes it for everyone. Returns 409 when the report's current status does not allow the transition. To transition several reports, use `inbox-reports-bulk-set-state`.","category": "Signals","feature": "signals",- "summary": "Dismiss or snooze a signal report",- "title": "Dismiss or snooze a signal report",+ "summary": "Resolve, dismiss, or snooze an inbox report",+ "title": "Resolve, dismiss, or snooze an inbox report","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/state/"],"annotations": {@@ -8058,11 +8058,11 @@}},"inbox-reports-update": {- "description": "Edit the human-facing title and/or summary (description) of a signal report, addressed by id. Both fields are optional — pass only the ones you want to change, but supply at least one. Use this to clarify a report's title or rewrite its summary when you understand the underlying issue better than the auto-generated text does. Every other field (status, weights, priority/actionability judgments) is managed by the signals pipeline and cannot be set here — change a report's state with inbox-reports-set-state and its judgments by appending artefacts with inbox-report-artefacts-create. Returns the full updated report.",+ "description": "Edit the human-facing title or summary of an inbox report. Pass at least one. Use it when you understand the underlying issue better than the generated text does. The pipeline manages every other field: change the state with inbox-reports-set-state, and the judgments by appending artefacts with inbox-report-artefacts-create. Returns the full updated report.","category": "Signals","feature": "signals",- "summary": "Edit a signal report's title or summary",- "title": "Edit a signal report's title or summary",+ "summary": "Edit an inbox report's title or summary",+ "title": "Edit an inbox report's title or summary","required_scopes": ["task:write"],"api_operations": ["PATCH /api/projects/{project_id}/signals/reports/{id}/"],"annotations": {@@ -8153,11 +8153,11 @@"feature_flag": "signals-reviewer-exclusions-mcp"},"inbox-source-configs-create": {- "description": "Create a signal source config for the current project, switching an inbox signal source on. A source ties a `source_product` to a `source_type` and an `enabled` flag. Valid `source_product` values: llm_analytics, github, linear, zendesk, conversations, error_tracking, pganalyze, signals_scout, logs. Valid `source_type` values: evaluation_report, issue, ticket, issue_created, issue_reopened, issue_spiking, cross_source_issue, alert_state_change. To surface AI observability evaluation report findings in the inbox, create `source_product=llm_analytics`, `source_type=evaluation_report` — there is no per-evaluation-run source. The Signals scout source is ON BY DEFAULT — scout findings reach the inbox with no config row needed. The only reason to create a `source_product=signals_scout`, `source_type=cross_source_issue` row is to OPT OUT: create it with `enabled=false` (the per-scout `emit` flag is set separately via `scout-config-update`). There is at most one config per (source_product, source_type) per project; if one already exists, update it instead. For `source_product=linear`, `source_type=issue`, pass `config.linear_team_ids` (a list of Linear team ids from `integrations-linear-teams-retrieve`) so only issues from those Linear teams become signals; the warehouse still syncs the whole workspace. Omit it to use every team.",+ "description": "Switch an inbox source on for the current project. A source config ties a `source_product` and a `source_type` to an `enabled` flag and optional `config`. A project has at most one config per (source_product, source_type); if one exists, update it instead. To surface AI observability evaluation report findings, create `source_product=llm_analytics`, `source_type=evaluation_report`; there is no per-evaluation-run source. The scout source is on by default, so scout findings reach the inbox with no config row. Create a `source_product=signals_scout`, `source_type=cross_source_issue` row only to opt out, with `enabled=false`; set each scout's own `emit` flag with `scout-config-update`. Get Linear team ids from `integrations-linear-teams-retrieve`.","category": "Signals","feature": "signals",- "summary": "Create signal source config",- "title": "Create signal source config",+ "summary": "Create inbox source config",+ "title": "Create inbox source config","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/source_configs/"],"annotations": {@@ -8168,11 +8168,11 @@}},"inbox-source-configs-list": {- "description": "List the configured signal sources for the current project. A signal source ties a product (e.g. error_tracking, session_replay, github, linear, zendesk) and a source_type to an enabled flag and configuration. The 'status' field reflects the current state of the underlying data import or workflow (running, completed, failed) when applicable.",+ "description": "List the inbox source configs for the current project. Each ties a product (for example error_tracking, github, linear, zendesk) and a source_type to an enabled flag and configuration. `status` is the state of the underlying data import or workflow (running, completed, failed), when there is one.","category": "Signals","feature": "signals",- "summary": "List signal source configs",- "title": "List signal source configs",+ "summary": "List inbox source configs",+ "title": "List inbox source configs","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/source_configs/"],"annotations": {@@ -8183,11 +8183,11 @@}},"inbox-source-configs-partial-update": {- "description": "Partially update an existing signal source config by ID — typically to flip its `enabled` flag on or off, or to adjust its `config`. Only the fields you pass are changed. To turn the Signals scout source off for a project, set `enabled=false` on its `signals_scout` / `cross_source_issue` config. Use `config_set` to set individual top-level settings and `config_remove` to delete keys atomically, preserving unrelated settings. For guidance, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. For Linear teams, set `config_set.linear_team_ids`. The resulting full configuration is validated before saving. `config` still replaces the whole object; use it only for an intentional replacement. Do not combine `config` with `config_set` or `config_remove`, or set and remove the same key.",+ "description": "Partially update an inbox source config by ID, usually to flip `enabled` or adjust `config`. Only the fields you pass change. To turn the scout source off, set `enabled=false` on its `signals_scout` / `cross_source_issue` config. Prefer `config_set` and `config_remove` over `config`, which replaces the whole object. For example, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. The full resulting configuration is validated before saving.","category": "Signals","feature": "signals",- "summary": "Update signal source config",- "title": "Update signal source config",+ "summary": "Update inbox source config",+ "title": "Update inbox source config","required_scopes": ["task:write"],"api_operations": ["PATCH /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {@@ -8198,11 +8198,11 @@}},"inbox-source-configs-retrieve": {- "description": "Get a single signal source config by ID. Returns the full record including source_product, source_type, enabled flag, configuration JSON, and current status of the underlying data import or workflow.",+ "description": "Get one inbox source config by ID, with its full configuration and the status of the underlying data import or workflow.","category": "Signals","feature": "signals",- "summary": "Get signal source config",- "title": "Get signal source config",+ "summary": "Get inbox source config",+ "title": "Get inbox source config","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {@@ -8213,11 +8213,11 @@}},"inbox-source-configs-update": {- "description": "Replace an existing signal source config by ID (full update — `source_product` and `source_type` are required; `enabled` and `config` are optional and keep their current values if omitted). Prefer `inbox-source-configs-partial-update` when you only need to flip `enabled` or tweak `config`.",+ "description": "Replace an inbox source config by ID. `enabled` and `config` keep their current values when omitted. Prefer `inbox-source-configs-partial-update` to flip `enabled` or change part of `config`.","category": "Signals","feature": "signals",- "summary": "Replace signal source config",- "title": "Replace signal source config",+ "summary": "Replace inbox source config",+ "title": "Replace inbox source config","required_scopes": ["task:write"],"api_operations": ["PUT /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {diff --git a/services/mcp/schema/tool-definitions-all.json b/services/mcp/schema/tool-definitions-all.jsonindex 332e5973728a..402d70977758 100644--- a/services/mcp/schema/tool-definitions-all.json+++ b/services/mcp/schema/tool-definitions-all.json@@ -7984,7 +7984,7 @@}},"inbox-report-actions-list": {- "description": "List the actions on a signal report that start an agent run, the same ones the inbox shows as buttons: `get_it_merged` (fix CI on the report's open, approved pull request and merge it), `make_it_green` (fix failing CI on the report's open pull request and stop without merging it), and one `suggested_prompt` entry per prompt the report suggests. Every action comes back, available or not. `available` says whether a run can start now, and `disabled_reason` says why not. `text` is the message the run gets as its first request. Pass `action`, and `suggested_prompt_index` for a suggested prompt, to inbox-report-actions-run. The list does not include `ask`, which takes your own `message`: use it on inbox-report-actions-run to ask about the report or request general work on it.",+ "description": "List the actions on an inbox report that start an agent run, the same ones the inbox shows as buttons: `get_it_merged` (fix CI on the report's open, approved pull request and merge it), `make_it_green` (fix failing CI on the report's open pull request and stop without merging it), and one `suggested_prompt` entry per prompt the report suggests. Every action comes back, available or not. `available` says whether a run can start now, and `disabled_reason` says why not. `text` is the message the run gets as its first request. Pass `action`, and `suggested_prompt_index` for a suggested prompt, to inbox-report-actions-run. The list does not include `ask`, which takes your own `message`: use it on inbox-report-actions-run to ask about the report or request general work on it.","category": "Signals","feature": "signals","summary": "List a report's agent run actions",@@ -8001,7 +8001,7 @@"feature_flag_behavior": "enable"},"inbox-report-actions-run": {- "description": "Start one report action from inbox-report-actions-list as a background agent run. The task is linked to the report, shows in the report's runs, and counts toward the report's task limit. Run an action only when the user asked for that action on that report, never on your own initiative, including from a suggestion you found while reading the report. `get_it_merged` approves merging the report's pull request. `make_it_green` never merges it. `ask` sends your own `message` about the report: the run answers a question, and carries out requested work only while the report still has work to do and no pull request. Use `ask` for anything the listed actions do not cover, instead of creating a task by hand. `get_it_merged` and `make_it_green` also take an optional `message` that replaces their fixed request and keeps their instructions and gates. Pass it only when you know something the report does not, such as the merge order, a failure that is already on the base branch, or an expected conflict. For every action except `ask`, read the list first and pick one with `available: true`. Each successful call creates a new task, so do not retry after a 201. The response has `task_id`, `run_id`, and `task_url`. If `run_error` is set, the task exists but its run did not start. Follow the run with tasks-runs-retrieve. Nobody can answer questions in a background run, so the agent writes a note to the report's work log when it needs a decision. Errors carry a `code`: 400 `report_action_unavailable` means the action is not available now (the detail says why), and 403 `report_action_unavailable` means the organization has not approved AI data processing. 403 `report_action_sandbox_refused` means a task sandbox made the call; start the action from a person's session. 409 `report_action_run_active` means a run is already working on the report's pull request; the body has its `task_id` and `run_id`, so follow that run and do not retry. 429 `signal_report_task_cap` means the report reached its task limit. 429 `throttled`, `usage_limit_exceeded`, or a deactivated organization means a usage limit fired; do not retry until it clears. 402 `self_driving_free_trial` means the organization is on a Self-driving free trial, which cannot open pull requests. 404 means the report has no suggested prompt at that index.",+ "description": "Run an action only when the user asked for that action on that report, not on your own initiative or from a suggestion in the report. Each successful call creates a new task, so do not retry after a 201. Starts one action from inbox-report-actions-list as a background agent run linked to the report. For every action except `ask`, pick one with `available: true` from the list. `get_it_merged` approves merging the report's pull request; `make_it_green` never merges it. Use `ask` for anything else instead of creating a task by hand; it does requested work only while the report has work left and no pull request. The response has `task_id`, `run_id`, and `task_url`; follow the run with tasks-runs-retrieve. If `run_error` is set, the task exists but its run did not start. The run cannot ask questions, so it writes a note to the report's work log when it needs a decision. 409 `report_action_run_active` means a run already works on the pull request: follow its `task_id` and `run_id`. 403 `report_action_sandbox_refused` means start the action from a person's session. 402 and 429 mean a trial, task, or usage limit: do not retry until it clears. For `report_action_unavailable`, the detail says why.","category": "Signals","feature": "signals","summary": "Run a report action as an agent task",@@ -8018,7 +8018,7 @@"feature_flag_behavior": "enable"},"inbox-report-artefacts-create": {- "description": "Append an artefact to a signal report so it reads as a living document. Everything is append-only. Log types accumulate — `code_reference` (a contiguous span of source lines, at most 20: file_path, start_line, end_line, contents, relevance_note; a single line is just start_line == end_line), `commit` (one commit that has already been pushed to a remote branch: repository, branch, commit_sha, message — usually recorded automatically when you push via git_signed_commit. Only create one yourself for a commit pushed to a remote by other means; never record a commit that is not on a remote branch — an unpushed or local-only commit is always a mistake), `note` (free-form: note). Follow-up goals live in report checks, not artefacts. Status types are latest-wins — appending a new version supersedes the previous one as the report's canonical status: `priority_judgment` (explanation, priority P0–P4), `actionability_judgment` (explanation, actionability, already_addressed), `safety_judgment` (choice), `repo_selection` (repository, reason), `suggested_reviewers` (a list of {github_login}), `source_suggestion` (product, reason: a product the project does not use that would have given this report better evidence; the inbox hides it once the product is in use). Status judgments are consequential, not advisory: the canonical priority/actionability steer what humans and agents pick up next, and PostHog's automation uses them when deciding which reports to act on. `content` is a JSON object matching the chosen type and is validated against its schema. Writes are attributed to your task automatically. Pass claim_id to associate the work with your current claim; stale or foreign claims are rejected. Returns the created artefact including its id.",+ "description": "Append an artefact to an inbox report so it reads as a living document. Everything is append-only. Status judgments are consequential, not advisory: the canonical priority and actionability steer what people and agents pick up next, and PostHog's automation uses them to decide which reports to act on. Follow-up goals live in report checks, not artefacts. Writes are attributed to your task automatically. Returns the created artefact with its id.","category": "Signals","feature": "signals","summary": "Append an artefact to a report",@@ -8048,7 +8048,7 @@}},"inbox-report-artefacts-list": {- "description": "List every artefact on a signal report — the full picture of why it exists and what has been done about it: `signal_finding` entries (the evidence behind the report), status judgments (safety / actionability / priority, repo_selection, suggested_reviewers — the newest row of each status type is the canonical status), and work-log entries (code references, commits, task runs, notes). Read this before re-judging a status or adding to the log. `ranking_score` entries are compact: each model keeps its scores, lifts, and head readability, but not its training metadata. Use inbox-report-artefacts-retrieve to read one in full.",+ "description": "List every artefact on an inbox report, the full picture of why it exists and what has been done about it: `signal_finding` entries (the evidence behind the report), status judgments (safety / actionability / priority, repo_selection, suggested_reviewers; the newest row of each status type is the canonical status), and work-log entries (code references, commits, task runs, notes). Read this before re-judging a status or adding to the log. `ranking_score` entries are compact: each model keeps its scores, lifts, and head readability, but not its training metadata. Use inbox-report-artefacts-retrieve to read one in full.","category": "Signals","feature": "signals","summary": "List a report's artefacts",@@ -8170,11 +8170,11 @@}},"inbox-reports-bulk-set-state": {- "description": "Transition many signal reports to the same state in one call — the bulk form of `inbox-reports-set-state`, for clearing, snoozing, or resolving a batch of inbox reports without one request per report. Pass `ids` (1–100 report ids) and a `state` ('resolved' when the requested work is done, 'suppressed' to dismiss, 'potential' to snooze/restore); the optional `dismissal_reason` (same canonical codes as the single-report tool, including `wrong_assignee` and `wrong_repo`), `dismissal_note`, `corrected_repository` (only with `wrong_repo`), and `snooze_for` apply to every id. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the whole call returns 200 even on partial failure: inspect `results` (one entry per id, in request order) and the `transitioned_count` / `skipped_count` / `failed_count` / `not_found_count` summary. An id whose transition isn't allowed from its current status comes back as `skipped` (the single-report 409) while the rest still go through.",+ "description": "Transition up to 100 inbox reports to the same state in one call, the bulk form of `inbox-reports-set-state`. Dismissing or resolving closes each report's open implementation PR, if it has one. Each id is processed independently, so the call returns 200 even on partial failure: read `results` (one entry per id, in request order) and the `transitioned_count`, `skipped_count`, `failed_count`, and `not_found_count` summary. An id whose current status does not allow the transition comes back as `skipped`, and the rest still go through.","category": "Signals","feature": "signals",- "summary": "Dismiss or snooze signal reports in bulk",- "title": "Dismiss or snooze signal reports in bulk",+ "summary": "Resolve, dismiss, or snooze inbox reports in bulk",+ "title": "Resolve, dismiss, or snooze inbox reports in bulk","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/bulk-state/"],"annotations": {@@ -8185,11 +8185,11 @@}},"inbox-reports-claim": {- "description": "Start, resume, or release work on a report. Returns assignee.claim_id for the work attempt. Pass claim_id on subsequent updates; stale or foreign claims are rejected. For internal task agents, claiming automatically records the task association. Task-run artefacts are read-only through the API. Another actor's active claim requires explicit takeover=true. Add pull_requests (an array of GitHub URLs) in the same call, including when starting work. Links are additive and retries are deduplicated. Use release=true to end ownership without removing PRs or history. A report resolves when every linked PR is closed or merged and at least one merged; it is suppressed when all closed without merging. Open, draft, unknown, or no PRs do not trigger completion. Repositories without a connected GitHub integration retain unknown state and require manual report resolution.",+ "description": "Start, resume, or release work on an inbox report. Returns `assignee.claim_id` for the work attempt; pass it on later updates. For internal task agents, claiming records the task association automatically. Add pull_requests (GitHub PR URLs) in the same call, including when you start work. A report resolves when every linked PR is closed or merged and at least one merged, and it is suppressed when all closed without merging. Open, draft, unknown, or no PRs do not complete it. Repositories without a connected GitHub integration keep unknown PR state, so resolve those reports with inbox-reports-set-state.","category": "Signals","feature": "signals",- "summary": "Update work on a signal report",- "title": "Update work on a signal report",+ "summary": "Update work on an inbox report",+ "title": "Update work on an inbox report","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/claim/"],"annotations": {@@ -8200,11 +8200,11 @@}},"inbox-reports-feedback-create": {- "description": "Record a person's thumbs up or thumbs down on a signal report, with their context for why: `positive` means thumbs up and `negative` means thumbs down. Pass the person's verdict, never your own interpretation of the report. The note is forwarded to the scout that authored or edited the report as steering context for its next run; the response says whether it was forwarded. This does not dismiss, resolve, or otherwise change the report's state. Each successful call can create a new steering note, so do not retry after a confirmed success.",+ "description": "Record a person's thumbs up or thumbs down on an inbox report, with their context for why. Pass the person's verdict, never your own interpretation of the report. The note is forwarded to the scout that authored or edited the report as steering context for its next run; the response says whether it was forwarded. This does not dismiss, resolve, or otherwise change the report's state. Each successful call can create a new steering note, so do not retry after a confirmed success.","category": "Signals","feature": "signals",- "summary": "Rate a signal report",- "title": "Rate a signal report",+ "summary": "Rate an inbox report",+ "title": "Rate an inbox report","required_scopes": ["task:read", "signal_scout:write", "llm_skill:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/feedback/"],"annotations": {@@ -8245,7 +8245,7 @@}},"inbox-reports-merge": {- "description": "Fold duplicate inbox reports into the one report that survives them, when the same issue landed in more than one report. The URL names the survivor and `source_report_ids` (1–10) names the duplicates. Pick the survivor deliberately: prefer the older report, and prefer the one holding an open implementation PR or an active claim. The sources' signals, work-log artefacts, pull requests, task runs and checks move onto the survivor, the survivor's signal counters take theirs on, and each source is archived with a 'duplicate of' link back. A source's open pull request stays open, because the survivor holds it after the move; any active claim on a source is released first, so re-claim the survivor if you were working on one. Titles and summaries are NOT combined, so follow with `inbox-reports-update` if the survivor needs a rewrite. Both ends must be a live report, and the whole call applies or none of it does: 409 and no writes when the survivor is resolved, or when a source is the survivor itself, is resolved or archived, is still being researched (`in_progress`), or carries more signals than one merge can move. A merged report keeps its URL but can never be restored, so merge only reports you are confident are the same issue, and use an `inbox-report-artefacts-create` `related_to` link when they are merely related.",+ "description": "Merge only reports you are confident describe the same issue: a merged report keeps its URL but can never be restored. For reports that are only related, add a `related_to` artefact with `inbox-report-artefacts-create` instead. The URL names the survivor. Prefer the older report, and prefer the one with an open implementation PR or an active claim. The sources' signals, work-log artefacts, pull requests, task runs, and checks move onto the survivor, which also takes on their signal counters. Each source is archived with a 'duplicate of' link back. A source's open pull request stays open under the survivor. An active claim on a source is released, so claim the survivor if you were working on one. Titles and summaries are not combined, so follow with `inbox-reports-update` if the survivor needs a rewrite. Returns 409 with no writes when the survivor is resolved, or when a source is still being researched (`in_progress`) or holds more signals than one merge can move.","category": "Signals","feature": "signals","summary": "Merge duplicate reports into one",@@ -8260,11 +8260,11 @@}},"inbox-reports-retrieve": {- "description": "Get a single signal report by ID. Returns the full report, including work_state, current assignee, and the attached pull request and its latest known state, plus typed impact metrics. Every metric includes a bounded live InsightVizNode/TrendsQuery built only from EventsNode or ActionsNode sources and may include an optional cached snapshot fallback. This call returns that stored content without executing the query. Consumers derive a BoldNumber whole-window headline and an ActionsBar longitudinal response, capped at 1,000 estimated points, through the normal analytics query path and cache. Queryless legacy or malformed metrics are always redacted. The report's full work log is readable via inbox-report-artefacts-list; read it before acting. The raw underlying signals require a HogQL query (see the 'signals' skill). Claim the report before doing work. A report may be claimed in potential, candidate, in_progress, pending_input, ready, or failed state. Its `ranking` field has the ranking model's predictions and the key of the model that made them, as described in inbox-reports-list.",+ "description": "Get a single inbox report by ID, with its work_state, current assignee, attached pull requests and their latest known state, and typed impact metrics. Each metric holds a bounded live Trends query built only from EventsNode or ActionsNode sources, and may hold a cached snapshot fallback. This call returns that stored content without running the query. Queryless legacy or malformed metrics are redacted. The `ranking` field has the ranking model's predictions and the key of the model that made them; inbox-ranking-outcomes-list explains them. Read the full work log with inbox-report-artefacts-list before acting. The raw underlying signals need a HogQL query (see the 'signals' skill). A report may be claimed in potential, candidate, in_progress, pending_input, ready, or failed state.","category": "Signals","feature": "signals",- "summary": "Get signal report",- "title": "Get signal report",+ "summary": "Get inbox report",+ "title": "Get inbox report","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/reports/{id}/"],"annotations": {@@ -8275,11 +8275,11 @@}},"inbox-reports-set-state": {- "description": "Transition a single signal report to a new state. Use 'resolved' when the work this report asked for has been done (e.g. you fixed the issue it describes), 'suppressed' to dismiss the report from the inbox (the user has reviewed it and decided no action is needed), or 'potential' to snooze/restore it back into the pipeline for later review. Resolving is allowed from ready, pending_input, or failed, or from a suppressed report whose previous status was ready, pending_input, failed, or resolved. Repeat resolution succeeds. Other statuses return 409. Fixed reasons require state='suppressed' or state='resolved', not 'potential'. Dismissing or resolving closes the report's open implementation PR, if it has one; a resolved report never reopens, and a recurrence starts a fresh report linked to it. Optionally include a `dismissal_reason` — a canonical code from the inbox UI (`fixed_outside_posthog`, `pr_merged`, `already_fixed`, `report_unclear`, `analysis_wrong`, `wrong_assignee`, `wrong_repo`, `wontfix_intentional`, `wontfix_irrelevant`, `other`), so it renders as a labelled chip rather than a raw string. With state='resolved' use `fixed_outside_posthog` when the fix landed without a pull request, `pr_merged` when a pull request with the fix was merged but did not resolve the report on its own, or `already_fixed` when it was fixed before the report was filed; the other codes describe a dismissal. Use `wrong_assignee` when the report reached the wrong person or team. Use `wrong_repo` when the agent picked the wrong repository for this report, and pass `corrected_repository` (an 'owner/repo' string, only allowed with `wrong_repo`) to name the one it should have used — the correction is recorded and fed into future repository selection for this project. Use `other` plus a `dismissal_note` (free-form text, up to 4000 chars) for anything that doesn't fit a code. Both are persisted as a DISMISSAL artefact on the report so the rationale survives later transitions. Returns 409 if the transition is not allowed from the report's current status. To transition several reports at once, use `inbox-reports-bulk-set-state` instead of calling this per report.",+ "description": "Transition one inbox report to a new state: 'resolved' when the work it asked for is done, 'suppressed' to dismiss it, or 'potential' to snooze it or restore it for later review. Dismissing or resolving closes the report's open implementation PR, if it has one. A resolved report never reopens: a recurrence starts a fresh report linked to it. `dismissal_reason` and `dismissal_note` are saved as a dismissal artefact, so the rationale survives later transitions. Reason codes need state 'suppressed' or 'resolved', not 'potential'. When the report only reached the wrong person, `inbox-reports-leave-reviewers` keeps it open for everyone else, while `wrong_assignee` closes it for everyone. Returns 409 when the report's current status does not allow the transition. To transition several reports, use `inbox-reports-bulk-set-state`.","category": "Signals","feature": "signals",- "summary": "Dismiss or snooze a signal report",- "title": "Dismiss or snooze a signal report",+ "summary": "Resolve, dismiss, or snooze an inbox report",+ "title": "Resolve, dismiss, or snooze an inbox report","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/reports/{id}/state/"],"annotations": {@@ -8290,11 +8290,11 @@}},"inbox-reports-update": {- "description": "Edit the human-facing title and/or summary (description) of a signal report, addressed by id. Both fields are optional — pass only the ones you want to change, but supply at least one. Use this to clarify a report's title or rewrite its summary when you understand the underlying issue better than the auto-generated text does. Every other field (status, weights, priority/actionability judgments) is managed by the signals pipeline and cannot be set here — change a report's state with inbox-reports-set-state and its judgments by appending artefacts with inbox-report-artefacts-create. Returns the full updated report.",+ "description": "Edit the human-facing title or summary of an inbox report. Pass at least one. Use it when you understand the underlying issue better than the generated text does. The pipeline manages every other field: change the state with inbox-reports-set-state, and the judgments by appending artefacts with inbox-report-artefacts-create. Returns the full updated report.","category": "Signals","feature": "signals",- "summary": "Edit a signal report's title or summary",- "title": "Edit a signal report's title or summary",+ "summary": "Edit an inbox report's title or summary",+ "title": "Edit an inbox report's title or summary","required_scopes": ["task:write"],"api_operations": ["PATCH /api/projects/{project_id}/signals/reports/{id}/"],"annotations": {@@ -8385,11 +8385,11 @@"feature_flag": "signals-reviewer-exclusions-mcp"},"inbox-source-configs-create": {- "description": "Create a signal source config for the current project, switching an inbox signal source on. A source ties a `source_product` to a `source_type` and an `enabled` flag. Valid `source_product` values: llm_analytics, github, linear, zendesk, conversations, error_tracking, pganalyze, signals_scout, logs. Valid `source_type` values: evaluation_report, issue, ticket, issue_created, issue_reopened, issue_spiking, cross_source_issue, alert_state_change. To surface AI observability evaluation report findings in the inbox, create `source_product=llm_analytics`, `source_type=evaluation_report` — there is no per-evaluation-run source. The Signals scout source is ON BY DEFAULT — scout findings reach the inbox with no config row needed. The only reason to create a `source_product=signals_scout`, `source_type=cross_source_issue` row is to OPT OUT: create it with `enabled=false` (the per-scout `emit` flag is set separately via `scout-config-update`). There is at most one config per (source_product, source_type) per project; if one already exists, update it instead. For `source_product=linear`, `source_type=issue`, pass `config.linear_team_ids` (a list of Linear team ids from `integrations-linear-teams-retrieve`) so only issues from those Linear teams become signals; the warehouse still syncs the whole workspace. Omit it to use every team.",+ "description": "Switch an inbox source on for the current project. A source config ties a `source_product` and a `source_type` to an `enabled` flag and optional `config`. A project has at most one config per (source_product, source_type); if one exists, update it instead. To surface AI observability evaluation report findings, create `source_product=llm_analytics`, `source_type=evaluation_report`; there is no per-evaluation-run source. The scout source is on by default, so scout findings reach the inbox with no config row. Create a `source_product=signals_scout`, `source_type=cross_source_issue` row only to opt out, with `enabled=false`; set each scout's own `emit` flag with `scout-config-update`. Get Linear team ids from `integrations-linear-teams-retrieve`.","category": "Signals","feature": "signals",- "summary": "Create signal source config",- "title": "Create signal source config",+ "summary": "Create inbox source config",+ "title": "Create inbox source config","required_scopes": ["task:write"],"api_operations": ["POST /api/projects/{project_id}/signals/source_configs/"],"annotations": {@@ -8400,11 +8400,11 @@}},"inbox-source-configs-list": {- "description": "List the configured signal sources for the current project. A signal source ties a product (e.g. error_tracking, session_replay, github, linear, zendesk) and a source_type to an enabled flag and configuration. The 'status' field reflects the current state of the underlying data import or workflow (running, completed, failed) when applicable.",+ "description": "List the inbox source configs for the current project. Each ties a product (for example error_tracking, github, linear, zendesk) and a source_type to an enabled flag and configuration. `status` is the state of the underlying data import or workflow (running, completed, failed), when there is one.","category": "Signals","feature": "signals",- "summary": "List signal source configs",- "title": "List signal source configs",+ "summary": "List inbox source configs",+ "title": "List inbox source configs","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/source_configs/"],"annotations": {@@ -8415,11 +8415,11 @@}},"inbox-source-configs-partial-update": {- "description": "Partially update an existing signal source config by ID — typically to flip its `enabled` flag on or off, or to adjust its `config`. Only the fields you pass are changed. To turn the Signals scout source off for a project, set `enabled=false` on its `signals_scout` / `cross_source_issue` config. Use `config_set` to set individual top-level settings and `config_remove` to delete keys atomically, preserving unrelated settings. For guidance, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. For Linear teams, set `config_set.linear_team_ids`. The resulting full configuration is validated before saving. `config` still replaces the whole object; use it only for an intentional replacement. Do not combine `config` with `config_set` or `config_remove`, or set and remove the same key.",+ "description": "Partially update an inbox source config by ID, usually to flip `enabled` or adjust `config`. Only the fields you pass change. To turn the scout source off, set `enabled=false` on its `signals_scout` / `cross_source_issue` config. Prefer `config_set` and `config_remove` over `config`, which replaces the whole object. For example, set `config_set.steering` and remove `default_not_actionable` with `config_remove`. The full resulting configuration is validated before saving.","category": "Signals","feature": "signals",- "summary": "Update signal source config",- "title": "Update signal source config",+ "summary": "Update inbox source config",+ "title": "Update inbox source config","required_scopes": ["task:write"],"api_operations": ["PATCH /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {@@ -8430,11 +8430,11 @@}},"inbox-source-configs-retrieve": {- "description": "Get a single signal source config by ID. Returns the full record including source_product, source_type, enabled flag, configuration JSON, and current status of the underlying data import or workflow.",+ "description": "Get one inbox source config by ID, with its full configuration and the status of the underlying data import or workflow.","category": "Signals","feature": "signals",- "summary": "Get signal source config",- "title": "Get signal source config",+ "summary": "Get inbox source config",+ "title": "Get inbox source config","required_scopes": ["task:read"],"api_operations": ["GET /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {@@ -8445,11 +8445,11 @@}},"inbox-source-configs-update": {- "description": "Replace an existing signal source config by ID (full update — `source_product` and `source_type` are required; `enabled` and `config` are optional and keep their current values if omitted). Prefer `inbox-source-configs-partial-update` when you only need to flip `enabled` or tweak `config`.",+ "description": "Replace an inbox source config by ID. `enabled` and `config` keep their current values when omitted. Prefer `inbox-source-configs-partial-update` to flip `enabled` or change part of `config`.","category": "Signals","feature": "signals",- "summary": "Replace signal source config",- "title": "Replace signal source config",+ "summary": "Replace inbox source config",+ "title": "Replace inbox source config","required_scopes": ["task:write"],"api_operations": ["PUT /api/projects/{project_id}/signals/source_configs/{id}/"],"annotations": {diff --git a/services/mcp/src/tools/generated/signals.ts b/services/mcp/src/tools/generated/signals.tsindex f9940568b3df..226170f8b63a 100644--- a/services/mcp/src/tools/generated/signals.ts+++ b/services/mcp/src/tools/generated/signals.ts@@ -192,7 +192,13 @@ const inboxReportActionsRun = (): ToolBase<const InboxReportArtefactsCreateSchema = () => {const SignalsReportArtefactsCreateBody = orvalSchemas.SignalsReportArtefactsCreateBody()const SignalsReportArtefactsCreateParams = orvalSchemas.SignalsReportArtefactsCreateParams()- return SignalsReportArtefactsCreateParams.omit({ project_id: true }).extend(SignalsReportArtefactsCreateBody.shape)+ return SignalsReportArtefactsCreateParams.omit({ project_id: true })+ .extend(SignalsReportArtefactsCreateBody.shape)+ .extend({+ content: SignalsReportArtefactsCreateBody.shape['content'].describe(+ 'The artefact payload as a JSON object or array, validated against the schema for `artefact_type`. `code_reference`: file_path, start_line, end_line, contents, relevance_note, for a contiguous span of at most 20 source lines (a single line has start_line equal to end_line). `commit`: repository, branch, commit_sha, message, for one commit already pushed to a remote branch. git_signed_commit usually records it for you, so create one only for a commit pushed by other means, and never for an unpushed or local-only commit. `note`: note, free-form. `priority_judgment`: explanation, priority (P0–P4). `actionability_judgment`: explanation, actionability, already_addressed. `safety_judgment`: choice. `repo_selection`: repository, reason. `suggested_reviewers`: a list of {github_login}. `source_suggestion`: product, reason, for a product the project does not use that would have given this report better evidence; the inbox hides it once the product is in use.'+ ),+ })}const inboxReportArtefactsCreate = (): ToolBase<diff --git a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-report-artefacts-create.json b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-report-artefacts-create.jsonindex ce22c8c497a0..d15f93a96bf8 100644--- a/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-report-artefacts-create.json+++ b/services/mcp/tests/unit/__snapshots__/tool-schemas/inbox-report-artefacts-create.json@@ -10,7 +10,7 @@"type": "string"},"content": {- "description": "The artefact payload as a JSON object or array; shape depends on artefact_type and is validated against its schema."+ "description": "The artefact payload as a JSON object or array, validated against the schema for `artefact_type`. `code_reference`: file_path, start_line, end_line, contents, relevance_note, for a contiguous span of at most 20 source lines (a single line has start_line equal to end_line). `commit`: repository, branch, commit_sha, message, for one commit already pushed to a remote branch. git_signed_commit usually records it for you, so create one only for a commit pushed by other means, and never for an unpushed or local-only commit. `note`: note, free-form. `priority_judgment`: explanation, priority (P0–P4). `actionability_judgment`: explanation, actionability, already_addressed. `safety_judgment`: choice. `repo_selection`: repository, reason. `suggested_reviewers`: a list of {github_login}. `source_suggestion`: product, reason, for a product the project does not use that would have given this report better evidence; the inbox hides it once the product is in use."},"expected_reviewers": {"description": "Report reviewer_assignment.state read before selection began. Required when reviewer corrections are enabled.",