DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to route issues to a coding agent on your own machine with Itsaplan

Install the runner so your local coding CLI picks up tasks from the tracker.

Credentials. The runner works under your own account and the coding CLI can act with your local permissions, so limit what the CLI can reach before assigning it tasks.

Remote script. The runner hands each task to a command that reads stdin, so review what that command is allowed to execute on your machine.

Who it is forA developer who uses Claude Code, Codex, or another coding CLI and wants those tools to take tickets from the team board.

The problemCoding tools work in a terminal and do not see the backlog, so each ticket is copied by hand into a prompt.

The outcomeTasks assigned to an external agent are handed to your chosen coding CLI on your machine, and the reply streams back to the issue.

What you need first

  • Docker and Bun for a local try-out, or a Railway account with a domain of your own for hosted deploy
  • A model or coding CLI for internal or external agents, if you use agents
  • Admin access to the instance to set up agents and API keys

Steps

  1. Read the runner setup in docs/runner.md and install the coding CLI you plan to use.
  2. Install the runner package @itsaplan/runner from the repo's packages/runner folder, following its README. (inferred, check the README)
  3. Register the external agent in the instance under your own account and point the runner at it.
  4. Assign an issue to the external agent or @mention it in a comment.
  5. Check the streamed reply and the coding agent's tool calls on the issue, then review any code changes it made.

Prompt for your agent

Using docs/runner.md in the itsaplan repo, configure @itsaplan/runner for <coding CLI name> on this machine. Assign issue <issue key> to the external agent and report whether the reply and tool calls stream back to the issue.

Caveat. The runner is Apache-2.0 while the rest of the repo is AGPL-3.0, so check the license of packages/runner before you embed it in another product.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page