explaingit

treygoff24/papercuts

Analysis updated 2026-05-18

31RustAudience · developerLicense

TLDR

A CLI tool that lets AI coding agents log small workflow frustrations to a shared file so humans can review and fix the underlying problems.

Mindmap

mindmap
  root((papercuts))
    What it does
      Agent complaint logging
      Append only journal
      Friction tracking
    Tech stack
      Rust
      CLI
      JSONL
    Use cases
      Log agent friction
      Review complaint backlog
      Multi agent safe logging
    Audience
      Developers
      AI agent builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let an AI coding agent log friction it hits, like broken links or bad configs, as it works.

USE CASE 2

Review a backlog of agent-reported complaints and fix the underlying repo or tooling issues.

USE CASE 3

Track resolved and open complaints in a version controlled append-only log.

USE CASE 4

Run multiple agents against the same repo without log file conflicts.

What is it built with?

RustCLIJSONL

How does it compare?

treygoff24/papercutszunelyat/udiomusicrestsend/pipa
Stars313132
LanguageRustRustRust
Setup difficultyhardeasy
Complexity1/54/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

In plain English

papercuts is a small command line tool that gives AI coding agents a way to complain when something in a codebase gets in their way. The idea is that agents constantly run into small frustrations, a broken link, a confusing config file, a test command that only works from a specific folder, and normally they just push through without telling anyone, so the problem never gets fixed. papercuts gives an agent a one line command to log that friction the moment it happens, creating a paper trail a person or another agent can review later and use to actually fix the repo, the tooling, or the docs. Each complaint, called a papercut, gets written to a simple text file at the root of the repo, one line per entry, so the log shows up naturally in version control and travels with the project. There is no server and nothing is sent anywhere. Commands let you add a new complaint, list open ones sorted by how serious they are, mark specific ones as resolved, or attach details like the failed command, its exit code, or an error log. A schema command explains the whole system to an agent using it for the first time. Multiple agents can safely write to the same log file at once, since it uses file locking and appends in a way that cannot corrupt the file. Marking something resolved never deletes or rewrites past entries, it just adds a new event showing it was fixed, so the log works like a running journal rather than an editable database. Teams can choose whether to commit this log file to version control so complaints show up in code reviews, or keep it private and ignore it in git. It installs through Rust's cargo package manager and is released under the MIT license.

Copy-paste prompts

Prompt 1
Explain how papercuts records and resolves complaints without rewriting history.
Prompt 2
Show me how to add the papercuts instructions to my CLAUDE.md so agents use it automatically.
Prompt 3
Help me set up papercuts as a private, gitignored log instead of a committed file.
Prompt 4
What does the papercuts schema command tell an agent about the tool's contract?

Frequently asked questions

What is papercuts?

A CLI tool that lets AI coding agents log small workflow frustrations to a shared file so humans can review and fix the underlying problems.

What language is papercuts written in?

Mainly Rust. The stack also includes Rust, CLI, JSONL.

Who is papercuts for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.