Autonogrammer
Autonogrammer is a visual builder for multi-agent AI workflows. Operators draw role cards on a canvas, wire them into a pipeline, swarm, or orchestration, and run them on their own machine with their own provider keys.
The problem
Running several AI coding agents on one codebase raises questions about order, instructions, and records. Autonogrammer keeps those answers on a canvas that saves to the project and writes a run log for each run.
01 / 03
Autonogrammer is a visual builder for multi-agent AI workflows. It is for engineering teams that want several AI agents to work on one repository, on the o … omitted 11633 chars … s. Terminal tickets carry a keyed hash (HMAC) made from a secret created at launch. Both happen off-chain, on the operator's machine.
The package README lists a login in the app's own profile as a requirement. The root README describes a free model tier that needs no key, but it refers to the earlier engine. [NEEDS CONFIRMATION: whether that free tier still works on the Omp engine.] Confirm the current setup before you rely on either path.
Cards work in the project folder the operator selects. Under the default permission mode, each tool request is approved automatically, including shell commands, and every decision is written to the run log. Operators should review the resulting changes with normal version control, because the agents work on real files.
02 / 03
To ask for a technical briefing or early access, use the contact page on this site. This case study does not discuss commercial terms, and it stays unpublished until the owner signs off.
03 / 03
Paths marked autonogrammer-ship are relative to the Autonogrammer repository. The contact page is in the site repository.
Questions
The canvas host is a process on the operator's machine. It starts one local omp process for each card session and drives it over a local protocol. Model requests go to the provider the operator configured. The request gate limits the canvas to loopback addresses by default.
No. The code has no wallet, Ethereum, or on-chain library, and no step asks a person to sign with a personal key. Two things are cryptographically marked. Swarm assignments are signed with an Ed25519 key the operator provides. Terminal tickets carry a keyed hash (HMAC) made from a secret created at launch. Both happen off-chain, on the operator's machine.
The Omp engine in Autonogrammer uses the provider credentials the operator configures in the app profile. A free model tier may be available depending on the provider; confirm against the current Omp engine README before assuming no key is required.
The root README mentions a free model tier that needs no key, but it refers to the earlier opencode serve engine. The current Omp engine requires a login in the app's profile. Confirm whether the free tier still applies on the Omp engine you ship.
Cards work in the project folder the operator selects. Under the default permission mode, each tool request is approved automatically, including shell commands, and every decision is written to the run log. Operators should review the resulting changes with normal version control, because the agents work on real files.
Sources
This is a product use case. No customer is named and no outcome figures are shown.