agentleFS
quanticstudiosquanticstudios/pitwall/AGENTS.md

pitwall

AGENTS.md22 starsChanged 43 days agoMITView on GitHub

A native (Gio, pixel-drawn) terminal multiplexer for running coding agents. A daemon owns PTYs and state; the GUI client draws an aide-style sidebar with agent status next to split terminal panes. Sessions survive the window closing (daemon) and a reboot (store + agent resume). Exported signatures in each package are the contract other packages build against. Implement them as written; if one is wrong, say so in your report instead of changing it. - aide (look and behavior to match):…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repositoryOne other file it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read CONTRIBUTING.md before preparing a contribution.

    line 58
  2. Very specific:

    Never list processes with arguments (ps aux, ps -ef, pgrep -a, /proc/*/cmdline) and never run bare env/printenv: the shell carries secrets.

    line 66
  3. Very specific:

    Never touch ~/.claude/settings.json or ~/.codex/config.toml.

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

pitwall

A native (Gio, pixel-drawn) terminal multiplexer for running coding agents. A daemon owns PTYs and state; the GUI client draws an aide-style sidebar with agent status next to split terminal panes. Sessions survive the window closing (daemon) and a reboot (store + agent resume).

Layout

PackageOwns
internal/modelShared types and aide's activity priority/tier logic
internal/layoutSplit tree types and ops
internal/vtEmulator contract and the emulator behind New
internal/paneOne process in a PTY, feeding a vt.Emulator
internal/protoWire messages, gob framing, socket path
internal/daemonState owner, socket server, wiring of pane/agent/gitstat/store
internal/agentClaude/Codex hook payload to model.Activity
internal/sessionChats' events, deltas, snapshots (Reduce, Apply), Driver
internal/guardThe deny list a guarded tab's hooks check commands against
internal/controlls --json rows, tab and pane addresses, the wait evaluator
internal/progstatusOSC 7501 (Program Status Protocol) parser and record store
internal/gitstatWorktrees and branch stats via git
internal/storePersist state, snapshots, resume commands
internal/logindHold a Linux shutdown or sleep until the daemon saves
internal/repoiconFind a repo's root and its favicon or logo files
internal/logsLog files, a non-blocking log writer, a rate limiter, Redact
internal/updateFind a newer GitHub release, install it over the binary
internal/remoteThe phone page: pairing, device tokens, its HTTP server
internal/qrQR codes for pairing
internal/webThe web protocol: listener, handshake, subscriptions
internal/inputGio events to PTY bytes
internal/ui/themeColors, derived tokens, type and spacing scales, from aide
internal/ui/animEased values, the durations, reduce_motion
internal/ui/kitThe button, popover placement and elevation
internal/ui/sidebarThe sidebar, and the board's drawing
internal/ui/boardThe board's columns, scopes, held cards, from the state
internal/ui/termGrid renderer and pane input
internal/ui/mdviewThe markdown reader: parse, flowcharts, images, its overlay
internal/ui/appWindow, splits, Alt navigation, switcher
cmd/pitwallEntry point (orchestrator only)

Exported signatures in each package are the contract other packages build against. Implement them as written; if one is wrong, say so in your report instead of changing it.

References

  • aide (look and behavior to match): ../aide (a sibling checkout), especially src/renderer/src/components/SidebarTree.tsx, src/shared/workspace-activity.ts, src/main/git-service.ts, the CSS tokens under src/renderer/src.
  • tuios (MIT, Go, read-only, git-excluded): .ref/tuios. Copy whatever code we need from it. Put // Adapted from tuios (MIT): <path> above copied code. Take the part, not the framework around it.

Rules

  • Read CONTRIBUTING.md before preparing a contribution. Send every change to main through a pull request; GitHub blocks direct pushes for everyone.
  • Go 1.27.1 via mise.toml. gofmt, go vet ./... and go test ./... pass before every commit.
  • Stdlib first. A new dependency needs a reason in the commit message.
  • One runnable test per non-trivial piece of logic. No test frameworks.
  • GUI windows only through agent-ws (skill agent-desktop): never launch a window on the user's desktop. agent-ws down <name> when done.
  • Never list processes with arguments (ps aux, ps -ef, pgrep -a, /proc/*/cmdline) and never run bare env/printenv: the shell carries secrets. pgrep -c -f <pattern> is fine.
  • Never touch ~/.claude/settings.json or ~/.codex/config.toml.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.