Categories
MCP Self-hosted Scheduling AI agents Job automation Recurring tasks Sandboxed execution Workflow automationStars
Forks
Watchers
Developer links
Umpteenth
Recurring chores should get cheaper every time you run them, and Umpteenth is a self-hosted agent service built on that idea: describe a job once in plain language, and each run teaches it to need less help. A job starts on a schedule, a webhook call, the API, or the Run now button, and each run gets a fresh disposable container destroyed afterwards. The first run is an Explore run where the agent works out the steps; afterwards a reflection step reads the transcript and writes short learnings plus reusable toolkit scripts into a numbered playbook version. Later runs are Assisted, starting from those learnings, and after three successful assisted runs that take the same steps, the job graduates: reflection writes a main script, and scripted runs execute it alone, spending no model tokens unless a check asks for a judgment call. If a scripted check fails, the agent takes over in the same sandbox, finishes the job, and repairs the script. The job page charts cost per run dropping toward zero. Connect HTTP MCP servers such as GitHub or Slack; model keys and MCP credentials stay on the host and never enter the sandbox. Each job sets its own schedule, model, reach, and per run spending limit. Deploy with Docker Compose, or on Kubernetes with the Helm chart, where every sandbox is a pod. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Benefits
- Jobs Graduate To Scripts
- After three assisted runs that take the same steps, reflection writes a main script and later runs execute without an agent, so model token cost per run falls to zero.
- Disposable Sandbox Per Run
- Every execution gets a fresh container that Umpteenth creates and destroys, so leftover state, stray files and half-finished work from earlier runs can never contaminate the next scheduled execution.
- Credentials Stay On Host
- Model API keys and HTTP MCP credentials never enter the sandbox; only job secrets arrive as environment variables, and command based MCP servers run inside under their own user.
- Every Run Fully Recorded
- Each run stores its transcript, its mode and what it cost, and the job page charts cost per run, so you can watch automation get cheaper as the playbook matures.
Features
- Three Run Modes
- Jobs progress from Explore, where the agent works steps out, through Assisted runs guided by learnings, to Scripted runs that execute a generated main script alone.
- Versioned Job Playbooks
- After every run a reflection step writes short learnings and reusable toolkit scripts into a numbered playbook version, which later runs call as tools instead of reasoning again.
- MCP Server Connections
- Connect HTTP MCP servers such as GitHub or Slack for agent tools, while Umpteenth brokers one token per run and keeps those credentials outside the sandbox entirely.
- Schedules Webhooks API
- A schedule, an incoming webhook call, the API, or Run now on the job page each start a run, with per job limits on what a run may spend.
- Docker Or Kubernetes
- Deploy with Docker Compose on one host, where sandboxes come from the host Docker socket, or with the Helm chart on Kubernetes, where every sandbox is a pod.