Stars and mentions
Last 30 days, Oct 4 – Nov 2
Package downloads
Top repositories
SirAllap’s repositories ranked by new stars, as on trending.
Contributes to
Repositories outside SirAllap’s account where SirAllap opened or reviewed pull requests in the past 365 days.
Who noticed SirAllap
Everyone who starred or forked SirAllap’s repositories since the archive began in 2011.
Notable accounts
Ordered by the stars their own repositories have received.
Biggest fans
Accounts that starred the most of these repositories.
Breakout weeks
Each repository’s best week of new stars, with the release published around it.
- Gold
- 01st place finishes
- Silver
- 02nd place finishes
- Bronze
- 03rd place finishes
- Awarded repositories
- 0Owned by SirAllap now
No trending awards yet
None of the repositories SirAllap owns has finished in the top three of a completed trending day or week, by stars, forks or PR authors. See who is trending now.
A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.
Mentions
I kept losing track of which coding agent was stuck on a permission prompt, so I built agentglass: terminals, PRs and approvals for Claude Code, Codex, Gemini CLI and OpenCode in one window. One agent runs the others. Free, MIT, local. SirAllap/agentglass
Three months on, one agent runs the others and I mostly answer questions Back in July I posted agentglass in r/ClaudeAI, the app I made to see what my Claude Code sessions were doing. A lot of you tried it and a few sent PRs. This is what it turned into, and it's not really a viewer anymore. The thing that changed my day is the orchestrator. Each project gets one lead agent. It reads the repo, keeps a queue, and hands work to worker agents in their own tmux tabs. I write the rules once in a plain file: what it may start, which model, how many workers. The workers can't push or merge. That stays my click. So my job went from walking through panes to answering questions. When a worker needs a permission or a decision, it shows up at the top, and I answer it from the desk or from my phone. It isn't only for Claude either. Codex, Gemini CLI and OpenCode sessions sit in the same window, and the lead can hand work to any of them. The rest is still there: real terminals on your own tmux, diffs, a PR board with CI, a git panel, and a browser the agents can drive with your logins. How it got built: almost all of it with Claude Code, and for the last few weeks by agentglass itself. The lead agent splits the work into briefs, Sonnet workers write the code in their own worktrees, and I review and merge. What I learned: a worker is great at a bug with a failing test and bad at anything a person has to look at, so screens and wording still come back to me. And the slow part was never the agents. It was me noticing they were waiting. Fair warning, same as last time. It's built around how I work. I use it on Linux every day. The macOS build is unsigned and I don't own a Mac, so if you have one and ten minutes, that helps more than anything. Demo with fake data, no install: sirallap.github.io Repo, MIT: SirAllap/agentglass If you already run more than one agent at a time, I'd like to know how you keep track of them, and what you'd rip out of this.