Ansho ReiandClaude Opus 5 88918b2f8a (c628759) Show a page indicator on the detail overlay's border, and bump to 0.16.1
The overlay has scrolled since 1b78a24 and nothing said where you were: a long
ticket opened looking exactly like a short one, so the only way to learn there
was more below was to press pgdn and watch whether anything moved.

`pg 2/8` now sits on the bottom right of the border, through
`Block::title_bottom` with a right-aligned line, which spends no text row. That
is the trade the title already makes on the top border, and the two cannot
crowd each other because they are on opposite borders.

Both of the things this had to get right are arithmetic. `wrapped_height` is
now the one measurement: `last_offset` is it less the viewport and
`page_indicator` takes the same two numbers, so the clamp and the indicator
cannot disagree. A second `line_count` call would be a number free to drift,
and an indicator claiming there is more to read where the scroll refuses to
move is worse than none.

The furthest offset is the last page by definition rather than by division. The
clamp stops at the wrapped height less the viewport, which is not a page
boundary, so the final screenful is partial and dividing reads `pg 2/3` at the
bottom of the ticket. The pages are counted in `scroll_step`, a screenful less
the overlap line, because that is the step the keys take: counting whole
screenfuls names a page pgdn cannot land on, and puts a 30 row ticket in a 10
row viewport at `pg 3/3` two rows short of its end.

Grey, the colour the footer keys and a rendered checkbox take, since this says
where you are in the ticket rather than anything about the ticket. Dropped
whole on an overlay too narrow for it and absent entirely when nothing scrolls,
the rules a corner and the tags row already follow.

`page_indicator` is four numbers in and an `Option<String>` out, so the
arithmetic is pinned without a terminal. The drawn tests answer the two things
it cannot: which border it landed on and what colour it reached the screen in.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 17:22:41 +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 [path...] 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, whose border carries a page indicator while there is more of it than fits, / to jump to the first ticket whose id or title matches, y to copy the selected ticket's short id to the clipboard, q to quit. Each path opens the first .worklane at or above it, the working directory by default. Several paths are monitored together, as a tab per project plus an all tab that merges them, with tab and shift+tab between them
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. --due takes YYYY-MM-DD and refuses anything else at parse time
worklane ls [status] Lists tickets, sorted by priority then title. Optional positional status, and --priority <1-5>, --tag <tag> and --campaign <campaign>, which compose in any combination. --tag matches a whole value of the comma-separated Tags field, case sensitively, so --tag bug does not list a ticket tagged bugfix or one tagged Bug
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 relate <ticket> Records an edge to another ticket with --blocked-by, --regression-of or --relates-to, each repeatable. At least one required. Only the ticket named is written; show derives the other end by scanning. mv refuses to move a ticket blocked by one that is not done, unless -f
worklane chown <user> <ticket> Sets the Owner field, the only command that writes it. Free text, checked against nothing. User first and ticket second, after Unix chown
worklane check <ticket> [criteria...] Ticks acceptance criteria, each by number as shown by show or by a substring. Several in one call, or all for every one of them. Prompts with the numbered list if none is given, or errors with it when there is no terminal
worklane uncheck <ticket> [criteria...] Unticks acceptance criteria, addressed the same way
worklane comment <ticket> <body> Adds a comment to a ticket by UUID or title
worklane install-skill [skill] Writes the embedded agent skills to ~/.claude/skills/<skill>/SKILL.md, which Claude Code and opencode both read. Three ship: worklane teaches the CLI, worklane-review reviews a finished ticket against the code that claims to close it, worklane-plan grooms the board as a whole, its priorities, due dates, tags and campaigns. Every document unless one is named. Leaves a modified copy alone unless --force; --print writes one to stdout instead and needs the name

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%