codenotary

Activity

Stars and mentions · Last 30 days, Oct 7 – Nov 5

GitHub stars12
Mentions1
01234Oct 7Oct 21Nov 5
UTC days · repositories codenotary owns4 repositories

Top repositories

codenotary’s repositories ranked by new forks, as on trending.

Loading

Contributes to

Repositories outside codenotary’s account where codenotary opened or reviewed pull requests in the past 365 days.

Who noticed codenotary

Everyone who starred or forked codenotary’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.

Mentions

3posts
Nov 62 posts
  1. I built AgentMon Live to keep track of Claude Code. Now it has a browser view. Running a few Claude Code sessions at once is great until I forget which one is doing what. One is working through a change. Another has subagents running. A third might be waiting for me, but I won't know until I check that terminal again. I kept bouncing between them to answer a few basic questions: What's happening? Does anything need me? Is the work actually finished? That's why I built AgentMon Live. !Image description It's a Claude Code mod that lets you watch Claude and its subagents work, see costs and usage limits, and spot when something needs your attention. It also checks for unfinished work before Claude says "done". I shared an earlier release recently. This update adds the part I've been most excited about: you can now follow your agents live in your browser. A browser view across your sessions You keep working in Claude Code as usual. Open the browser view alongside it, and you can follow agent activity in real time and switch between sessions running in different terminals. For my workflow, that last part matters a lot. Checking on several sessions means remembering where each one lives, switching terminals, and finding the relevant output. Having a browser view gives me somewhere to look while the work carries on. The pane beside the chat is still available too. If you're working in one session, you might prefer keeping everything together. When several sessions are going, the browser gives you another way to follow them. It's a simple addition to describe, but it's the one I've really wanted to use myself. What I want to know while an agent works Seeing activity is useful. Knowing when to pay attention is more useful. AgentMon brings together running tool calls, subagent activity, changed files, and verification results. It also shows costs and how close you are to your usage limits. !Image description That helps with the questions I keep coming back to: - What is Claude working on right now? - What are its subagents doing? - Is anything waiting for my attention? - How much of my usage allowance is left? - What has actually been checked? I want to be able to glance over, understand the situation, and get back to what I was doing. Checking what "done" means The other part of AgentMon I care about is the completion check. Consider a session where Claude runs the tests successfully, makes another code change, and then reports that everything passes. The earlier test result doesn't verify the latest edit. AgentMon's "done gate" checks the recorded work before Claude finishes. It can catch things such as failed checks, tests that became stale after an edit, and unfinished todos. When it finds unfinished work, it sends that back to Claude once. I still review the result myself. This helps catch some of the things I'd otherwise have to find by reading back through the session. The README explains the checks in more detail. Trying it In a Claude Code session, install it with: /plugin install agentmon-live --marketplace codenotary/agentmon-live Follow the marketplace and scope prompts. You can open the pane with: /agentmon It also works with Code inside Claude Desktop. For that setup, install AgentMon as a mod in Claude Desktop itself rather than through Claude Code in your terminal. The project is open source, with installation instructions on GitHub. If you tried an earlier release, I'd love to hear how the browser view fits into your workflow. I'm especially interested in hearing from people juggling several sessions. What do you find yourself checking most often while your agents are working?

  2. AgentMon Live – Watch Claude Code agents and check their work – Apache 2.0

    1 point
  3. Reddit · · r/ClaudeCode · u/codenotary · codenotary/agentmon-live

    Claude Code mod that checks whether "done" actually means done We've been working on AgentMon Live, a plugin that puts a live monitoring pane beside your Claude Code chat. The main reason we built it: Claude can report that work is finished even when a test failed, the last passing test predates the latest edit, or a subagent left something unfinished. The plugin adds a "done gate" that checks for those conditions before Claude stops. It sends unfinished items back to Claude once. A second model, which doesn't write code, checks whether every part of your request was answered. The pane also shows: - Running tools and subagents - Files edited and read - Latest test, lint, and build results - Context usage and token consumption - Items needing attention, including repeated failures and stuck subagents You can turn the done gate off and customize which sections appear. Install in Claude Code: /plugin install agentmon-live --marketplace codenotary/agentmon-live Requires Claude Code 2.1.308 or later. Apache 2.0 licensed. GitHub - Open source under Apache 2.0.: codenotary/agentmon-live Walkthrough: codenotary.com Curious what you'd want checked before Claude calls a task finished. Failed tests are straightforward. What else do you regularly catch during review?

    1 point · 4 comments

Achievements

Awards earned by the repositories codenotary owns. Select an award to embed its badge.

Gold
01st place finishes
Silver
12nd place finishes
Bronze
23rd place finishes
Awarded repositories
1Owned by codenotary now

Repositories

Ordered by gold, then silver, then bronze.

  1. immudbBest: 2nd by stars, 370 stars012

Every award

Top-three finishes of these repositories in completed trending days and weeks, newest first.

  1. immudb
  2. immudb
  3. immudb

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.