Chat Tools
Complete reference for every tool available in Critique Chat, including parameters, side effects, and availability conditions.
Critique Chat exposes a set of tools that ground conversational output in real data. The agent calls tools automatically based on the question, but understanding what each tool does helps you get better answers.
Tool categories
Tools are grouped by what they interact with:
| Category | Tools |
|---|---|
| Repository | searchRepository, inspectPullRequest, inspectWorkflowRun |
| External docs | searchLibraryDocs, searchDocs, fetchDocPage |
| Workspace state | getWorkspaceStatus, getActiveContext, searchSharedMemory |
| Review runs | listRecentReviewRuns, inspectReviewRun |
| Remedy | inspectRemedyRuntime, startRemedy, checkRemedyStatus |
| Agent handoff | prepareClaudeCodeHandoff |
| GitHub actions | createGitHubIssue, commentOnPullRequest |
searchRepository
Explore the selected GitHub repository using warm snapshot retrieval when available, with GitHub code search as fallback.
| Property | Value |
|---|---|
| Requires repository | Yes |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Search query (min 1 char) |
When to use: Before making repository-specific claims, tracing implementation details, or locating files and code paths.
When not to use: When no repository is selected or the answer is purely about product or runtime state.
Result shape: summary, relevant_files[], code_context[], search_notes, retrieval, execution
inspectPullRequest
Fetch a GitHub pull request: metadata, changed files, merge and check summary, and review thread context for the head commit.
| Property | Value |
|---|---|
| Requires repository | Yes |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires GitHub App installation access |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
pullNumber | integer | Yes | — | PR number (min 1) |
includePatch | boolean | No | false | Include full patch content |
maxFiles | integer | No | 30 | Max files to return (1–100) |
When to use: When the user references a PR number, PR URL, or asks about changes, blockers, open comments, or CI status for a specific PR.
When not to use: For generic repo exploration without a PR — use searchRepository instead.
Result shape: pull, files[], issueCommentsSummary[], reviewCommentsSummary[], checksSummary, links[]
inspectWorkflowRun
Load a GitHub Actions workflow run or job: status, conclusion, associated commit, steps, and capped log excerpts.
| Property | Value |
|---|---|
| Requires repository | Yes |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires GitHub App installation access |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
mode | 'run' or 'job' | Yes | — | Whether to fetch a full run or a specific job |
runId | integer | No | — | Workflow run ID (min 1) |
jobId | integer | No | — | Job ID (min 1) |
logCharsPerJob | integer | No | 12000 | Max log chars per job (0–50000) |
logMaxChars | integer | No | 24000 | Global log char cap (0–100000) |
When to use: When debugging CI failures, flaky tests, or deployment workflows tied to a known run or job ID.
When not to use: For source-code-only questions or when no run/job identifier is known.
Result shape: run, jobs[], logExcerpts[], artifactsSummary[]
searchLibraryDocs
Retrieve version-aware documentation snippets for a named library or framework.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires Context7 integration |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
libraryName | string | Yes | — | Library or framework name (max 200 chars) |
topic | string | Yes | — | What to look up (max 2000 chars) |
version | string | No | — | Specific version to target (max 80 chars) |
When to use: For framework or library API questions where generic web search is noisy or version-specific behavior matters.
When not to use: For arbitrary doc URLs or when the library docs integration is unavailable.
Result shape: libraryId, version, snippets[], sourceUrls[]
searchDocs
Search docs and web pages through Firecrawl and return relevant URLs for current documentation or vendor facts.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires Firecrawl integration |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
query | string | Yes | — | Search query (min 1 char) |
domains | string[] | No | — | Restrict search to these domains (max 6) |
limit | integer | No | 5 | Max results (1–8) |
When to use: For current external docs, vendor APIs, pricing, or product facts not guaranteed by the local repository.
When not to use: For repository-local answers or when Firecrawl is unavailable.
Result shape: hits[], creditsUsed
fetchDocPage
Fetch and scrape a specific documentation page through Firecrawl and return markdown content plus metadata.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires Firecrawl integration |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
url | string (URL) | Yes | The page URL to fetch |
When to use: After a docs search when you need the full contents of a specific page before answering.
When not to use: Unless a specific allowed URL is already known.
Result shape: url, title, description, markdown
getWorkspaceStatus
Read GitHub connection, installation, repository, and automation readiness state for this user.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters: None.
When to use: For questions about setup, GitHub connectivity, installations, or review readiness.
When not to use: For repo code questions or external docs.
Result shape: githubLinked, installations, activeRepositories, reviewRuns, automationReady, nextStep
getActiveContext
Read the current durable context bundle for workspace, runtime, and repository state.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
reviewRunId | string | No | Scope context to a specific review run |
When to use: Before answering questions about current product truth, runtime state, or accumulated known context.
When not to use: As a replacement for repo search or docs search.
Result shape: summary, documents[]
searchSharedMemory
Search persisted board entries and memory chunks across chat, review runs, and repository memory.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
query | string | Yes | — | Search query (min 1 char) |
reviewRunId | string | No | — | Scope to a specific review run |
limit | integer | No | 6 | Max results (1–10) |
When to use: When the user asks about earlier findings, persisted learnings, or prior run context.
When not to use: For current repo implementation details when fresh repository search is needed.
Result shape: results[]
listRecentReviewRuns
List recent review runs visible to the current user.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
limit | integer | No | 5 | Max runs to return (1–8) |
When to use: When the user asks about recent PR reviews or wants a run to inspect.
Result shape: reviewRun[]
inspectReviewRun
Inspect a specific review run, including findings and latest Remedy state.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
reviewRunId | string | Yes | The review run ID to inspect |
When to use: When the user names or selects a review run and needs its details.
When not to use: Without a run identifier.
Result shape: Review run snapshot with findings and Remedy state.
inspectRemedyRuntime
Explain how Remedy executes today and which runtime surface it uses.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters: None.
When to use: When the user asks about Remedy architecture or current execution behavior.
When not to use: To start Remedy — use startRemedy instead.
Result shape: Remedy runtime summary.
startRemedy
Queue a Remedy run for a specific review run. Shows a confirmation card before executing — it does not auto-start.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Write |
| Renderer | Card |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
reviewRunId | string | No | Review run to remediate (uses selected repo if omitted) |
suggestedInstructions | string | No | Pre-fill the edit prompt in the confirmation dialog (max 1000 chars) |
When to use: Only when the user explicitly asks to start Remedy.
When not to use: Speculatively or as part of ordinary information gathering.
Result shape: remedyRunId, status, executionSurface
Confirmation required
startRemedy emits a confirmation card. The user must approve before execution begins. No code is modified without explicit consent.
checkRemedyStatus
Check the current status of a running or completed Remedy run, including recent progress events.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
remedyRunId | string | Yes | The Remedy run ID to check |
When to use: When the user asks about the status of a Remedy run, or to check if a queued or running Remedy has completed.
When not to use: To start Remedy — use startRemedy instead.
Result shape: remedyRunId, status, recentEvents, commitUrl, streamUrl
prepareClaudeCodeHandoff
Compile the current Critique Chat thread into a detailed Markdown handoff and send it through the Anthropic Messages API using the operator's own API key.
| Property | Value |
|---|---|
| Requires repository | No |
| Side effects | Read |
| Renderer | Card |
| Availability | Requires user Anthropic API key in Settings |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
taskFocus | string | No | — | Extra instructions or scope emphasis for the handoff (max 8000 chars) |
maxTranscriptMessages | integer | No | 48 | How many recent messages to include (4–120) |
When to use: When the user explicitly wants Claude Code, a coding agent, or an autonomous fixer to take over.
When not to use: For ordinary Q&A, repo search, or when the user has not asked for an agent handoff.
Result shape: handoffMarkdown, anthropicModel, transcriptStats
createGitHubIssue
Draft a GitHub issue from the current chat context and show a confirmation card before posting.
| Property | Value |
|---|---|
| Requires repository | Yes |
| Side effects | Write |
| Renderer | Card |
| Availability | Requires GitHub App installation access |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
title | string | Yes | — | Issue title (max 240 chars) |
body | string | Yes | — | Issue body in Markdown (max 12000 chars) |
labels | string[] | No | [] | Labels to apply (max 12, each max 60 chars) |
When to use: When the user explicitly asks to open an issue, file a bug, or create a GitHub issue from this conversation.
When not to use: For ordinary summaries — do not auto-post without explicit user intent.
Confirmation required
Like startRemedy, this tool shows a confirmation card. The issue is only created after the user approves.
commentOnPullRequest
Draft a PR comment from the current chat context and show a confirmation card before posting.
| Property | Value |
|---|---|
| Requires repository | Yes |
| Side effects | Write |
| Renderer | Card |
| Availability | Requires GitHub App installation access |
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
pullNumber | integer | Yes | — | PR number |
body | string | Yes | — | Comment body in Markdown (max 12000 chars) |
path | string | No | — | File path for line-specific comments (max 500 chars) |
line | integer | No | — | Line number for line-specific comments |
side | 'LEFT' or 'RIGHT' | No | — | Diff side for line-specific comments |
commitSha | string | No | — | Commit SHA (required for line-specific comments, min 7 chars) |
Supports both general PR comments and file-line-specific review comments.
When to use: When the user explicitly asks to post findings or feedback onto a pull request from chat.
When not to use: For private notes, ordinary summaries, or speculative posting without explicit user intent.
Hidden tools
Two additional tools are always registered but do not appear in the tool manifest or UI:
-
promoteReviewRunLearning— Promote a review run into repository memory after a human explicitly decides the run contains reusable learning. Parameters:reviewRunId(required),rationale(required, min 8 chars). -
promoteRemedyOutcome— Promote a completed Remedy outcome into repository memory when the result should inform future runs. Parameters:remedyRunId(required),rationale(optional, min 8 chars).
These tools write to repository memory and are not directly invocable through the chat UI.