On your machine
- Hermes and its project configuration
- The git checkout and agent workspaces
- Model, provider, tool, and CLI credentials
- The terminal, browser, and tools Hermes uses
Hermes gives you the autonomous builders. AI StackWorks gives them a production system: a visible backlog, specialised roles, repeatable stages, quality gates, and a controlled path from idea to shipped software—all while Hermes runs on your machine.
The factory architecture
AI StackWorks is the factory control plane. Hermes is the skilled workforce executing on your machine. A real-time connection routes scoped work down and returns progress, results, and evidence.
Your team requests and approves work in AI StackWorks. AI StackWorks sends the scoped task and approved plan over a real-time connection to Hermes on your machine. Hermes works with the repository and tools on that machine, while progress and evidence return to the task record.
One backlog. One production system.
Your team directs. AI StackWorks orchestrates. Hermes builds on your machine.
People
Requests work, approves the plan, and reviews the result.
Factory control plane
AIS-204
Ship customer export
Your infrastructure
Production workforce
Hermes Agent
The production line
Backlog items move through planning, build, QA, review, and a human ship decision. Handoffs, failures, and proof stay visible, and the record survives long after the originating chat is gone.
Work comes in
Initial input or idea, from Slack, Jira, or Linear.
Agent plans
A full plan, scoped to your docs and decisions.
You approve
Your team discusses and edits it with the agent.
Agent builds
Code written, pull request opened.
QA checks
Failures go straight back to the agent.
Review pass
Final checks, plus a demo video.
You ship
Watch the demo. Merge with one click.
Work comes in
Initial input or idea, from Slack, Jira, or Linear.
Agent plans
A full plan, scoped to your docs and decisions.
You approve
ApprovedYour team discusses and edits it with the agent.
Agent builds
Code written, pull request opened.
loops with QA until green
QA checks
Failures go straight back to the agent.
Review pass
Final checks, plus a demo video.
You ship
ShippedWatch the demo. Merge with one click.
After every ship, automatically:
Want to see AI StackWorks in action?
Watch the product video, then explore the interface and task record.
Your factory, your infrastructure
Your source, credentials, tools, and Hermes runtimes remain on the machine you control. AI StackWorks coordinates the production line and makes its selected work record available to the team.
Start the line
Connect Hermes, enroll the machine, and bind it to a project. Then put a real backlog item onto the line and inspect what comes back at every stage.
Install Hermes on the machine that will do the work and configure the model and tools you want it to use.
Run the one-line command shown in AI StackWorks. It enrolls the machine and starts the real-time Hermes connection in a couple of minutes.
Create a project, dispatch one real task, and follow it through planning, build, QA, review, and ship.
Prefer guided setup? See the Agent Team Kickstart.
The workforce
Terminal, files, web research, browser automation, and APIs when the task calls for them.
Persistent memory, project context, and reusable skills reduce repeated instructions.
Profiles and isolated subagents can separate specialist roles and parallel tasks.
Configurable model providers, execution backends, plugins, MCP tools, and gateways.
Practical questions
Connect a machine, choose a repository, and send one real task down the line—from backlog and plan to tested, reviewed, human-approved software.