Why not using GitHub as backend?

[asgarovf]

I have been building a similar tool for almost 2 months that works with multiple AI providers, including Codex. The tool executes tasks in auto-approval mode on Docker sandboxes for safety. Previously, I also had a separate UI where I managed the task, documents, comments, and more. However, I think GitHub CLI is enough to achieve what we are trying to do, and then I migrated my tool to work with GitHub.

Check it out: https://github.com/asgarovf/locusai
Demo: https://www.youtube.com/watch?v=JmHeKq3Ty0s&feature=youtu.be

[Octane0411]

Good work. This direction makes sense. And we’re building symphony-tsas a TypeScript implementation of Symphony, we’re also considering integrating GitHub Projects into it.Linear is a strong starting point, but we also think the Symphony model should expand beyond a single backend over time.

[jaeko44]

We tried this with Bosun but it will hit rate limits if you use the github API too much

Honestly an internal first board and syncing occasionally would be better than using it as your source of task management since you need the github API for a ton of other things like creating PRs, etc so you don't want to get rate limited trust me.

[asgarovf]

Rate limiting is a valid concern, but GitHub gives you 5000 requests per hour per user. Most task management operations are low frequency. 5000 is a generous limit IMO. I haven't had an issue so far.

[jaeko44]

It's not that law when you need to continiously update tasks with the state progress, move it around, continiously check what PR's are open, etc. There's a lot of gh calls.