Airuncode
Freemium
Developers preferring fully local agent execution
Tmppr
FreemiumSelf-HostedAgentic
Coding agents working in parallel have no shared coordination layer — they overwrite each other's changes, lose context in chat logs, and leave you manually stitching together what ran, what passed, and what's ready to merge. tmppr gives those agents a local forge: PRs, CI, review threads, and merge gates, all running on your machine.
Similar tools
ClixadFreemiumClixad is a terminal coding agent with free daily usage, configurable approval modes and…
ManifestGoFreemiumThe core workflow is a one-prompt generation: describe what you want, and ManifestGo produces…
AiruncodeFreemiumAiruncode runs agents locally, lets you plug in your own provider keys or on-device models…
AtlarixFreemiumAtlarix is a desktop AI workstation where agents plan, write, test, and debug inside workspaces…
Summary
The core workflow is a full pull-request lifecycle that runs on localhost: agents open PRs, trigger CI via your existing GitHub Actions YAML, review each other's diffs inline, and ship only after merge gates clear. An MCP server registers every action as a native tool for Claude Code and Codex, so agents call PR open, review, and merge without glue code. The stacked-PR workflow handles dependent branches in order without manual rebasing. The ceiling appears when teams need shared CI infrastructure — local runners work for solo or small-team setups, but shared minutes require the paid cloud runner option. No API means external systems cannot push events into tmppr without building through the plugin SDK.
Bottom line: Pick tmppr when you want autonomous coding agents to coordinate through structured PRs on a single machine without code leaving your network — plan a different architecture when your CI needs to fan out across multiple machines or integrate with an existing cloud pipeline you cannot replace.
Pricing Plans
Last verified 4 months ago- Free Tier
- Local and free - runs on your machine, code stays on 127.0.0.1
Local tmppr
Free
Local and free. Plugins run on your machine alongside the rest of tmppr local. Your code and your extensions stay on 127.0.0.1.
- Local PR review
- Plugin SDK support
- GitHub-style diff viewer
- Real CI run locally
- Enforced merge gates
- First-class CLI for agents
- Stacked-PR workflow
- Code never leaves your box
- Event automations
- Native desktop app
- MCP server built in
Cloud runners
per month
Burst to tmppr Cloud runners when you need shared minutes or a bigger box.
- Cloud burst capacity for CI
View full pricing on tmppr.com →
Pricing may have changed since last verified. Check the official site for current plans.
Find your fit
Before you choose Tmppr
More options in Coding Assistants. Compare pricing, platforms, and features side by side.
Atlarix
Freemium
Engineering teams needing private/local AI coding assistance
Pros
- MCP server auto-registered on init, so Claude Code and Codex agents call PR, CI, review, and merge as native tools — no glue scripts to maintain between your agent loop and the forge.
- Executes existing GitHub Actions YAML locally with live log streaming, which means you reuse CI definitions you already have instead of rewriting them for a new platform.
- Strict 127.0.0.1 binding with no telemetry and no account required for local use, so teams with hard code-leakage policies can run full agent loops without sending source off the machine.
- Full-lifecycle event triggers covering the entire issue-to-merge cycle, which means a failed CI run automatically queues a fix agent rather than leaving the loop waiting for a human to notice.
- Plugin SDK lets you add agent providers, merge rules, and automation triggers from a single installable package without forking core, so your customizations survive upstream updates.
Cons
- Local CI runners work for a single machine — the moment a team needs shared CI minutes, parallel runners, or a bigger build box, they hit a wall that only the paid cloud runner option unblocks. Teams evaluating cost at that point compare against existing cloud CI they already pay for.
- No public API means external systems — monitoring tools, issue trackers, deployment pipelines — cannot push events into tmppr without a plugin authored against the SDK. Teams that need bidirectional integration with an existing platform end up maintaining a custom plugin as a second system.
- The tool has no listed alternatives in market, but teams whose agent workflows already live inside a hosted platform like GitHub Actions with Copilot or a managed agent orchestration service will find tmppr's local-first model an architectural mismatch rather than a drop-in addition — those teams do not adopt it, they replace it.
About
- Platforms
- macOS, Linux, Windows
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- June 18, 2026
Best For
Who it's for
- Teams using Claude Code, Cursor, or similar with agent loops
- Local-first development avoiding code leakage
- Enforcing structured processes on autonomous coding agents
What it does well
- Coordinating multiple coding agents on shared tasks via PRs
- Running local CI and enforcing merge gates for agent-generated code
- Automating review, QA, and fix cycles in agent workflows
Integrations
Frequently Asked Questions
- Is Tmppr free?
- Tmppr offers a free option alongside paid upgrades. Check the current allowances and terms before choosing a plan.
- Can I self-host Tmppr?
- Yes. Tmppr supports self-hosting on your own infrastructure.
- What platforms does Tmppr support?
- Tmppr is available on: macOS, Linux, Windows.
Most agent-based coding setups devolve into one agent overwriting another’s work, with no record of what was reviewed or why something merged. tmppr addresses this by giving agents a local Git forge — the same pull-request primitives a human team uses, but scriptable end-to-end. Agents grab open issues, open PRs, run CI against your existing GitHub Actions YAML, post inline review comments, and trigger follow-up agents on events like failed CI or requested changes. Merge gates enforce GO/NO-GO from review approval, CI status, and conflict checks before a real `git merge –no-ff` in a detached worktree.
The differentiating feature is the MCP server, auto-registered on `tmppr init`. Every action — PR open, sync, comment, review, rerun CI, merge — is exposed as a native MCP tool, which means Claude Code and Codex call them directly without wrapper scripts. Combined with full-lifecycle event triggers (`pr.created`, `ci.updated`, `review.updated`, and others), the entire issue-to-merge loop can run without a human touching it. You stay in the loop by setting the merge rules; the agents work within them.
The plugin SDK (`@tmppr/plugin-sdk`) lets teams extend the forge without forking: a single package can add agent providers, automation triggers, merge rules, hook executors, event subscribers, and HTTP routes, installed with one command and running on 127.0.0.1 alongside everything else. This matters when your agent provider is not Claude Code or Codex — you wire in a custom command and tmppr treats it as first-class.
The architecture binds strictly to localhost with no telemetry or account requirement for the local tier, which satisfies teams with code-leakage concerns. The constraint is the inverse: teams that need CI to fan out across machines, integrate with an existing cloud pipeline, or expose tmppr as a service to external systems will hit the boundary fast. Cloud burst runners are a paid-only feature, and the absence of a public API means external event sources require a plugin to get data in.
Contribute
- Work on Tmppr? Claim this listing.
- Embed a badge for your README or site.
Sign in to rate this tool or suggest an edit.