32a43b5201f79c0749c984d3be3df93e36d00901
worklane --version exited 2: the Cli derive set name and about but never
version, so clap generated no flag. Nothing could say what a given binary
was, which matters here because the opencode tools shell out to whatever
worklane is on PATH, so an agent can be driving a stale build with no way
to notice.
The crate version alone would not have answered it. Cargo.toml is pinned
at 0.1.0 and nobody bumps it per install, so a stale install and a fresh
build both claim the same thing. A build script stamps the short sha
alongside it, giving "worklane 0.1.0 (df97b06)", and falls back to
"unknown" where there is no git directory, as when installing from a
published crate.
propagate_version lets subcommands answer too. This overrides the ticket's
own plan step, which said to skip the sha if it needed a build script.
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%