Hi HN - we're Chris and Jacob, and over the past few months, we've been building a way for teams (non-technical and technical) to easily get the agents they need to handle things like creating engineering tickets, drafting pull requests, and code review without context loss.

Today, I'd like to share how this all works end to end with our Slack thread to GitHub pull request flow. And here's a small demo video of how it works made with Remotion: https://www.youtube.com/watch?v=-wDmWIgnBoM

So Choji is a platform where teams can add agents based on their needs in the product development lifecycle. The first step is you connect your knowledge and code bases (e.g. GitHub, Jira, Linear, or whatever you use). Then, connect a place where you get requests (e.g. Gmail, Slack, Intercom, Crisp), then Choji can see the threads as they come or when you command it to e.g @Choji with Slack, and it'll take the request, enrich it with the context it has from your knowledge and code bases to make an actionable eng ticket with an estimated level of effort (e.g. S-XL). Some teams stop here and give the Choji tickets to their teams.

For those who want to go one step further, Choji marks tickets it's coding agent can handle with "Agent-Ready", and if the user chooses, Choji can attempt to one-shot the pull request using the ticket it created as the plan. It makes an ephemeral runner, clones your repo, and then gets to work making the fix. I personally give Choji a group of tickets while I'm making my kids' breakfast in the morning and it's pretty cool to see the pull requests get made. And, if it gets it wrong, you can give Choji more context to try again.

Lastly, we also have a code review agent that reviews pull requests made by you+your team and Choji. If the code review agent finds a matching ticket where the PR is originating from, then Choji can use that originating ticket as context to give a more accurate review of what is in the PR compared to the original intent.

Jacob and I made Choji internally as our collectibles marketplace (Raremarq.com) started growing, and we made our first ticket agent as a way for our non-technical support staff to file tickets from Intercom and Slack quickly. But, as the volume of tickets from Choji kept growing, we figured out a way to make a coding agent to take those tickets and ship the small customer asks ones that were filling the backlog. From there, we've just kept building on top of it and now giving it to more teams to use.

It's still early for us so we'd love your questions and feedback and if you have any integrations you want us to add let us know!