AI workflows you can run,
review, and own.
Package repeatable coding work into versioned Chains, connect the models and tools you choose, and run them from the CLI, VS Code, or ACP clients with explicit approval gates. No hosted Contenox service required.
Installs contenox. Run contenox init to scaffold a workspace.
Where Contenox fits
The agent layer you control, from terminal to editor.
Contenox is not just a chatbot, not just a VS Code extension, and not just an agent framework. It is a local-first workflow runtime for specific, reviewable AI work.
| Nearby world | Why Contenox is different |
|---|---|
| Cursor / IDE copilots | Runtime-first, not editor-first. The same engine works from the terminal, VS Code, and ACP clients. |
| Aider / CLI coding agents | Broader workflow, session, tool policy, and provider scope than a single coding loop. |
| LangChain / agent frameworks | End-user executable product, not just a library you wire into an application. |
| Dify / n8n / web AI workflow tools | Local desktop/workspace-first, not web-app or SaaS-first. |
| Ollama wrappers | Provider-neutral and workflow/tool/HITL-oriented, with local and hosted models. |
What you can author
Repeatable work, with policy in the file.
- →Release evidence pack: feed in git history, PRs, ticket notes, and CI output; the chain drafts the changelog, risk notes, and deployment checklist, then stops before publishing.
- →API-to-workflow wrapper: register a narrow OpenAPI subset, inject hidden workspace or environment arguments, and require approval for mutating calls.
- →Repo maintenance chain: inspect an issue, plan the patch, touch only approved files, run tests, and prepare a review packet instead of silently changing the project.
- →Browser QA evidence: Playwright captures the live app state, the chain writes documentation or screenshots, and the policy decides what needs human approval.
Run it where work happens
The same chain can run in your editor, terminal, or automation.
Contenox ships a native VS Code extension, and speaks the Agent Client Protocol over stdio for other editors. Use VS Code, Zed, JetBrains, or AionUi when an editor UI helps; keep the workflow itself in the chain file, with tool calls and HITL approvals routed through the client.
// ~/.config/zed/settings.json
{
"agent_servers": {
"Contenox": {
"type": "custom",
"command": "contenox",
"args": ["acp"]
}
}
}Bring one recurring workflow. We'll package it as a reviewable Contenox chain.
Private pilots include workflow packaging, internal API integration, and early Dashboard work for shared knowledge and operated deployments.
Request a workflow review