Starts Nov 20. Live now. 40% off your first invoice with code BLACKFRIDAY26, Nov 20 to Dec 1. See pricing

For engineers already using Claude Code or Codex

Leave tickets. Come back to pull requests.

DevIntern is a self-hosted worker that picks up your ready Jira and Linear tickets, runs the coding agent you already use, and opens pull requests for review. It handles the queue, checks, review feedback, and recovery. Your team decides what merges.

Your coding agent does the setup from a chat: install, tracker and repo connections, and your first worker. Prefer to do it by hand? Follow the manual setup guide.

14 days of unattended runs · No credit card · No task limit · Sign-in required

127.0.0.1:4400 Run PROJ-1842
DevIntern dashboard run detail for ticket PROJ-1842: status succeeded, pull request #4419 opened on acme/api, with a timeline of feasibility check, implementation, verification, self-review, and outcome, plus a metadata sidebar.
Ticket PROJ-1842 became pull request #4419 on acme/api, shown in the worker's local dashboard. Example data.

The problem with watching agents

Your attention does not parallelize.

Interactive agent sessions are faster than typing the code, but they still take your whole day: watching terminals, approving steps, holding context for every open run. DevIntern moves you to checkpoints. Work runs in the background, and only decisions reach you: a spec that needs a human call, or a pull request ready for review.

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

How it works

One worker carries each ticket from ready to review

The worker watches your backlog, routes each ready ticket to the right repository, and runs your coding agent in an isolated worktree. Review comments come back to the same worker and the same branch, not to another session for you to resume.

DevIntern worker · running
your machine · your keys · your repos

Optional intake

Prompt, logs, Figma → DevIntern PM

  1. 1

    01 · INPUT

    Ready tickets

    Tracker queue

    3 queued
  2. 2

    02 · ROUTE

    Worker

    Routes across repos

  3. 3

    03 · BUILD

    Coding agent

    Isolated worktrees

  4. 4

    04 · CHECK

    Quality gates

    Auto-review optional

  5. 5

    05 · HANDOFF

    Pull requests

    Ready for humans

    2 open

Review loop

Comments return to the worker as commits on the same branch.

What "ready" means: any ticket that matches the tracker query you choose, such as a status, a label, or a JQL filter. The worker only picks up tickets that match.

task_query = "project = PROJ AND labels = devintern"

One ticket, start to finish (example)

  1. 1 PROJ-1842 Labeled devintern in Jira, so it matches the query.
  2. 2 Picked up Moved to In Progress, routed to acme/api, worked on its own branch.
  3. 3 Checked Feasibility check, implementation, verification, and optional self-review.
  4. 4 PR #4419 Opened on acme/api, with the summary and PR link posted back to the ticket. Your team reviews it.

Need a ticket first? DevIntern PM turns a prompt, log, or Figma frame into optional intake for the worker.

The dashboard

Check in on your schedule, not the agent's

Every run lands in a dashboard: what the worker picked up, what each step did, and which pull requests are waiting on you. It runs on the worker machine and listens only on loopback, so run history, transcripts, and logs stay next to your code.

Every ticket the worker picked up, with its status, harness, duration, and pull request.

127.0.0.1:4400 Runs
Dashboard runs list showing tickets from acme repositories with status, outcome and pull request link, harness (claude-code or codex), start time, and duration.

Swipe the screenshot sideways to see the full view.

Screenshots show example data from a demo workspace. Read the dashboard guide →

Workspaces

One worker for every team's tracker and repo

A workspace connects several teams, trackers, and repositories to a single worker. Each team keeps its own tracker and credentials, and each repository keeps its own agent and pipeline settings.

127.0.0.1:4400 Workspace
Dashboard workspace view with a work routing graph: Jira for Engineering with a JQL query, Linear for Product, and GitHub Issues for Developer tools, plus scheduled automations and a Sentry error monitor, routed to the repositories acme/api, acme/web, acme/infra, and acme/sdk. A side index lists repositories, automations, estimations, error monitors, credentials, and policy.
Example workspace in the dashboard. Example data.

The same worker can run scheduled maintenance and fix qualifying Sentry errors, and your coding agent can queue an agreed fix for it directly, without a ticket. Delegate from your agent →

Start with one repo. Add teams and repositories as you grow. Explore workspace setup →

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.

.env

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.

Your ongoing worker

Put a worker on your backlog

Choose which tickets count as ready and keep your existing review process. The worker runs on your own server, devbox, or spare VM, opens pull requests, and responds to review feedback. Start with the free 14-day Worker Pilot, then choose a license for ongoing automation.

  • Try it first: the pilot runs unattended for 14 days, with no card and no task limit
  • 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
Optional: inspect one run

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 →

Weighing hosted agents too? Self-hosted vs hosted coding agents →

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.

14 days of unattended runs · No credit card · No task limit · Sign-in required

Prefer to do it by hand? Follow the manual setup guide. After the pilot, continued automation requires a license: see pricing.

Different seat? DevIntern for engineering managers, product managers, and founders.