b6d0b55d4be336fd7aefdff85e0e97615d6dbeaf
should_use_colors only asked whether stdout was a terminal, so there was no way to turn colour off in one, and it was re-evaluated on every color_text call. Honour NO_COLOR by the no-color.org rule, set and non-empty disables whatever the value, with an empty value treated as unset so an inherited one can be cleared. Treat TERM=dumb and an empty TERM as no colour. Decide once in a OnceLock, since none of the three inputs change mid-run. The decision itself is a pure function of its three inputs, so it is tested without a pty. Verified under a real one as well: colour on by default, absent with NO_COLOR=1, absent with TERM=dumb, present again with NO_COLOR set to empty. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Worklane
Worklane is a local Kanban flow for agentic software development.
Commands
| Command | Description |
|---|---|
worklane init |
Creates .worklane/ with backlog, committed, reviewing, done directories |
worklane add |
Creates a ticket in backlog with --title, --description, --acceptance, --plan, --tags, --due, --owner flags |
worklane ls |
Lists tickets, optionally filtered by --status |
worklane show <id> |
Shows ticket by UUID prefix (8+ chars) or title substring |
worklane mv <id> --status <target> [-f] |
Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions |
worklane comment <ticket> <body> |
Adds a comment to a ticket by UUID or title |
Languages
Rust
97.8%
TypeScript
1.9%
Makefile
0.3%