For engineers IC Self-hosted

For engineers who already use a coding agent and are done babysitting sessions

Your backlog drains in the background. You stay on the hard problems.

@devintern/code turns tracker tickets into self-reviewed draft PRs on your machine, using the coding agent and keys you already have. Queue several tickets, go work the problem that needs a senior, and step in when a diff is ready. You can install it today without asking anyone.

$ bun install -g @getdevintern/code

Free for interactive use. No signup, no time limit. Your first PR can land within the hour.

Trackers supported
7
yours is on the list

Jira · Linear · Trello · Asana · Azure DevOps · GitHub Issues · markdown

Coding agents
4
one config line to swap

Claude Code · Codex · Cursor · OpenCode

To start
$0
free interactive use

no signup, no time limit, no credit card

Install command
1
no approval needed

bun install -g @getdevintern/code

Why self-hosted wins for engineers

Runs where your code already lives.

Everything runs on your laptop or devbox, on your keys, so there is nothing to procure and nothing to hand over. That is also why you can adopt it solo, this afternoon, without a rollout.

You can install it today, alone

It runs on your laptop or devbox, so there is no rollout to request and no admin to convince. One install command, point it at a ticket, and the first PR can land within the hour.

Your hardware. Your call. No procurement.

Credentials never leave your machine

Tracker tokens, repo access, and model keys live in a project-local env file, and each one is sent only to its own vendor's API. Nothing except license checks touches our servers, and the source is available so you can verify that instead of trusting it.

Local env file · vendor APIs only · auditable source.

Reaches your private context

It works inside your shell, so it sees the private repos, internal packages, and local tooling a hosted agent never can. No mirroring your codebase into someone else's VPC.

Private repos · internal tooling · your network.

Runs on the keys you already have

Bring your own model keys and your existing coding agent subscription. No bundled model, no token markup, no second AI contract to justify.

BYO model · BYO keys · your billing.

The async dividend

Your attention does not parallelize.

Supervising interactive sessions is still your focus, all day. @devintern/code moves your involvement to checkpoints: work happens in the background, and the only interruptions that reach you are a spec that needs a human call or a PR ready for review.

With @devintern/code

Kick off · stay heads-down · review diffs

  • Queue several tickets in one command. Runs happen in the background; you get pinged when a diff is ready.
  • Each run gathers its own context from the repo and the ticket. Your head is free for the hard problem.
  • The run closes the loop: draft PR, tracker update, implementation summary posted back. You review the work, not the paperwork.
  • With unattended automation, routine review comments get addressed on the same branch with replies.
  • The feasibility gate flags vague specs back to the tracker with questions before any code is written.

Your day without it

Open sessions · held context · interruptions

  • Five terminal tabs, each mid-session, each waiting on you to approve the next step.
  • Context held in your head for every open run, all day.
  • Break out of deep work to close the loop: PR write-up, tracker updates, handoff notes.
  • Drop everything mid-afternoon for review nits and follow-up pushes.
  • A vague ticket burns a session before anyone notices it was vague.

Delegate tickets. Review PRs.

the routine loop runs without you

What's inside

Built for the way you already ship.

@devintern/code plugs into the tracker, repo, and coding agent you already use; nothing about your workflow changes. Same reviewers, same CI, and you stay the final gate on every merge. The loop below is what makes unattended runs produce mergeable diffs instead of confident mistakes.

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

    The run scans your codebase and the ticket before writing a line. Real files and real context, not a half-pasted spec from Slack.

  • Feasibility gate before the branch

    Ambiguous tickets get flagged back to the tracker with questions before any work starts. Bad specs bounce, they do not become confidently wrong PRs you have to triage.

  • Self-review before humans

    The agent reviews its own diff and fixes what it finds before a human sees it. The first human review is not the first review, and you stay the final gate.

  • Review comments become commits

    With unattended automation, reviewer feedback gets picked up and addressed on the same branch, with replies. Less ping-pong on nits for you and your reviewers.

  • Multiple tickets, one kickoff

    Queue several ticket keys in one command and each run works in the background. Your focus block stays a focus block.

  • 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.

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

@devintern/pm turns a rough prompt, error log, or Figma link into a proper ticket: scope, context, and acceptance criteria, grounded in your codebase. Preview it, fix 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, branches, implements with your agent, 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.

Next step

Install it this afternoon.
Your first PR can land within the hour.

Interactive use is free forever: no signup, no time limit, every tracker and agent included. If it doesn't earn its keep on the first ticket, rm -rf ~/.devintern and forget us.

When you want unattended automation (scheduled ticket pickup plus webhook-driven review handling, self-hosted), a one-time $99 Supporter license covers your own repos. Team is $99 a month for up to 10 developers, less than a single engineer-hour a month; Business is $299 for up to 30. Subscriptions carry a 30-day money-back guarantee, and early pricing is locked in for as long as you stay subscribed.

Source-available under the FSL, converting to Apache-2.0 two years after each release. The worst case is "stops improving", never "stops working".

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

Free for interactive use · BYO model & keys

Also evaluating DevIntern for another role in your org?