← Receivers

tasks:comment

tasks family

mcp

Post a comment on a task's thread, or read the thread back when `body` is omitted. An @mention in the body subscribes that actor to the task. A reader (viewer) may comment even where it cannot move the task. Address by tid, or by the /do slug — same two-way contract as claim/link, so a wave-close heartbeat does not need the generated tid

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
member
The class of authority the caller must already hold, decided from the attested context with no round trip.
Reversible
yes
The effect can be undone by a later call.
Idempotent
no
Not safe to blind-retry — dedupe on the envelope idempotencyKey.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code
Codex
Cursor
Gemini CLI
Claude Desktop
ChatGPT
curl -X POST https://one.ie/api/ask/tasks:comment \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "tid": <string>, "slug": <string>, "body": <string>, "workspace": <string> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

  • tid string optional
  • slug string optional
  • body string optional
  • workspace string optional
  • threadId string optional
  • author string optional

Response

What comes back from the call.

  • ok boolean
  • tid string
  • messages object[]
  • error string

Traffic

Every call to tasks:comment, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names tasks:comment, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

UI 2
  • one.ie/web/src/components/in/inbox-data.ts:451
  • one.ie/web/src/components/in/TaskDetail.tsx:212
API route 3
  • one.ie/web/src/lib/in/speaker.ts:4
  • one.ie/web/src/lib/resolvers/messaging.ts:290
  • one.ie/web/src/lib/resolvers/tasks.ts:534
Agent runtime 1
  • channels/src/tools/tasks.ts:246
Workflow 1
  • one.ie/web/src/lib/workflow-receivers.ts:407
MCP 1
  • tasks_comment · packages/mcp/src/tools/tasks.ts:240
Docs 1
  • one.ie/web/src/components/in/CLAUDE.md:22
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "tid": {
      "type": "string"
    },
    "slug": {
      "type": "string"
    },
    "body": {
      "type": "string"
    },
    "workspace": {
      "type": "string"
    },
    "threadId": {
      "type": "string"
    },
    "author": {
      "type": "string"
    }
  }
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "tid": {
      "type": "string"
    },
    "messages": {
      "type": "array",
      "items": {
        "type": "object",
        "propertyNames": {
          "type": "string"
        },
        "additionalProperties": {}
      }
    },
    "error": {
      "type": "string"
    }
  }
}