A plaintext, git-tracked issue tracker. Issues are markdown files with
YAML frontmatter, stored in .tisket/ inside your git repo. No external
service, no API tokens, works offline. Built so coding agents can read
and write issues as ordinary filesystem operations instead of jumping
out to a hosted API.
cargo install --git https://github.com/cjohnhanson/tiskettisket init # set up .tisket/ in a git repo
tisket issue create "Fix the thing" # create an issue
tisket issue list # list open issues
tisket issue list -s todo # filter by status
tisket issue show ab12 # full issue details
tisket issue edit ab12 --add-label urgent
tisket issue close ab12 # move to .closed/
tisket search "TLS|certificates" # regex search across all issues
tisket docs [topic] # bundled documentationEach issue is a file: a 4-character random prefix, a slug derived from
the title, YAML frontmatter for metadata, and a markdown body. Closed
issues move to .closed/.
.tisket/
default/ # project directory
ab12-fix-the-widget.md # open issue
.closed/
cd34-old-resolved-thing.md # closed issue
Issues have a status lifecycle: discovery → todo → in_progress →
done (or cancelled). Issues can also be blocked or paused.
Each issue has an optional ## Scratch Notes section, separated from
the issue body. Agents append working memory there (investigation logs,
dead ends, intermediate findings) without touching the problem
description above.
tisket scratch ab12 append "Confirmed: bounds check missing on line 42"
tisket scratch ab12 readWhen listing or showing issues, tisket reads the same issue file from
every other branch and compares field by field. If another branch has a
different status, assignee, or priority, tisket flags it with a * and
names the diverging branches — so you find out two branches moved the
same issue forward before merge clobbers one side.
- What is Tisket? — design, file format, status lifecycle
- Getting Started — first issue walkthrough
- CLI Reference — complete command documentation
Part of a loose ecosystem of plaintext, git-tracked, agent-readable tooling.
- zettel — zettelkasten knowledge base
- almanac — agent skill aggregator
- belmont — secrets manager for LLM agents
- mdstore — frontmattered markdown library this is built on
- codelikecody — workflow engine that bundles these
MIT.