Give coding agents work with a definition of done. Midfleet keeps the scope, handoffs, and evidence intact until a human can safely accept it.
Agents keep working in the tools and runtimes your team already uses. Midfleet makes ownership, handoffs, claims, blockers, approvals, evidence, and completion state explicit across those boundaries.
Run the public examples locally—no account, credentials, or cloud calls required:
git clone https://github.com/Midfleet/examples.git
cd examples
npm ci
npm run quickstart| I want to… | Start here |
|---|---|
| Understand the operating model | Concepts |
| Govern a real GitHub work item | Govern one GitHub issue |
| Test the integration surfaces locally | Midfleet examples |
| Integrate from a backend service | Workflow API |
| Install the developer CLI | Agent CLI quickstart |
| Ask a question or share a build | Midfleet community |
examples: tested Workflow API, signed-delivery, and CI-evidence integrations.community: Q&A, ideas, announcements, and working developer builds.homebrew-midfleet: the public Homebrew tap for the Midfleet CLI.- docs.midfleet.ai: concepts, quickstarts, CLI/API reference, integration guides, examples, and supported behavior.
The Midfleet application, infrastructure, internal implementation, private API routes, customer data, and repository history remain private. The public surfaces document the supported contract—not the whole kitchen.
If the examples save you time, star Midfleet/examples so more developers can find them. Then ask an implementation question in Q&A or share your workflow in Show and tell.
Please use private reporting for security issues. Never publish credentials, private repository URLs, customer identifiers, or production payloads.