devintern
DevIntern is a self-hosted worker that turns ready Jira, Linear, GitHub tickets into pull requests using your coding agent. It runs on local machines with your keys, never sending code to external servers.
Ficha actualizada 23 sept 2026, 1:55 · upstream 23 sept 2026, 1:53 · release code-v2.11.0
Qué es devintern
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
DevIntern is a self-hosted automation tool for teams already using ticketing systems like Jira, Linear, or GitHub Issues. It takes ready-to-go tickets from your tracker and automatically creates pull requests through your preferred coding agent (Claude Code, Codex, Cursor, OpenCode). The workflow runs entirely on your local machine — no code leaves your environment. You review the diff yourself rather than watching an agent ship unreviewed changes.
The tool is designed for teams that want to keep their existing ticketing workflows intact while still automating pull request creation. It eliminates the need for a separate agent platform, webhook infrastructure, or external API integrations. Instead, it runs as a local daemon that polls your tracker, implements ready tickets, and manages its own PR lifecycle.
Key benefits include reduced friction in the review process, faster feedback loops between developers and product owners, and complete control over which code is actually merged into production. The tool also handles edge cases like merge conflicts, stale dependencies, and incomplete reviews by intelligently routing them back to your ticketing system.
- Automate pull request creation for ready Jira or Linear tickets without manual intervention
- Reduce review friction by having the agent critique its own PR diff before any human sees it
- Eliminate duplicate work where multiple agents try to create overlapping PRs from the same ticket
- Keep your existing ticketing workflow (Jira, Linear, GitHub) intact while adding automation
- Run scheduled maintenance tasks as automated pull requests without creating new tickets
- Self-serve code reviews for team members who need quick feedback on their own work
- Runs entirely locally with your existing agent (Claude Code, Codex, Cursor) and keys — no external API calls or server costs
- Supports multiple ticketing systems including Jira, Linear, GitHub Issues, Trello, Asana, Azure DevOps, and plain markdown files
- Self-reviewed PR workflow where the agent critiques its own diff before any human review is needed
- Handles merge conflicts intelligently by merging base branch first then resolving with semantic reasoning
- Supports scheduled automations via cron-like triggers that run full pipelines without manual intervention
- Built-in dashboard at localhost:4400 showing real-time pipeline status and stage-by-stage progress
- Requires a local agent instance (Claude Code, Codex, Cursor, or OpenCode) to be running locally — no serverless alternative available
- Only supports pull request creation; cannot create issues, comments, or other ticket types directly from the worker
- Does not handle complex multi-step workflows that require conditional branching based on dynamic data (e.g., feature flags, environment variables)
- No built-in code review tooling — you must manually inspect diffs and address any issues before merging
- Limited to single-repo or small team use cases; scaling beyond a few repositories requires manual orchestration
- Sentry integration is optional and only works for recurring error groups, not individual incidents
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Install via `bun install -g @getdevintern/code` then run `devintern worker init` to configure your tracker connection, operating policy, and integrations. The daemon runs on a local port (default 4400) with SQLite storage for task history. Use the CLI commands like `devintern PROJ-123 --create-pr` or batch mode `--query 'status=todo'`. For teams using multiple repos, create separate worker instances per repository or use workspace-level configuration in `workspace.toml`. The paid automation tier supports unattended pipelines with scheduled triggers and rate limiting. Always verify your agent's CLI compatibility before running the worker.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.