DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to follow one project folder across every agent with Agentacct

Point a work group at a project folder to see which agents worked there and in what order.

Who it is forA developer who switches between several coding agents on the same repository and loses track of which one changed what.

The problemWork on one project is scattered across sessions from different agents, so no single view shows the sequence of changes.

The outcomeA folder-anchored Work group with its sessions drawn on one cross-agent timeline, where you can open and scrub each session.

What you need first

  • Python 3.11 or newer on macOS or Linux, or Windows through WSL, with pipx available (or the signed macOS app from the latest release on macOS 14+)
  • At least one supported coding agent with local session logs on this machine, such as Claude Code or Codex
  • Permission to open a new agent session after setup, because hooks and MCP servers bind at session start

Steps

  1. Run agentacct tui
  2. Open the Work tab
  3. Select the group for your project folder
  4. Open a session from the shared timeline with the enter key and scrub through its steps

Prompt for your agent

Using the agentacct repo at https://github.com/mikehasa/agentacct, open the Work group for the folder <project path> and list the agents that worked there and their most recent sessions. Verify that group totals are shown as sums of the participating sessions, with partial coverage labeled.

Caveat. Each session keeps its own evidence, and the agent that worked on a folder only appears when its logs are readable on this machine.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page