For teams already using Claude Code or Codex
Leave tickets. Come back to pull requests.
DevIntern turns ready Jira and Linear tickets into reviewable pull requests using the coding agent you already have, on your infrastructure. It manages the queue, checks, review feedback, and recovery. Your team decides what merges.
14-day Worker Pilot · No credit card · Sign-in required Manual setup guide
How it works
How the worker runs
One daemon watches the backlog, routes each ticket to the right repository, and runs the implementation loop locally. Review comments return to the same worker instead of becoming another terminal session for you to resume.
Optional intake
Prompt, logs, Figma → DevIntern PM
- 1
01 · INPUT
Ready tickets
Tracker queue
3 queued - 2
02 · ROUTE
Worker
Routes across repos
- 3
03 · BUILD
Coding agent
Isolated worktrees
- 4
04 · CHECK
Quality gates
Auto-review optional
- 5
05 · HANDOFF
Pull requests
Ready for humans
2 open
Review loop
Comments return to the worker as commits on the same branch.
Need a ticket first? DevIntern PM turns a prompt, log, or Figma frame into optional intake for the worker.
Move work forward across every repo
Turn ready tickets into pull requests, keep dependencies current, and fix production errors across your teams’ codebases. One workspace brings their trackers, repositories, scheduled maintenance, and Sentry fixes together under a single worker.
- Engineering Jira
- Product Linear
- Developer tools GitHub Issues
DevIntern
One workspace
One worker on your machine
Shared defaults · per-repo settings
- acme/api
- acme/infra
- acme/web
- acme/sdk
Scheduled work & error monitoring
- Triage worker logs Daily
- Update dependencies Weekly
- Repair failing main Every 12 hours
- Sentry auto-fixes Unresolved errors
Each team keeps its tracker and credentials. Each repo keeps its agent and pipeline settings. Your team reviews the changes, while the worker handles the follow-through.
Start with one repo. Add teams and repositories as you grow. Explore workspace setup →
The async dividend
Your attention does not parallelize.
Supervising interactive agent sessions is still your focus, all day: watching terminals, approving steps, holding context for every open run. DevIntern moves your involvement to checkpoints. Work happens in the background, and the only interruptions that reach you are the ones that deserve to: a spec that needs a human call, a PR ready for review, a comment already addressed.
Your morning, supervising sessions
- Five terminal tabs, each mid-session, each waiting on you
- Context held in your head for every open run
- Faster than typing the code, but still your attention, all day
Your morning, with DevIntern
- Overnight tickets arrived as pull requests, checked and described
- One spec flagged as ambiguous, waiting on a human call in the tracker
- Your day starts with diffs to review, not sessions to resume
No lock-in
Keep the tools your team already uses
DevIntern does not ask you to replace your tracker, coding agent, or model contract. Model rankings reshuffle every few months, and each reshuffle makes the neutral layer more valuable.
Your tracker
Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, or plain markdown files. Full lifecycle, not just reading titles: batch selection with JQL, status transitions on pickup and completion, and the implementation summary posted back as a comment with the PR link.
Your coding agent
Claude Code, Codex, Cursor, or OpenCode. The agent is one config line. When a better one ships next quarter, switching costs that line, not a workflow migration: the tracker wiring, the review loop, and the run history all survive the swap.
Your model, your keys
Whatever models your agent supports, billed on your existing provider contract. No bundled model, no token markup, no waiting for a vendor to adopt the new frontier model. Day-one support for every release, by construction.
AGENT_HARNESS=claude-code
AGENT_HARNESS=codex # that is the whole migration
Built for unattended work
How it holds up without you watching
Async delegation only works if the loop catches its own mistakes. Four mechanisms carry that weight.
Feasibility gate
Before implementing, the task is checked for clarity. Vague specs get flagged back to the tracker with questions instead of becoming a confidently wrong pull request.
Optional self-review loop
Turn on auto-review and the agent critiques its own diff, fixes what it finds, and checks again before a human sees it.
Review comments become commits
With unattended automation on, reviewer feedback is picked up and addressed on the same branch, with replies. The cycle does not end when the PR opens.
Survives real life
Persistent queue, crash recovery, and provider rate-limit detection with pause and resume. The unglamorous 20% that kills the DIY script is built in.
Put a worker on your backlog
Choose which tickets the worker picks up and keep your existing review process. It watches for ready work, opens pull requests, and responds to review feedback. Start with the 14-day Worker Pilot, then choose a license for ongoing automation.
- Try it first: the no-card Worker Pilot runs unattended for 14 days with no task limit
- Ready-ticket pickup and review handling on your own server, devbox, or spare VM
- Team is $99 a month for up to 10 developers, with no per-repo metering
- Solo? A one-time supporter license covers unattended automation for one person's own repos
- 30-day money-back guarantee on subscriptions, no questions asked
- Early pricing: subscribers keep their price for as long as they stay subscribed
Start with one ticket
Want to inspect the pipeline before leaving the worker running? Run devintern PROJ-123 --create-pr after setup to implement a ticket and open a pull request. Interactive runs are free forever, with no DevIntern account required. They do not keep watching your backlog or responding to review feedback.
- Run a local task file to try the pipeline without tracker credentials
- All trackers and all agents included: Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, markdown
- Use your existing coding agent and keys; provider usage costs still apply
- Source-available, so you can read exactly what it does before pointing it at your repo
Read the source before you hand over a Jira token
DevIntern is source-available under the FSL: read it, audit it, self-host it. Your code, credentials, and diffs never touch our servers, and the source is how you verify that instead of trusting it. Each release converts to Apache-2.0 after two years, so the worst case is "stops improving", never "stops working".
Read the source on GitHub Where every credential lives, in full →
FAQ
The questions engineers actually ask
Why not just give my coding agent a tracker connection myself?
You can, and it works for one ticket while you watch. DevIntern is what you build after that demo: the queue, the branch and PR and status state machine, optional auto-review, review-comment handling, rate-limit recovery, and a record of what happened to every ticket. The source is available, so compare it to your script.
Is agent-written code good enough to merge?
Sometimes no, which is why there is a feasibility gate before implementation, an optional self-review loop for the diff, and an escalation path instead of a forced merge. Your reviewers stay the final gate, exactly as they are today.
You want my tracker token and push access?
They stay on your machines. Credentials live in a local env file and each one is sent only to its own vendor's API. Optional DevIntern services receive narrow operational data, never source code, diffs, ticket bodies, review comments, or vendor credentials. See the security page for the full inventory.
Another subscription?
Sign in to try the worker for 14 days with no credit card or task-count limit. Continued unattended automation requires a Supporter license or a Team/Business subscription. Your coding-agent usage is billed separately by your provider. You can also inspect the pipeline with free interactive runs, with no DevIntern account or time limit.
What if you disappear?
The license (FSL) converts to Apache-2.0 two years after each release, the code is public, and everything runs on your infrastructure. The failure mode is "stops improving", not "stops working".
Do we have to change our workflow?
No. Same repo, same reviewers, same CI, same tracker. Pull requests arrive the way your team already reviews them, and one engineer can start alone without asking anyone.
Which trackers, agents, and models are supported?
Trackers: Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, and plain markdown files. Coding agents: Claude Code, Codex, Cursor, and OpenCode. Models: whatever your agent supports, on your own keys.
Credentials and data flow, in full: the security page →
Put a worker on your backlog this afternoon.
Connect your tracker, choose which tickets are ready, and leave devintern worker running. It picks up tasks and follows up on PR feedback. Your team decides what gets merged.
Worker Pilot: 14 days, no card or task limit. Sign-in required. Continued automation requires a license.
Different seat? DevIntern for engineering managers, product managers, and founders.