Hours-long agents need a control plane, not a longer request
Vocion Teamvocion-v2.47.9
ADR 0004 is accepted on main; phase 1 (worker_run, the worker API, the reaper) is in review as vocion-core#237, a draft PR, not merged.
15 posts. Tags are topics; for the editorial split see Feature releases and Developer updates.
ADR 0004 is accepted on main; phase 1 (worker_run, the worker API, the reaper) is in review as vocion-core#237, a draft PR, not merged.
What self-hosting an agentic workflow platform ran in September 2026: Postgres, Temporal, Langfuse, an app server. Updated for 5.0: Temporal was removed in 4.0.
How to build an AI agent approval workflow you can self-host: an approve step, a skill that requires review, trust thresholds, and a REST decision API.
Which version of the agent did that? A concrete schema for AI agent versioning and audit trails: version rows on apply, a workspace SHA on every tool call.
When a human edits, approves, or rejects a draft, that decision can become a rule the agent reads next time — but only after a person approves it.
An agent can extract and score an application, but only a person should reject one. Here is the object, the gate, and the API call that enforces it.
Vocion's review queue API: GET /api/v1/reviews lists an org's pending agent actions, POST /api/v1/reviews/decide approves, rejects, or edits one.
Build a support agent that summarizes and drafts ticket replies, then holds them in a review queue until a human approves.
A guide to deploying AI agents in production with human approval: five insertion points, an autonomy ladder, trust thresholds, and a REST review queue.
The exact commands a coding agent runs to install Vocion, scaffold a workspace, apply it, and start the server, with a check that proves each step worked.
A build guide with the artifacts: the agent file, the team file, the mission, the workflow with a human gate, and the version row the apply writes.
What to trace when many agents run: per-org, per-agent, per-feature cost, tool calls linked to a workflow, and the schema behind it.
What an open-source agent workforce platform is, what it must include, and how Vocion implements it with git-authored agents, approvals, and audit.
Autonomy levels are usually an analogy. Here are three real missions at levels 1, 2, and 3, the code that enforces the gate, and what the levels do not do.
A working setup for the v2.16 MCP surface in Claude Code: registration without leaking a token, exact CRM counts, on-demand call transcripts and mail threads, and writes that always wait for a human.