Skip to content

v0.15.0 — CLI 不再静默回落到全局活跃指针;写操作打印 resolved workspace

Choose a tag to compare

@evolution301 evolution301 released this 10 Nov 11:36
· 2 commits to main since this release

[0.15.0] - 2026-11-10

Breaking — the CLI no longer falls back to the global active-project pointer

With three towers alive (evergocasa / prl-ops / offroadleagues), running a command
in a directory that has no tower.toml silently resolved against the active
project: tower say ops deputy "…" answered unknown role 'deputy' (its roles
came from another tower), and the same path would have misrouted dispatch /
accept / relay. Field report 2026-11-10.

  • Resolution is now exactly --workspace > tower.toml found walking up from
    cwd > a loud error.
    ~/.tower/binding.json and the tower projects use
    pointer are no longer consulted by the CLI; they exist for the GUI panel and
    plugin reconnection only.
  • Every write command announces its target: resolved workspace = <path> on
    stderr (stdout stays a single JSON document under --json). Covered:
    dispatch, accept, rework, relay, say, escalate, batch, restate,
    review, attention claim|resolve.
  • READMEs document the rule and the pointer's scope; regression tests pin that a
    registered+active tower elsewhere is never touched from a foreign cwd.