Ansho ReiandClaude Opus 5 580e3cf7f0 (0721739) Show the ticket id and title on the detail overlay's border
The modal named nothing. It showed a description, criteria and a metadata table
belonging to a ticket whose title is nowhere in the text, because content_trim
drops the `# ` heading on purpose: `cmd_show` prints it. The card behind the
overlay carries it, but the overlay covers most of the board, and the seven
characters of id in the metadata table were the only thing identifying what was
open.

The id and the name now sit on the block title, `(1111111) · First one`. The id
goes first because that is how every other view addresses a ticket, and both sit
on the border rather than at the head of the paragraph, so reading to the end of
a long ticket cannot carry them off the screen.

The string is cut here rather than left to the renderer, which truncates an
overlong block title at whatever cell it reaches and would take the id with it.
Cut against the inner width, the id survives whole and the name ends in an
ellipsis where it was trimmed.

`Board::detail` is now a `Detail` carrying the title, the id and the text, since
the title has to travel beside the body rather than inside it.

Written in an opencode session, lost from the working tree to a `git checkout
src/tui.rs` that Claude ran to drop a scratch test, and recovered from the
opencode snapshot store. The diff is unchanged from what was written, bar one
rebase conflict where both sides had added a test helper in the same place.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-21 16:41:26 +02:00
2026-05-14 20:41:40 +02:00

Worklane

Worklane is a local Kanban flow for agentic software development.

Commands

Command Description
worklane or worklane tui Opens the board: four status columns, redrawn when the tree changes. Read only. Opens on backlog, committed and reviewing; d shows or hides done, whose count stays in the footer either way. Arrows or hjkl to move, enter for detail, pgup/pgdn to scroll an open ticket, q to quit
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, --priority flags
worklane ls [status] Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5>
worklane show <id> Shows ticket by UUID prefix (4+ chars), title substring, or filename substring
worklane mv <id> --status <target> [-f] Moves ticket between statuses. Default: forward only, one stage at a time. -f bypasses both restrictions
worklane set <ticket> Replaces fields with --title, --description, --acceptance, --plan, --tags, --due, --priority. At least one required. Changing the title renames the file, keeping the UUID
worklane append <ticket> Adds to a section with --description, --acceptance, --plan. At least one required. The description gains a paragraph; list items go on the end, steps numbered on from the last
worklane check <ticket> [criterion] Ticks one acceptance criterion, by number as shown by show or by a substring. Prompts with the numbered list if omitted, or errors with it when there is no terminal
worklane uncheck <ticket> [criterion] Unticks one acceptance criterion, addressed the same way
worklane comment <ticket> <body> Adds a comment to a ticket by UUID or title
worklane install-skill Writes the embedded agent skill to ~/.claude/skills/worklane/SKILL.md, which Claude Code and opencode both read. Leaves a modified copy alone unless --force; --print writes it to stdout instead

Exit codes

Code Meaning
0 Success
1 An error, such as no matching ticket or an ambiguous search
2 A usage mistake, such as an unknown flag
141 Output was piped to a reader that stopped early, for example worklane ls | head -3

141 is 128 + 13, the shell's way of reporting death by SIGPIPE. Worklane restores the default signal disposition so a truncated pipe is quiet, the way head and sort are, rather than printing a panic. A script using set -o pipefail will see 141 for a case that is not a failure, so guard for it there.

Whether a truncated pipe reports 141 or 0 depends on the size of the output, not on the command. A pipe holds 64 KiB, so a listing that fits lands in the buffer whole and the writer never learns the reader left, giving 0. Only output past that gets far enough to be cut off. Either way nothing is printed to stderr.

S
Description
No description provided
Readme
3.7 MiB
Languages
Rust 97.8%
TypeScript 1.9%
Makefile 0.3%