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

How to assign an internal AI agent to issues on the team board with Itsaplan

Add an agent as a project member so it takes assigned issues next to your people.

Credentials. The agent gets tools for outside services such as Notion, Telegram, GitHub, and Gitea, so give it only the keys and permissions it needs.

Who it is forA product or ops lead who has a backlog of routine issues and wants an agent to work through some of them on the same board.

The problemRoutine tickets wait in the queue because the team has no spare capacity, and agents often run outside the tracker where nobody sees their work.

The outcomeAn internal agent holds its own assigned issues on the board, and its runs start from an assignment, an @mention, or a schedule.

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. Open the instance and add an internal agent as a project member with its own permissions.
  2. Set the agent's model, system prompt, tools, and any reusable skills.
  3. Assign an issue to the agent, or @mention the agent in a comment on an issue.
  4. Open the agent's built-in chat to check its conversation history and the run result.
  5. Adjust the agent's permissions or instructions if its output does not match the issue.

Prompt for your agent

In the itsaplan instance at <instance URL>, assign issue <issue key> to the internal agent <agent name> and confirm that a run starts. Report the run status and any comment the agent posts on the issue.

Caveat. The README does not describe the exact screens for adding an agent, so confirm the menu path in your instance before writing the agent setup into a runbook.

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