Clarvis

English

Español (España)
Português (Brasil)

English

Español (España)
Português (Brasil)

Appearance

Clarvis v0.1.1.

Tasks ​

View tasks from an external tracker and choose one for Clarvis to work on.

Tasks connects Clarvis to an external issue tracker. You can browse its work items in one board and use Clarvis tools to work with them. The tasks stay in the external service; Clarvis does not keep a second task database.

Configure a task provider ​

Tasks uses a named MCP server that implements the clarvis.tasks.v2 protocol. After declaring and connecting that server, add the provider to global or workspace settings.json:

json
{
  "tasks": {
    "provider": {
      "kind": "mcp",
      "server": "tracker:tasks",
      "protocol": "clarvis.tasks.v2"
    },
    "default_container": "engineering",
    "writes": "disabled"
  }
}

default_container is optional. Writes are disabled by default; set writes to enabled only after reviewing the connected server and the agents that carry tasks.* grants. Provider setup, plugin installation, and Extension Profile activation remain separate decisions.

Browse the provider from Clarvis ​

Open /tasks to check the connection, switch between board and list views, filter by container or text, refresh, and read task details. The board shows the Clarvis stage, the service's own status, the assignee, and any active claim separately. It does not assume every service supports the same workflow.

Read failures, conflicts, and uncertain mutation outcomes appear as explicit states rather than an empty board. Returning from agent work refreshes the task from the external source of truth.

Inspect a task or work on it ​

Selecting Work on task opens the normal Agent Profile picker and starts a run in the current workspace bound to that external task. The task description enters the run as untrusted work data; it cannot change the workspace, grant tools, disable safety controls, or select a provider.

Task access has two modes:

  • inspect offers read operations only;
  • work can offer supported writes when settings, the selected agent's grants, and the provider's advertised capabilities all allow them.

Opening a task in work mode does not mutate it. The agent must explicitly call start_task, and finishing a Clarvis run never completes, reopens, or submits the external task automatically.

Know when changes are allowed ​

A write tool is available only when all four conditions agree:

  1. tasks.writes is enabled;
  2. the bound run uses work mode;
  3. the selected agent has the matching tasks.* grant;
  4. the provider advertises that operation or lifecycle transition.

Clarvis sends changes one at a time within a run and includes an identifier to prevent duplicate requests. If a network failure leaves the result uncertain, Clarvis reads the task again, reports the uncertainty, and does not retry the change automatically. Check the task in the external service before trying again.

See also ​