Terminal app
TrackLin.es in the terminal: My work, mentions, projects, boards and backlogs. Create, edit, move, assign and comment on tickets without leaving the keyboard. It uses your terminal’s colours, so it follows your theme. Source and releases: github.com/TrackLines/tui.
Install
- Make a Personal key in Your settings → API keys. Leave Read only unticked to move and comment; a read-only key can still browse.
- Save it (or set
TRACKLINES_API_KEYinstead):mkdir -p ~/.config/tracklines echo 'tl_p_…' > ~/.config/tracklines/key chmod 600 ~/.config/tracklines/key
- Download the file for your machine from Releases:
- Linux (x86)
tracklines-linux-amd64- Linux (arm)
tracklines-linux-arm64- macOS (Apple silicon)
tracklines-darwin-arm64- macOS (Intel)
tracklines-darwin-amd64
Then make it executable and put it on your path. For example, on Linux x86:
curl -fLo ~/.local/bin/tracklines https://github.com/TrackLines/tui/releases/latest/download/tracklines-linux-amd64 chmod +x ~/.local/bin/tracklines
- Run
tracklines.
On macOS, the binary isn’t signed. Downloaded with curl it runs as it is; downloaded in a browser, macOS blocks it until you run:
xattr -d com.apple.quarantine tracklines-darwin-arm64
On Windows, build it with Go 1.26 or later:
go install github.com/tracklines/tui/cmd/tracklines@latest
Keys
Each screen lists its own keys at the bottom, and ? shows the ones that work everywhere.
- Everywhere
- 1 My work · 2 Projects · 3–5 your most used projects · / search · t go to a ticket (TL-308) · esc or q back · Q quit · ? version, updates and keys
- Lists
- j/k move · g/G top/bottom · h/l slide a long title · enter open · r reload
- Backlog
- n new ticket · s sort · f filter by labels
- Board
- h/l column · j/k ticket · H/L move the ticket a column · n new ticket here · f follow a running standup or refinement
- Ticket
- e edit · m move · c comment · a assign to you
- Writing
- like vim: esc normal mode, :w save, :q leave (or keys = standard: ctrl+s save, esc cancel)
What it doesn’t do
It’s for the everyday work. You can follow a standup or refinement someone’s running, but hosting them, settings and API keys stay in the web app.
Config
Optional: ~/.config/tracklines/config, one name = value per line (config.example has them all).
keys = vimorstandard: how writing tickets and comments works.backlog_sort = manual,newestoroldest: the order a backlog opens in.update_check = on: a release build looks for a newer one when it starts;?thenuinstalls it, checked against the release’s checksums.reports = on: the app’s own failures (the API unreachable, a crash) go to Bugfixes so they get fixed. Never your key, your searches or what you write.offstops it.