Generated by Answer me with HTML 0.5.10 · 2026-11-02 17:24 · ★ Star on GitHub
How Mothership works
Connect an agent, control its tools, and carry work across sessions.
Mothership gives AI agents a shared place to use tools, store files and save task progress. The human operator controls access.
One task from start to finish
Example: an agent gathers public research, prepares a report, saves its files and leaves a checkpoint for the next session.
Actions stay within granted access
An approval request does not mean an action succeeded. If the outcome is uncertain, keep the original action key and reconcile it.
What each part does
| Part | Job |
|---|---|
| Agent | Chooses tools to complete the human's task. |
| Mothership | Provides scoped tools, saved state, approvals and execution records. |
| Human operator | Sets access, reviews gated actions and manages the host. |
| DeadBolt | Provides a separate permission gate where integrated. |
| Witness | Provides separate provenance records where integrated. |
Connect and evaluate
- Apply at nexteleven.tech/pilot.
- Choose one workflow and agree its permissions.
- Connect through MCP, REST or the Python SDK.
- Inspect the result and saved task state.
Pilot access is arranged after review. Browser tools require a compatible Linux host with Chromium sandbox support.