Skip to content

v0.11.0

Choose a tag to compare

@github-actions github-actions released this 27 Oct 00:35
· 74 commits to main since this release
700385e

Breaking: stricter CLI parsing

Scripts relying on input silently accepted by 0.10.0 must correct it before upgrading. The following now exit with code 2:

  • Unknown or misspelled --flags, such as --captur=50 (#346).
  • Flags belonging to another subcommand, such as send --capture=50 (#348).
  • Boolean flags with values other than true or false, such as --enter=1; use --enter=false to disable a flag (#338).
  • Invalid --diagnostics intervals, including non-numeric, non-positive, false, and values above 2147483 seconds (#342).

Added

  • Added a bundled omp (Oh My Pi) pattern set for pluk watch --cli=omp.
  • pluk watch now warns once on stderr when the --cli name has no pattern set, and pluk patterns --cli=<name> reports no pattern set instead of printing an empty set.

Changed

  • pluk attach now writes its progress, warnings and status messages to stderr, and the JSONL event schema is documented in the README as a stable surface.
  • Releases publish to npm via Trusted Publishing (OIDC) through the npm GitHub Environment; the NPM_TOKEN secret is no longer used (#303).

Fixed

  • Diagnostics written to stderr no longer carry ANSI colour codes unless stderr is a TTY and NO_COLOR is unset; a small leveled log() helper is added in src/diagnostics.ts.
  • pluk sessions no longer reports STATE/CLI as unknown when raw_output events (from pluk attach with raw capture) flood the log tail; raw lines are skipped when sizing the tail window.
  • pluk patterns and pluk subscribe now derive the builtin CLI fallback list from BUILTIN_PATTERNS, so it includes codex and aider and cannot drift.
  • pluk subscribe and pluk watch now reject an empty --filter= value with an error (exit 2) instead of silently ignoring it.
  • pluk watch now emits raw_output events when no pattern set exists for the chosen --cli, as its warning promises, without needing --include-raw.
  • Log rotation now also enforces PLUK_LOG_MAX_BYTES: after trimming to PLUK_LOG_KEEP_LINES, the oldest kept lines are dropped until the log fits under the byte cap, so it no longer stays over the cap and gets rewritten every 30s.
  • pluk patterns now honors --patterns-dir, so a custom pattern set is shown (and its CLI names listed) instead of a false "no pattern set".
  • tool_call_started events no longer cut an emoji or other astral character in half at the 120-character input_preview limit; truncation now counts code points, so the preview never ends in an invalid lone surrogate.
  • tool_call_started events no longer cut a ZWJ emoji sequence, flag or base-plus-combining-mark character in half at the 120-character input_preview limit; truncation now counts grapheme clusters.
  • pluk sessions no longer shows NaNd ago (or sorts a session first) when a log event carries an unparseable ts; such timestamps are ignored for last activity.
  • pluk attach no longer word-splits pluk/rationguard paths resolved from PATH when they contain spaces; the resolved path is shell-quoted so the pipe-pane, rationguard spawn, and watcher cleanup pattern see a single word (#274).
  • Bare value-taking flags (e.g. pluk send s --text hello, --run-dir /tmp/x, --filter x) are now rejected with exit code 2 and a --flag=<value> hint instead of being parsed as the string true (which typed true into the agent pane); fixes #278.
  • Log rotation now applies the PLUK_LOG_MAX_BYTES cap even when the log has fewer than PLUK_LOG_KEEP_LINES lines (#283).
  • pluk watch --capture=<ms> now rejects fractional intervals such as --capture=1.5, accepting only positive integers as documented (#291).
  • tool_call_completed events now report duration_ms in milliseconds ((2.3s) → 2300) instead of passing the on-screen seconds figure through unchanged (#294).
  • pluk subscribe without --from-beginning no longer replays the kept tail of the log as new events when the log is rotated before the first new line arrives; the subscriber now remembers the last line already in the file at start-up and resumes after it.
  • pluk send --session=<name> / pluk-send --session=<name> no longer drops a positional text word that happens to equal the session name; the leading positional is treated as the session only when --session is absent.
  • pluk sessions now prints the LAST ACTIVITY and EVENTS headings with a gap between them and aligns every row with its column heading; the table matches the README example again.
  • pluk attach --rationguard now scopes its stale-watcher reap (pgrep -f) to the invoking user's processes, so another user's process with a matching command line no longer makes kill fail and abort the attach before the rationguard watcher starts.
  • pluk attach --cli=copilot now launches the standalone copilot CLI (the gh copilot extension was retired) and --dangerous maps to --allow-all-tools for it.
  • pluk --help, pluk sessions and pluk patterns no longer emit ANSI colour codes when stdout is not a TTY or NO_COLOR is set; previously only stderr was gated.
  • pluk attach now wires tmux pipe-pane before launching the CLI, so start-up output (trust dialog, login prompt, model line) is classified instead of lost (#331).
  • Document the real PLUK_RUN_DIR default ($XDG_RUNTIME_DIR/pluk, else /tmp/pluk-<uid>) in the README and the session-monitoring runbook (#333).
  • pluk send no longer loses a trailing ; (tmux treats an argument ending in ; as a command separator); the text now reaches the pane byte-for-byte (#335).
  • Boolean flags such as --enter, --literal, --verbose and --dangerous now reject values other than true/false (e.g. --enter=1) with exit 2 instead of silently turning the flag off; --flag=false is the explicit off spelling.
  • pluk attach now warns on stderr when --command, --cli-args or --dir are passed for a tmux session that already exists, instead of silently ignoring them (#340).
  • watch/subscribe --diagnostics=SECS: a non-numeric, non-positive or false value (abc, 0, -5, 5min, false) used to silently run at the 60s default; it is now rejected with exit 2, as are values above 2147483 s that would overflow setInterval (#342).
  • Cap very large finite periods passed to the startDiagnostics library API at Node's maximum timer delay (2147483.647 seconds) instead of overflowing into a 1 ms reporting loop; the CLI already rejects out-of-range --diagnostics values with exit 2 (#344).
  • pluk now rejects unknown or misspelled --flags (e.g. --captur=50, --entr) with an error (exit 2) instead of silently ignoring them.
  • pluk watch --capture now bounds each tmux capture-pane poll with a timeout so a hung tmux server is counted as a capture failure (visible in --diagnostics) instead of freezing the watcher silently (#353).
  • pluk attach --rationguard no longer aborts a half-wired session when a stale watcher PID has already exited before kill; stale watchers are reaped per PID, already-gone PIDs are ignored, and other kill failures print a warning and continue.
  • pluk attach --dangerous now passes --yolo to gemini and --yes-always to aider; a CLI with no known auto-approve flag now prints a warning even without --verbose.
  • pluk attach --dangerous now launches goose with GOOSE_MODE=auto instead of the nonexistent --non-interactive flag, which made goose exit on an unknown argument.
  • Subscriber tail mode preserves a partially written event at startup and delivers it once its terminating newline is appended, instead of dropping it.
  • Classifier reports the tool name for Claude tool lines such as ● Bash(ls) instead of mistaking the one-word argument for a (kind) suffix.
  • attach: the --dangerous restart hint for an existing session now includes --cli-args (#370).
  • pluk attach now validates the CLI command and arguments before creating the tmux session, so a bad --cli-args (e.g. an unterminated quote) is reported as a usage error (exit 2) instead of leaving an orphaned session with pipe-pane attached.
  • pluk sessions now widens the SESSION and CLI columns to fit the longest value, so rows with long session or CLI names stay aligned with the header (#375).
  • attach: splitShellWords keeps explicitly empty quoted arguments ("" / '') instead of dropping them, so --cli-args/--command argv is no longer shifted (#381)
  • pluk attach --rationguard now also kills existing watchers that were started with a custom --rationguard-bin, so re-attaching no longer stacks duplicate watchers.
  • pluk attach rejects invalid --rebuttal values with exit code 2 before touching tmux, and warns when --rebuttal or --rationguard-bin is ignored without --rationguard (#280).
  • Reject flags that belong to another subcommand with exit 2 and a command-specific help hint instead of silently ignoring them (including flags passed to version). Valid invocations are unchanged; help now lists all supported per-command flags, and a table-driven unit test checks every command against the flag union (#348).
  • Mark command_received as reserved in the event documentation: pluk send / pluk-send does not currently emit it.
  • Keep Classifier.commandReceived() sequence numbers in an independent, increasing command counter without changing subsequent classified or raw-output event sequence numbers.
  • pluk attach --cli=omp --dangerous now passes --approval-mode yolo as two arguments; previously omp received a single --approval-mode yolo token and the flag had no effect.
  • pluk --help and the README no longer point to a Go pluk binary; the subscribe help line now names pluk watch as the usual publisher.
  • --help / -h after a subcommand (for example pluk watch --help) now prints usage and exits 0 instead of being ignored.
  • --help anywhere is always treated as a help request (as it was before, via parseArgs), even inside pluk send text. A bare -h after the send session positional is passed through as text.
  • pluk watch --capture --include-raw now emits raw_output events (once per changed frame) instead of silently ignoring the flag.
  • pluk watch now warns on stderr when --pane is passed without --capture, and --capture= (empty value) is rejected with exit 2 instead of silently selecting stream mode.

Security

  • SECURITY.md now names security@hivecommons.dev (the organization's published security.txt contact) as the primary channel for reporting vulnerabilities, so the policy has a working private route whether or not GitHub private vulnerability reporting is enabled for the repository.