human:resolve

Resolve a suspended human step — carries { runId, stepId, decision | formPayload } to the run DO

Effect: ask; Awaits an outcome — the call returns the response below.
Caller: manage_workflows; The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost: free; What one call costs, so you can budget before acting.
Reversible: yes; The effect can be undone by a later call.
Idempotent: yes; Safe to retry as-is.

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/human:resolve \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "runId": "run_1", "stepId": "s2", "decision": "approved" }}'

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.

runId string required
stepId string required
decision approved | rejected optional
formPayload object optional
slug string optional
attestation string optional

Response

What comes back from the call.

ok boolean
status string
error string

Traffic

Every call to human:resolve, 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 human:resolve, 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

API route 3

one.ie/web/src/lib/bind-receiver.ts:129
one.ie/web/src/lib/chat/doorman.ts:44
one.ie/web/src/lib/resolvers/tasks.ts:701

Agent runtime 4

channels/src/index.ts:564
channels/src/lib/actions.ts:37
channels/src/lib/approval.ts:80
channels/src/tools/workflows.ts:227

Workflow 3

one.ie/web/src/components/workflows/RunMonitor.tsx:273
one.ie/web/src/lib/workflow-receivers.ts:1426
one.ie/web/src/lib/workflow-templates.ts:1088

MCP 2

tasks_approve · packages/mcp/src/tools/tasks.ts:283
workflow_resolve · packages/mcp/src/tools/workflow.ts:80

CLI 1

packages/cli/src/workflow.ts:114

Docs 1

one.ie/web/src/content/docs/workflows.md:69

→

Answered by

human:resolve one.ie/web/src/lib/workflow-receivers.ts:1823 Dispatched through POST /api/ask/human:resolve, after the envelope validates the payload.

human family · 1 more

human:notify

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "runId": {
      "type": "string"
    },
    "stepId": {
      "type": "string"
    },
    "decision": {
      "type": "string",
      "enum": [
        "approved",
        "rejected"
      ]
    },
    "formPayload": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    },
    "slug": {
      "type": "string"
    },
    "attestation": {
      "type": "string"
    }
  },
  "required": [
    "runId",
    "stepId"
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "status": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}