agentglass

Activity, over time

Daily observations from the public event archive.

Attention

Daily stars & forks

Loading attention chart

Star accumulation

Cumulative stars

Loading star accumulation chart

Pull requests

Daily opens & merges

Loading pull requests chart

Conversations

Daily issues & comments

Loading conversations chart

Community

Daily accounts & reviews

Loading community chart

Releases

Daily releases

Loading releases chart

Mentions

2posts · 30d
Nov 30 posts
  1. 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

    1 like
  2. Reddit · · r/ClaudeCode · u/serallap

    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.

    2 points · 1 comment

Latest stargazers

The last 10 distinct accounts we observed this year.

Most active participants

PR, issue, comment & review events in the past year.

Packages

Scan pending.

README badges

Embed a badge in your README or website.

Live mentions · last 30 days
SirAllap/agentglass mentions in the last 30 days