For engineers IC Self-hosted

Work async. Save your judgment for what matters.

@devintern/code turns tracker tickets into draft PRs on your machine: small fixes or large features, not just busywork. Queue several tickets at the start of the day; each run gathers context, implements, and opens a PR in the background while you stay on design, hard bugs, and the problems that actually need a senior. You review when they're ready. Same repo, same keys, no SaaS in the loop.

Start free trial Read the docs 14-day trial · no credit card
Hours back / week
~16h
less prep · review

typical IC throughput

Tickets per kickoff
3+
queue at standup

runs while you stay heads-down

Context hunts
0
before you code

repo · ticket · MCPs gathered

Tools migrated
0
same stack

Jira · GitHub · your agent

Why self-hosted wins for engineers

100% self-hosted. Reaches what cloud agents can't.

Every cloud-agent pitch sends your repo to someone else's VPC and asks for a second AI contract. DevIntern runs on your laptop or devbox, uses keys you already have, and touches the private context a hosted agent literally cannot. No new tenant to vet, no telemetry leaving your network.

Zero extra cloud bill

Runs on your laptop, devbox, or the CI you already pay for. No DevIntern-side compute, no per-seat metering, only the model tokens you'd spend anyway.

Your hardware. Your infra. Unchanged.

Native access to internal context

Your local DB, private MCP servers, secret store, and unpublished repos. A SaaS in someone else's VPC can't reach any of it. The tool in your shell can.

Private repos · internal MCPs · secret stores.

Compliance by default

Source, prompts, and tracker payloads stay on your machine or your VPC. Security doesn't get a new vendor to vet or a new data path to redline.

Your network. Your audit log. Your rules.

Reuses your existing AI contract

Claude, OpenAI, Bedrock, Cursor, Opencode, whatever your org already signed for. Spend down the commit you negotiated instead of paying a wrapper to resell tokens.

BYO model · BYO keys · your billing.

Your week back

The wrapper work that used to eat your day.

AI writes code in minutes. The prep (context, branching, PR hygiene, review ping-pong) is what burns the hours. @devintern/code absorbs that layer so you work async and stay productive.

With @devintern/code

Async runs · review PRs · more throughput

  • Understanding the ticket, gathering context, and babysitting the agent is automated. Kick off and move on.
  • Queue several tickets in one command. Work runs async while you stay on hard problems.
  • The run closes the loop: draft PR, tracker update, implementation summary. You review the work, not the paperwork.
  • Server addon can address routine review feedback automatically, with less ping-pong for you and reviewers.
  • ~16 hours back per week for typical ICs: same seat, more tickets through.

Your day without it

Context hunts · babysitting · wrapper work

  • An hour understanding the ticket, gathering context, and babysitting the agent before you write a line.
  • Babysit multiple agent runs in parallel (switching tabs, watching terminals, hoping nothing stalls) while your focus block burns.
  • Break out of hard problems to close the loop: PR write-up, tracker updates, and handoff notes.
  • Drop everything for review nits and Slack clarifications mid-afternoon.
  • Throughput capped by prep and wrapper work, not how fast AI writes code.

~16 hours saved

per IC, per week

What's inside

Built for the way you already ship.

No new dashboard to live in. @devintern/code plugs into the tracker, repo host, and AI agent you already use, on hardware you already pay for. Every run leaves artifacts on disk if you need to audit what happened.

Fetch · implement · PR
  • One command, full run

    Ticket key in: branch, implement, self-review, draft PR, tracker update. One devintern PROJ-1234 --create-pr, not five tabs open at once.

  • Reads your repo first

    Scans the codebase and cleaned ticket payload before writing a line. Uses real files, internal MCPs, and private packages, not a half-pasted spec from Slack.

  • Feasibility before the branch

    Clarity check flags ambiguous tickets before any work starts. Bad specs bounce back with a comment, not a half-baked PR you have to triage.

  • Self-review before humans

    A second agent pass reviews the diff and patches priority issues. Your reviewers spend time on design, not catching the obvious stuff.

  • Review fixes, unattended

    With the server automation addon, review comments get addressed automatically: checkout, fix, push, reply inline. You and your reviewers stop ping-ponging on nits; the intern handles routine feedback while you stay on harder work.

  • Multiple tickets, one kickoff

    Queue several ticket keys in one command. Each run works in the background while you concentrate on design, hard bugs, or reviewing the PRs that are already done, not babysitting the terminal.

  • Your agent, your keys

    Claude, Codex, Cursor, Opencode, or whatever your org already signed for. Per-repo config in .devintern-code/, GitHub App auth instead of your personal PAT.

Two tools, one workflow

Run ready tickets end to end. Prep thin specs when you need to.

Most of the time you point @devintern/code at a ticket and let it run. When the spec is thin but you already know what to build, draft a proper spec first so the agent has a better shot.

@devintern/pm Optional

When the spec is thin

The ticket is a title and half a sentence, but you already know what needs to ship. Hand @devintern/pm a rough prompt, error log, or Figma link with the details you already have. It drafts a better spec from what you provided: scope, context, and acceptance criteria, not just a bullet list. Preview, edit what it missed, and post. Your corrections land in the tracker, so @devintern/code reads a ticket it can act on instead of guessing.

@devintern/code

Ticket key to draft PR

Your daily driver. devintern PROJ-1234 --create-pr gathers context, finds where to edit, branches, and implements with your agent. That's the prep work you used to do before writing a line. It self-reviews, opens the draft PR, and updates the ticket. Your commit and push hooks still run; if one fails, it works through the failure instead of publishing broken code for review. Kick off a ticket and move on. Your focus shifts to reviewing the PRs it opens.

Next step

Install it tonight.
Have a draft PR ready before standup.

Runs on your laptop. Uses the AI keys you already have. Wires into the tracker and repo you already use. If it doesn't earn its keep on the first ticket, rm -rf ~/.devintern and forget us.

# in your project repo
$ bun install -g @getdevintern/code
$ devintern init
$ devintern login
$ devintern PROJ-1234 --create-pr

14-day trial · perpetual license · BYO model & keys

Also evaluating DevIntern for another role in your org?