Define agents in markdown, connect your tools, and let them run while you sleep.
press return to run · / to focus · bring your own model
…and it gets to work
A primary agent decomposes the job and dispatches specialists in parallel — each in its own sandbox.
The system
Markdown-defined autonomous workers — each with its own identity, permissions, tools, and triggers. A support agent, a bookkeeper, a recruiter. Every one a specialist you can read, version, and own.
60+ reusable knowledge packs that teach agents real work — coding, research, browser, spreadsheets.
Cron schedules and webhooks fire agents on your timeline — automatically, overnight, on event.
Persistent and versioned. The longer it runs, the more context it keeps — and the smarter it gets.
Agents work in disposable sandboxes; work reaches main only through a change request you approve.
Meet your workforce
Each agent is its own markdown file. Pick one to see how it's wired.
Mission control
Every agent, session, and trigger — live status, activity, and spend at a glance.
Connect anything
Bring your own model and reach 3,000+ apps — swap providers per agent, connect any API.
Claude · GPT · Gemini · Mistral · Llama — and 40+ more providers
Agent preview
A simple file with frontmatter config and natural-language instructions. No SDK. Version-controlled. Instantly deployable.
--- name: Support Agent model: bring-your-own triggers: - cron: "*/5 * * * *" - webhook: /api/tickets skills: - customer-support - knowledge-base permission: "machine cr *": allow --- You are a Tier-1 support agent. Resolve tickets using the knowledge base. Escalate P0 issues immediately.
Claude, GPT, Gemini, Llama — swap per agent with one line.
Cron and webhooks fire agents on your timeline, automatically.
Each agent gets exactly the access it needs. Least privilege, built in.
Attach pre-built skill packs or write your own. Mix for any workflow.
How it works
Every tool your company uses — OAuth apps, MCP servers, REST APIs, CLI tools. If it has an interface, Machine connects to it.
Define agents, attach skills, set triggers. Each agent is a markdown file with its own identity, permissions, and activation rules.
Your agents run 24/7. Triggers fire them on schedule. They keep going until the job is verified done. Check in from anywhere.
Why Machine
A chatbot waits for you to ask. Machine runs your operation.
SOC 2 Type II audit underway — and the controls it measures (isolation, scoped credentials, encrypted secrets, an audit trail of every change) are already how it's built.
The morning after