Skip to content

kyb v0.3.2

Choose a tag to compare

@github-actions github-actions released this 27 Oct 03:50
· 66 commits to main since this release
ee34dfb

kyb v0.3.2 for aarch64-apple-darwin (Apple Silicon), Docker (linux/amd64, linux/arm64) and crates.io. Intel macOS is not supported.

A patch release with one addition: deadlines on tasks, which the server surfaces on its own (#27, #28).

Deadlines on tasks

A date written into a task's title as prose can be neither sorted nor noticed. A task now carries it as data:

  • due: YYYY-MM-DD, or a date-time with its zone (2026-03-14T17:00:00-07:00). A time without a zone is refused.
  • hard: missing it has consequences outside the team (an expiry, a contract, a regulator). Hard deadlines come first and are surfaced earlier.
  • remind_days: how far ahead to start surfacing it. The default is 14 days, or 30 for a hard deadline.
  • waits_on with expected: for a date that depends on an event. The provisional date is reminded on, and marked provisional, until the real due is set.

The fields live in the frontmatter like every other field. Moving a date is a new version, so kyb history and kyb diff show when it moved and who moved it. A deadline field left out of a write keeps its stored value, so rewriting a task never drops its due date; clearing the date clears the deadline whole. Tasks without a deadline are stored exactly as before.

kyb task --key task-renew-api-cert --title "Renew the certificate" --due 2026-03-14 --hard <<< "body"
kyb task-status task-renew-api-cert --due 2026-03-21     # no --status needed to move only the date
kyb deadlines [--within 14d] [--overdue] [--hard] [--tag a,b] [--assignee A] [--json]

Deadlines in every read answer

/search, /knowledge/{key}, /tasks and /incidents, and with them every CLI and MCP read, carry a deadlines block when an open task is late or inside its reminder window. The block holds up to five items, hard ones first and then by date, each with its days_left. A query scoped by tag shows that area first. When nothing is due there is no block at all. The CLI prints it as a short banner on stderr, so stdout stays the server's JSON:

kyb deadlines, today 2026-03-16: 1 overdue, 1 due soon
  2d late    HARD task-renew-api-cert  Renew the certificate  (due 2026-03-14)
  in 4d      task-answer-quote  Answer the vendor's quote  (expected 2026-03-20, waits on the quote)

To leave the block off, use --no-deadlines, ?deadlines=false, or MCP "deadlines": false.

GET /deadlines (kyb deadlines, MCP kyb_deadlines) is the full calendar: every open task with a date, grouped overdue, this week and later. Closed tasks, and tasks archived without closing, never appear.

A bare date is judged by the caller's calendar: the CLI sends its own date as X-KYB-Today. Other callers get the server's date in its TZ. The image now ships tzdata, and Compose passes TZ (default UTC).

The server advertises a new deadlines capability. The CLI checks it before sending a deadline flag, --no-deadlines or kyb deadlines, because an older server would silently drop the fields.

KYB reminds; it does not schedule. There are no notifications and no recurrence. The agent skill has a recipe for a session-start hook that prints kyb deadlines --within 14d.

Also

  • The agent skill now states that --history searches every version, the current one included, and that --as-of and --changed-between are lexical-only (#26).

Install

brew install alex09x/apps/kyb          # Apple Silicon
cargo install knowyourbusiness --locked  # kyb-server only
docker pull ghcr.io/alex09x/kyb:v0.3.2