Bug Fixes

• The git status fixtures no longer race their own cleanup. A test repository's commit and merge can leave a detached git maintenance writing under .git/objects as the temp directory is removed, which failed TestLoadFileTreeRealGitConflict on CI and stopped the v1.15.0 release workflow before anything was published. Fixture repositories now disable auto-maintenance at init. v1.15.0 was tagged but never released; its changes ship here as v1.15.1.

v1.15.1

Compare

Choose a tag to compare

Features

• The @ project switcher is a compact list, a card grid, and two dates that mean something. The switcher opens on a compact list with column headings and full-row click targets, switchable to a three-column card grid, and a shared sort control offers Last activity, Name and Date added with a direction. Sort, direction and view persist across launches. Neither date existed before this: ProjectConfig.AddedAt is written once by config.AddProject, the single Load-mutate-Save boundary the TUI and sidecar project add already share, so the CLI records it and project list --json reports it. It means registration with Sidecar, not the directory's birth time and not the first commit, so the control says "Date added" rather than claiming a creation date Sidecar does not have. Last activity is the latest Sidecar event recorded against the project — binding, at launch and on every switch, which sidecar project switch records through the same code; creating a shell in a project does not mark it active and nothing watches terminal output. Reading it touches no filesystem, git or tmux, and writing it happens in a tea.Cmd. Projects registered before this read Unknown and are never backfilled; an unknown date sorts last in both directions, because "not recorded" is not a date and reversing the order must not promote it. internal/projectlist is the state-free core, mirroring internal/workspacelist's vocabulary so the two collection surfaces answer the same question the same way.

• Overlay popovers are mouse-interactive, and hover no longer bleeds through them. The switcher's sort dropdown opened on a click but its options could not be clicked, and hovering its chrome lit up the project cards underneath. In the modal library, an overlay now registers a backdrop region over its own bounds that absorbs stray clicks and clears the hover id, indexes its focusables into the modal's focus positions and hit map with viewport clamping, and grows the viewport up to its maximum when the overlay is taller than the modal's natural content so option rows are not clipped. (td-3a434f)

• create shell --cwd, and a prompt receipt that says whether the bytes landed. sidecar create shell --project sidecar --cwd ~/code/tui --name publisher starts a managed shell somewhere without changing which project owns it — the two facts are stated separately rather than inferred from each other. Relative paths resolve from the caller's directory, ~ from the caller's home, and the directory must exist before tmux or durable state is touched; the resolved path is the shell's live cwd, its recorded workDir, the provider launch cwd and the cold-restore cwd. --cwd always creates a managed workspace row and is refused with --split, whose live terminal has no durable shell record. Separately, sidecar agent prompt --json now carries receipt.submission (submitted, not_submitted, unknown), receipt.wait, and the pinned receipt.target, on success and inside the error envelope alike. A timeout after delivery is still exit 1 with code timeout, but it now proves the prompt was submitted and only the wait expired — so an agent reading the receipt knows not to send it again. unknown means a write or transport may have landed and is equally unsafe to retry automatically. (td-6b63bf)

• Sidecar can bind a Hermes Agent session. sidecar agent integration install hermes drops a plugin into <hermes home>/plugins/sidecar-agent-state/ and adds one line to plugins.enabled in your config.yaml, so a pane running Hermes records which conversation it is running and a cold restart can offer to resume that exact one. The binding lands at process start rather than a turn in, which is earlier than any other agent Sidecar integrates with. Uninstall gives your config.yaml back byte for byte: it removes only Sidecar's own line, leaving your other plugins, your comments and your indentation where they were. Traced against hermes 0.17.0 and corroborated by hermes sessions list printing the same id. (td-73c4ff)

• The plugin browser answers the pointer everywhere. Every protocol plugin's tab and pane now has the interactions the rest of Sidecar has: clicking a pane focuses it, clicking a row selects it and a second click opens it, the query row and the View control are click targets, the wheel scrolls the box under the pointer, both the table and the detail have draggable scrollbars, the gap between them is a drag rail whose split is remembered per plugin, and +/- resize it from the keyboard. Tab and Shift+Tab reach the browser through an opt-in focus-ring capability, so Files, Git and Notes keep their own Tab behaviour. The "no action here" flash is gone: an action that does not apply is absent from the hints and inert on its key. The rules are in the design language under Pointer parity. (td-62b81c)

• Plugins declare filters, and a page that could not answer everything says why. A collection can declare up to eight choosers or text filters; the host draws them in the View modal, folds the applied scope into the sort pill, persists them with the tab, and sends list only the filters that differ from their defaults. A page may report what it omitted, a failed outcome, and per-source coverage rows; clicking the outcome word or a notice, or pressing c, opens a coverage modal with a Source, State, Elapsed and Reason table and a Retry button. outcome describes only the page's own rows. Recall is global first with a profile chooser over every configured profile, and no longer narrows to the Sidecar project on its own, which is what had made every documents source answer empty. --filter ID=VALUE reaches the same filters from sidecar plugin check, plugin call, sidecar open --plugin and the layout spec. (td-9ca6a7, td-786e42)

• Query bars are one field with real editing keys. Every / search bar in Sidecar — the plugin browser, both workspace sidebars, doc search, the file browser's tree and content search, git history search and path filter, both notes searches, Sessions search and both terminal searches — is the same field, backed by the text input the modals use, so option-arrow, option-delete, home, end, cursor movement and paste work in all of them, a clickable × clears the query wherever the row has a hit map, Esc clears then blurs, and the arrow keys hand the keyboard to the list beneath. In the plugin browser, down from the field moves to row one, k on row one returns to the field with a key-repeat guard, and the detail follows the cursor after a short quiet period with a superseded load killed rather than left running — the rule the Files plugin already followed, now named in the design language. (td-e8cceb, td-45898b)

• One selector control, and selectable text in every detail pane. The Create Workspace kind chooser is now modal.Select in the modal library: segmented under five choices while they fit, a bordered ❯-cursor list at five or more, scrolling past a visible cap, disabled rows kept visible with their reason, and a border that follows focus like an input's; every View modal uses it, and a modal sizes to its widest control. The plugin browser's detail, td issue cards, resource cards and diff panes are selectable with the pointer — drag, double-click a word, triple-click a line — and alt+c or super+c copies to both the system clipboard and the terminal over OSC 52, through the same engine file panes already used; the help modal names the shift or option bypass for the terminal's own selection. (td-21aafa, td-c6904c, td-2b8f79)

• A plugin authoring guide and a Plugins page. docs/guides/active/creating-plugins.md takes an author from a CLI to a plugin that passes sidecar plugin check, with a runnable Python example under docs/guides/examples/hello-plugin/ that a test keeps honest; docs/reference/plugin-protocol.md is the single authority for the frozen contract; and the documentation site's Plugins page replaces the Terminal Resources page, which described a configuration shape that never existed, with the sidecar plugin verbs added to the site's CLI reference. (td-40eb97, td-ade3a3)

• Configuration -> Agents -> Integrations is a table. One line per agent Sidecar can install for, with its name, its status, and Install, Update, Repair and Remove always in the same column, painted dimmed on the rows where the service would refuse them. Moving the cursor changes only which row is highlighted, and every action that is on offer can be clicked on any row without selecting that row first. Wide terminals also get the authority tier and the file the integration lives in; narrow ones keep the actions and drop the rest. Underneath the table, a fixed-height detail box follows the cursor with that agent's files, tier and demotion reason, CLI path and version, last lifecycle report, and diagnostic. Agents Sidecar has surveyed and ships nothing for collapse into one line instead of taking a row each. The count of an agent's known gaps is gone: they are gaps in that agent's own hook contract rather than faults in Sidecar, and the page names sidecar agent integration status <agent>, which lists them. (td-20e857)

• External plugins are hosted without turning a flag on first. plugin_protocol and terminal_resource_providers both default on. An install with nothing configured still starts nothing — no describe pass is even scheduled when no plugin or provider is configured for the section a flag governs — and turning a flag off still stops every one of that section's child processes while leaving the configuration in place. terminalResources.providers is now a read-only alias of the plugin configuration: it is still read and still dispatched on the frozen sidecar.terminal-resource/v1 identifier, and Sidecar no longer writes the section, so it stays exactly as you wrote it. plugins.<id>.enabled is the documented switch for the embedded panels, with the tasks_plugin and notes_plugin feature flags as read-only aliases for one more minor release: each answers only while its config key is absent, and the Feature Flags page now reports the panel's own answer rather than the flag, so it can no longer disagree with the Panels page. (td-944274)

• An empty plugin detail box shows the plugin's next collection. In a Tab placement, where the box stands beside the list, a plugin with a second collection gets that collection drawn there — its title, what it currently says, and its first rows — instead of a card of help text. A plugin's next collection is usually the ledger that explains the list, so "no matches" and "why" are on screen together and an abstained page can be checked where it is read. It is listed once, without a query, and never when its search is required; a plugin with one collection keeps the help line, and a pane, which shows one shape at a time, is unchanged. (td-6c49c5)

• A narrow plugin list keeps its rank beside the name. Below the table floor a row still reflows onto two lines, but the columns declared before the primary — a rank, an index — now stay with the primary on line one, and the remaining short columns, the status label and the secondary text fold into line two indented under the name. A list of ranked results reads down its names with the numbers still attached, which is what the M0 mockup drew. (td-6c49c5)

• status.label has a stated render bound. The reserved status column never grows past 24 characters, and the plugin protocol reference now says so in its Limits table as the protocol's own bound, beside the frozen 64-character wire bound it does not replace. A plugin author can pick a label that reads rather than discovering the truncation in a pane. (td-6c49c5)

• A plugin row now expands under the scope it was found in. get carries params.filters — the applied filter set of the list that produced the row, sent exactly as that list sent it, narrowed against the collection's declaration at the same process boundary. Enter on a row hands the scope to the tab that opens, a restored row tab carries the scope it recorded, sidecar open --plugin ID --collection C ROW --filter id=value and a layout spec row carry theirs, and sidecar plugin check --get and plugin call get take --filter too. The host's get cache is keyed by the applied set, so the same row under two scopes is two questions rather than one cached answer. Without this a row found under a raised-sensitivity profile expanded under the plugin's default profile, which could be a different document or a refusal. (td-6c49c5)

• The plugin protocol is frozen as sidecar.plugin/v1. Sidecar sends that identifier and validates the answer against it strictly: there is no alias, and a plugin still answering the pre-freeze sidecar.plugin/v1-draft is a protocol failure with a named reason rather than a silent downgrade. Tolerance belongs on the plugin side — a plugin that accepts either identifier on a request and answers with whichever it was asked keeps working with a Sidecar released before the freeze and with every one after it. The canonical request and response JSON under internal/pluginhost/testdata/protocol/, the reference fixture, the reference, the authoring guide, the runnable example, and the generated CLI reference all name the frozen identifier. (td-6c49c5)

• Every agent Sidecar can recognise is now an agent it can start, and you can add your own without waiting for a release. Twelve families gained a launch command: Cline, Devin, Droid, Hermes, Kilo, Kimi, Kiro, Maki, Qoder, Qwen, plus OMP and Mastra Code, which have their first Sidecar identity here. Each one's command, auto-approve flag and resume arguments were read from the provider's own documentation or --help, and where a provider has no auto-approve flag the catalog says so instead of guessing one. The catalog itself moved from Go code to one TOML file per family, embedded in the binary, so a family is a file rather than a rebuild-shaped change.

• You can override an agent or add one of your own. Drop a .toml file into agents/ beside your config file (~/.config/sidecar/agents/ by default) and it joins the catalog at startup. A file named after a family Sidecar ships overrides only the fields it states, so command = "claude-next" is a complete file and Claude keeps everything else; a file with a new name adds a whole family, launchable and resumable, at the end of the creation picker. A malformed file is reported and skipped rather than stopping Sidecar. See docs/reference/agent-catalog.md.

• The creation pickers offer the agents you actually have. Create Workspace, Create Shell and the Sessions create now list a family when its command is on your PATH, or when you have named it in plugins.workspace.agents. Naming one still offers it whether or not it is installed. Configuration → Agents keeps listing every agent Sidecar knows, marking the ones that are not installed, so nothing is hidden from you, and the CLI still launches any family by name, installed or not. The PATH lookup happens once per process, off every render path.

• Kilo Code reports its own lifecycle to Sidecar. sidecar agent integration install kilo writes one Sidecar-owned plugin into Kilo's config directory ($XDG_CONFIG_HOME/kilo/plugin, or $KILO_CONFIG_DIR/plugin), and from then on a Kilo pane's working, blocked, unblocked, idle and session-identity transitions come from Kilo itself rather than from reading its screen. It installs at the advisory tier on real traces of kilo 7.5.9, which is the ceiling this integration can reach: a user interrupt and a provider failure reach Kilo's bus as the same event with a different name, so a cancelled turn is not distinguishable from a failed one, and nothing releases the lane on exit. Kilo loads both plugin/ and plugins/, so a copy in each would report every event twice; Sidecar owns one of them and reports anything with its asset's name in the other as needing repair. Install, inspect, repair and uninstall go through the same adapter contract as the other integrations, so --dry-run shows the exact operations and uninstall removes only what Sidecar owns. It reports lifecycle facts only: never prompts, responses, tool data, paths or credentials.

• Kimi Code CLI reports its own lifecycle to Sidecar. sidecar agent integration install kimi adds twelve hook entries to Kimi's own config.toml ($KIMI_CODE_HOME/config.toml, or ~/.kimi-code/config.toml), and from then on a Kimi pane's working, blocked and idle transitions come from Kimi itself rather than from reading its screen. It installs at the advisory tier on real traces of kimi-code 0.40.1, covering work start, tool use, blocking, unblocking, turn completion and cancellation. Blocking is genuinely first-class here: one PermissionResult event fires whether you approve or deny, so a Kimi pane cannot get stuck showing blocked the way an agent with no denial event can. Two things are deliberately not claimed — process exit, because Sidecar already owns process liveness, and session binding, which needs Kimi to become a launchable agent family first. Sidecar owns only the block between its own two marker comments: it refuses to touch a hook of yours placed inside that block, refuses to leave a stray copy of its own outside it, and an uninstall leaves the rest of your config.toml byte-identical. It reports lifecycle facts only: never prompts, responses, tool data, paths or credentials. (td-b0e19a)

• OMP (oh-my-pi) reports its own lifecycle to Sidecar. sidecar agent integration install omp drops one Sidecar-owned extension into OMP's own extensions directory (~/.omp/agent/extensions, or wherever PI_CONFIG_DIR, an OMP profile or PI_CODING_AGENT_DIR puts it), and from then on an OMP pane's working, blocked, unblocked, idle and session-identity transitions come from OMP itself rather than from reading its screen. It installs at the advisory tier on real traces of omp 18.1.8. Blocking is first-class: one tool_approval_resolved event fires whether you approve or deny, so an OMP pane cannot get stuck showing blocked, and the ask tool blocks the pane on a question of its own. A turn that ends is not published immediately -- OMP can end one run and start another at once, so idle is debounced, and a provider error OMP is about to retry is held at working for a grace period rather than shown as a block you would have to do something about. Two things are deliberately not claimed: cancellation, which OMP does distinguish but its upstream mapping does not read, and process exit, which OMP's shutdown event carries nothing to support. Sidecar refuses to install when PI_CODING_AGENT_DIR has collapsed Pi's and OMP's extension directories into one, because both agents would then load both extensions and each would be reporting the other's pane; it says so on the status as well as in the refusal. Uninstall removes only the file Sidecar wrote and leaves any neighbouring extension exactly as it found it. It reports lifecycle facts only: never prompts, responses, tool data, question text, provider error text, paths or credentials. (td-11db02)

• The Devin CLI binds its pane to the exact conversation running in it. sidecar agent integration install devin adds one session-identity hook entry to Devin's own config.json ($XDG_CONFIG_HOME/devin/config.json, or ~/.config/devin/config.json) under each of the six events Devin can carry a session id on, so a cold restart can offer to resume that exact conversation rather than guessing which one the directory belongs to. State still comes from reading the pane, in Sidecar and in Herdr alike. Nothing is claimed on trust: the entry ships untraced, at screen fallback, because no released Devin was available to fire it here, and sidecar agent integration status devin says so in its own words. Sidecar owns only its own entries: an entry of yours that merely resembles one is never adopted, overwritten or deleted, your file is backed up before it is rewritten, and an uninstall leaves the rest of it exactly as it was. It reports the conversation's identifier only: never prompts, responses, tool data or credentials. (td-73c4ff)

• Droid binds its pane to the exact conversation running in it. sidecar agent integration install droid adds one session-identity hook entry to ~/.factory/settings.json, so a cold restart can offer to resume that exact conversation. State still comes from reading the pane. If you keep a ~/.factory/hooks.json, Droid reads its hooks from there and ignores the ones in settings.json entirely, so sidecar agent integration status droid tells you the entry would never fire and names the file; Sidecar does not move your hooks between files for you. It ships untraced, at screen fallback, because no released Droid was available to fire it here. Sidecar owns only its own entry: yours is never adopted, overwritten or deleted, your file is backed up before it is rewritten, and an uninstall leaves the rest of it exactly as it was. (td-73c4ff)

• The Qoder CLI binds its pane to the exact conversation running in it. sidecar agent integration install qodercli adds one session-identity hook entry to ~/.qoder/settings.json (or $QODER_CONFIG_DIR/settings.json), so a cold restart can offer to resume that exact conversation. State still comes from reading the pane. Only the user-level file is touched: a per-project copy would follow a checkout into other people's clones. It ships untraced, at screen fallback, because no released Qoder CLI was available to fire it here. Sidecar owns only its own entry, your file is backed up before it is rewritten, and an uninstall leaves the rest of it exactly as it was. (td-73c4ff)

• Qwen Code binds its pane to the exact conversation running in it. sidecar agent integration install qwen adds one session-identity hook entry to ~/.qwen/settings.json (or $QWEN_HOME/settings.json), so a cold restart can offer to resume that exact conversation. State still comes from reading the pane. Only the user-level file is touched. It is the one of these four that is proved against a released build: qwen-code 0.23.0 fires the hook before you have even chosen a provider to authenticate with, so the binding lands the moment the session opens. Sidecar owns only its own entry, your file is backed up before it is rewritten, and an uninstall leaves the rest of it exactly as it was, including the keys Qwen itself writes there afterwards. (td-73c4ff)

• Antigravity panes bind to their own conversation. sidecar agent integration install antigravity writes one PreInvocation entry into ~/.gemini/config/hooks.json under a sidecar hook block, so a managed shell running agy records exactly which Antigravity conversation is in it and a cold restore can offer that one back. Antigravity has no session-start event, so the binding lands on the session's first model call rather than at startup. Lifecycle state still comes from screen detection, which is what the session-identity tier means. Uninstall removes only Sidecar's own entry, wherever in the file it ended up, and leaves every other named hook block untouched. (td-73c4ff)

• GitHub Copilot CLI panes bind to their own session. sidecar agent integration install copilot writes one SessionStart entry into ~/.copilot/settings.json (or $COPILOT_HOME/settings.json), so a managed shell running copilot records which session is in it. Copilot is not installed on any machine Sidecar has surveyed, so this port is built entirely from Herdr's own installer and is untraced; sidecar agent integration status copilot says so in its known gaps rather than implying more confidence than there is. (td-73c4ff)

• Cursor Agent panes bind to their own session. sidecar agent integration install cursor writes one sessionStart entry into ~/.cursor/hooks.json, so a managed shell running cursor-agent records which session is in it. The entry goes to ~/.cursor and not to CURSOR_CONFIG_DIR, because cursor-agent's hook loader reads the former and never consults the latter. A version header is written only into a hooks.json Sidecar creates, so uninstall gives a file you already had back exactly as it was. (td-73c4ff)

• grok panes bind to their own session. sidecar agent integration install grok writes one SessionStart entry into ~/.grok/hooks/sidecar.json (or under $GROK_HOME), a directory grok merges every .json from, so a managed shell running grok records which session is in it. grok also loads hooks from ~/.claude/settings.json and ~/.cursor/hooks.json, so all three Sidecar entries fire inside one grok session and exactly one of them binds: a report whose claimed agent is not the one in the pane is refused rather than recorded. Uninstall removes only Sidecar's entry, so a hook you added to that file yourself is kept. One thing to expect: grok creates its session on your first prompt rather than at startup, so a pane you open and leave alone is not bound until you send something. (td-73c4ff)

• Mastra Code reports its own lifecycle to Sidecar. sidecar agent integration install mastracode adds eleven hook entries to Mastra Code's own ~/.mastracode/hooks.json, and from then on a Mastra Code pane's working, blocked and idle transitions come from the agent itself rather than from reading its screen, along with which thread the pane is on. It installs at the advisory tier on real traces of mastracode 0.38.0, covering work start, tool use, blocking, unblocking, turn completion, cancellation and session binding. Blocking is first-class: one PermissionResult event fires whether you approve or deny, and the traced case is a denial, so a Mastra Code pane cannot get stuck showing blocked the way an agent with no denial event can. Two things are deliberately not claimed: process exit, because Mastra Code's SessionEnd carries no reason and could not tell an exit from any other ending, and sub-agent activity, which no traced turn produced. The session binding is on AgentStart rather than on the session-start event other agents use, because Mastra Code's own session-start event carries a placeholder rather than a thread id; binding it would have made every Mastra Code shell claim the same conversation. The three hooks on events where Mastra Code can refuse a turn are written so a Sidecar failure can never do that. Sidecar owns only the entries whose command is its own: your hooks in the same file are preserved in place, and an uninstall leaves the rest of hooks.json byte-identical. It reports lifecycle facts only: never prompts, responses, tool data, paths or credentials. (td-c060a5)

• Porting an agent integration from Herdr is a written procedure. .claude/skills/port-herdr-integration/SKILL.md takes an agent from "upstream moved" to a merged port in eleven steps: reading the weekly sync report, picking the port shape, keeping the provider's own knowledge verbatim while swapping the transport, the ownership rules an installer has to obey against somebody else's configuration file, every registry the port has to appear in with the test that guards each, how a capability tier is earned from traces rather than copied from Herdr's table, and the hazards a live proof run hits. docs/guides/active/adding-new-agent-clis.md points at it before Step 4's hand-written path, so a provider Herdr already covers is not built twice. (td-615d9f)

Bug Fixes

• The session-identity installer's shared test suite covers all eight agents. The suite that pins how an integration behaves against a configuration file you already own -- it never adopts an entry that merely resembles Sidecar's, never writes through a symlink, converges on exactly its own entries when repairing, and gives your file back when it uninstalls -- was discovering its subjects from a hard-coded list of four. Devin, Droid, the Qoder CLI and Qwen Code had been outside all nine of those checks since they shipped. They are in now, and the list cannot go stale again because the suite discovers agents the same way the shipped code does. (td-615d9f)

• The Herdr sync review cannot report a ported agent as unported. The weekly review's integration table reads which agents Sidecar has ported from the port records themselves, and nothing had been checking that the two line up. They line up by Herdr's agent id, which is not always its directory name, so a mismatch would have silently listed a working integration as one nobody has built. (td-615d9f)

• The Integrations table's rows give way before its detail box does. The Configuration detail pane truncates at its bottom edge, so a page taller than the pane lost whatever was last -- which on this route was the detail box the cursor drives, the outcome of the last install, and the closing note. The rows now window instead: the column header above them and everything below them stays pinned, the rows scroll to keep the cursor's own row on screen, and a row the window hid takes its action pills' click targets with it. On a pane too short for any window to make the whole page fit -- fifteen agents on a 60x24 terminal -- the rows still give way down to three, and the rest of the page truncates as it did before, so the cursor's own row is on screen at every size. (td-20e857, td-73c4ff)

• A truncated path in Configuration keeps its filename. clampEnd passed the target width to ansi.TruncateLeft, whose count is how many columns to remove rather than how many to keep, so a 43-column path in the Projects page's path column came back as ten columns rather than the thirty-four it had room for. A column exactly one wide came back empty for the same reason, because the ellipsis was TruncateLeft's own prefix and it writes that only when the string is longer than the count. (td-20e857)

• Saving no longer drops a plugin section Sidecar does not manage. A key under plugins that this build does not know — one written by a newer Sidecar, or by hand — used to be discarded the next time anything saved the configuration. It is now merged, the way an unknown top-level key already was. The first save after upgrading sorts the subkeys under plugins once, the way the top level of the file has always been sorted, so expect one cosmetic diff there and no lost settings. An external plugin id that one of Sidecar's own surfaces already answers to (tasks, notes, td-monitor, git-status, file-browser, conversations, workspace-manager, sessions, activity) is refused by sidecar plugin add and by configuration validation, naming the surface, instead of painting two tabs with one identity. (td-944274)

• An integration for an agent Sidecar can recognise but not start can now bind the conversation in its pane. sidecar agent report-session --kind KIND resolved the kind through the launchable agent families only, so a hook for a detection-only family was refused as an agent kind Sidecar does not know, even when Sidecar itself had installed the integration sending it. The lookup now also consults the families Sidecar recognises in a pane, which is the right question for a verb that reports about a pane rather than about a launch.

• A relocated Claude Code is found by the integration installer. sidecar agent integration status|install|uninstall claude now resolves Claude's configuration home the way Claude itself does, from CLAUDE_CONFIG_DIR when that names an absolute directory and ~/.claude otherwise. Before this, a user who moved that directory saw not-installed for a Claude full of hooks, an install that wrote its entry where Claude never reads, and an uninstall that could not find its own entry. A relative or whitespace-only value keeps the default, because Claude refuses to run at all when the resolved home is not absolute. (td-73c4ff)

• A worktree created non-interactively can now be deleted non-interactively through the same lifecycle as the TUI. sidecar worktree delete TARGET --plan --json reports the exact checkout, dirtiness, remote availability, branch-cleanup choices, and pinned branch and HEAD without changing anything; using the returned absolute path and re-running with --expect-branch BRANCH --expect-head-oid OID --yes closes its Sidecar worktree session and rooted managed shells before removing the directory. Local and remote branch cleanup remain explicit flags, as the confirmation's unchecked boxes are, and a failed create's exact pending-creation journal is cleared only after deletion succeeds. A rooted shell that refuses teardown is reported as a warning after the checkout is removed, while requested branch and journal cleanup still finish. The shared refusal rules still protect main, bare, detached, locked, missing, and prunable worktrees. (td-85b0c4)

v1.14.0

Compare

Choose a tag to compare

Features

• Pi reports its own lifecycle to Sidecar. sidecar agent integration install pi writes one Sidecar-owned extension into Pi's user-level extension directory ($PI_CODING_AGENT_DIR/extensions, or ~/.pi/agent/extensions), and from then on a Pi pane's working, idle and session-identity transitions come from Pi itself rather than from reading its screen. It installs at the advisory tier on real traces of pi 0.84.3, which is the ceiling Pi can reach: it ships no permission system, so a blocked lane does not exist to be reported. Turn completion is taken from agent_settled and never from agent_end, because Pi can follow agent_end with an automatic retry or a compaction; tool use and process exit are deliberately not claimed. Install, inspect, repair and uninstall go through the same adapter contract as the other integrations, so --dry-run shows the exact ops and uninstall removes only the file Sidecar owns. It reports lifecycle facts only: never prompts, responses, tool data, paths or credentials.

• An agent installed as a plain #!/usr/bin/env node shim now gets a state badge. Detection used to match the pane's argv[0] basename only, so an npm-installed CLI left the interpreter in argv[0], tmux reported node, and neither identity input named the agent — the pane was never claimed at all. Sidecar now scores the whole foreground process group the way Herdr does: it knows the generic runtimes (sh bash zsh fish tmux node bun cmd powershell pwsh, plus python[3[.N]]), unwraps one using its own argv, prefers the process group leader, and ranks a non-runtime match above a runtime one. A pane running node /usr/local/bin/qwen is Qwen. Node package layouts upstream recognises by path are recognised too, so a Pi or Qwen CLI launched by its dist/cli.js is named without guessing from screen text.

• sidecar agent start --kind pi no longer times out. Pi rewrites its own process title, so tmux reports the pane as node while the process is really named pi; Pi's process check accepted only the literal pi and refused its own correctly identified pane before a single detection rule ran. A resolved process identity now settles which provider a pane is, and it settles it in both directions — the same check stops one agent's detection rules being evaluated against another agent's screen, which a bare node allowance previously permitted. Pi deliberately gains no bare-node allowance of its own: its published rules are a single literal "Working…", which on any Node pane would be a wrong answer rather than a missing one.

• SIDECAR_AGENT names the agent in a pane where the process cannot be seen. Export it on a wrapper command — a container, a sandbox, anything that hides the real process — and Sidecar uses the named provider's detection rules for that pane. It is a hint and nothing more: real process evidence always wins over it, and it can never grant or revoke an agent's lifecycle authority, so setting it in someone else's pane cannot switch off their session binding. One bound on macOS: a wrapper that is a SIP-protected system binary, such as sandbox-exec or ssh, publishes no readable environment to anyone, so it cannot be hinted through; a wrapper you installed yourself can.

v1.13.0

Compare

Choose a tag to compare

Features

• The Git tab reads a remote-bound project's repository. Bound to [host] Project from @, Git shows that machine's changed files with their staged, unstaged and untracked state, its branch and upstream, its ahead/behind counts, its repository state (merging, rebasing, detached), its commit list and graph, its commit details, and its stash and branch lists. Patches come from the host and render through this machine's own diff parser and viewer, so side-by-side, wrap, the minimap and the full-screen diff are unchanged. Author and path filters run on the host, over its whole log; a subject search runs here over the rows already loaded, the same split a local project makes. Every write refuses by name and changes nothing on either machine: stage, unstage, commit, amend, discard, push, pull, fetch, branch switch, stash, init and open-in-editor all name the host, and the footer offers only what the surface can do. Open in GitHub, yank commit and yank id work, because the remote URL is the host's fact and the browser and clipboard are this machine's. There is no watcher across the boundary: status refreshes on r and on the host's own snapshot signal. A bound workspace the host cannot resolve as a worktree says so instead of falling through to this machine's offer to run git init. Hosts serve it with the new read-only sidecar repo status|diff|history|commit|refs, advertised as repoReadV1; a host too old for it says so and names the machine to update. Writing to a bound repository is not part of this: it is a refusal table with a row per gesture, waiting for host verbs that do not exist yet. (td-7a1393)

• The Files tab browses a remote-bound project. Selecting [host] Project from @ already bound this TUI to that host; Files now shows that machine's tree and that machine's file bytes, never a same-named checkout on this disk. Directories expand against the host, and opening the tree costs one round trip for the root plus everything you had expanded rather than one per level. ctrl+p finds by name from the host's own catalog. Writes, git blame, file info, project search, and reveal-in-file-manager have no host verb behind them and refuse naming the host rather than silently doing nothing — the footer offers only what the surface can actually do. There is no filesystem watcher across the boundary: the tree refreshes on the host's own snapshot and on r, and claims nothing more. Hosts serve it with the new read-only sidecar content tree, advertised as contentTreeV1; a host too old for it says so and names the machine to update. (td-bc57bb)

• A bound @ destination is the screen for relayed sidecar open / layout. Selecting [host] Project already bound this TUI as that host's project workspace; a host agent that runs sidecar open or sidecar layout now lands on that workspace when this instance holds the geometry lease, not only on Sessions and never on a same-named local twin. Sessions landing is unchanged when you are actually looking at that row. Off-screen still declines and never queues. (td-af932a)

• Sessions can hide a remote's rows, and says so on the control that brings them back. The View flyout grows a ⇅ show remotes toggle with a checkbox per registered machine, so a busy host can be set aside without disconnecting it or editing config — the connection stays up and its notifications still arrive. A hidden machine leaves both projections at once, health row included, and the sort pill carries a struck host glyph (with a count once more than one machine is hidden) so missing rows are never a mystery. The choice persists, and it is dropped for a machine that is later de-registered. Hiding is not deleting: the machine's rows stay in the catalog, so pins, live terminal splits and the remembered selection all survive being hidden and come back with it — while its rows, cards, create targets and relayed pane requests are all off-screen for as long as it is. The flyout's Filter: none line is gone from both the global and project surfaces; the filter is reported only when a query is actually doing something.

• Every agent's state detection now runs Herdr's published detection manifests instead of Sidecar's hand-written rules. All ten providers Sidecar identifies — Claude Code, Codex, OpenCode, Cursor, Grok, Pi, Copilot, Amp, Antigravity and Muse — are classified by the vendored manifests, so an upstream rule fix arrives without anyone translating a regex. Claude's half-circle busy spinner (2.1.228 and newer) is recognised, so a working pane no longer has to be inferred from the absence of an idle prompt; MCP elicitation dialogs, the /btw overlay, "Waiting for N background agents" and "N MCP tasks still running" read as work in progress; a Muse pane sitting on an unanswered "Do you trust this workspace?" prompt reads as blocked instead of as a finished turn; a Copilot pane waiting for background agents reads as working; Cursor's approval prompts are recognised by the control lines every one of them renders rather than by a regex per prompt shape, so a prompt Cursor adds next release is already covered; and Codex's first-run "Do you trust the contents of this directory?" prompt, a Claude "Allow Claude to use …?" permission prompt, and a Codex approval prompt whose option line carries the composer glyph all read as blocked rather than idle. The things Sidecar knows that upstream does not are kept as data overlays with a fixture each — Claude's model picker still holds the prior state instead of reading as a finished turn, a Codex turn parked on a background terminal or in the middle of a tool call still reads as working, and an Antigravity pane on an unanswered "requesting permission for:" prompt reads as blocked — and the pane's status is still gated by Sidecar's stricter process check before any rule is evaluated.

• From a Sidecar-managed pane on a host you are viewing, sidecar open and sidecar layout land on this machine. The geometry lease names the screen: if you are looking at that Sessions row from here, the pane opens here; if you walked over to the host's own Sidecar, the open stays there. Relayed open never queues — a row that is not on screen, or a lease holder that is disconnected or too old, exits 4 with the reason rather than applying later against whatever is selected. There is still no sidecar open --host; an agent on the host runs the same command it runs locally. (td-3d2e0d, td-4971ac, td-716ba6, td-15344e, td-4c955f)

• n on a remote Sessions row lists that host's files, diffs, issues, and notes, and a Terminal split creates the tmux session on the host. Pickers stay empty until the host catalog arrives rather than filling from a same-named local twin. Resource rows come from the host's content describe matchers, not this machine's provider snapshot. layout apply of a new kind: shell pane uses the same host tmux path. (td-3fe778)

• A click in a remote Sessions pane opens that host's file, issue, note, diff, or resource, not a same-named local twin. Selecting a registered host's row and clicking a reference resolves and loads on the machine that owns the workspace, then renders here in the same Document, Issue, Note, Diff, and Resource panes local workspaces use. Nested links stay on that host; a failed remote read never falls back to this filesystem; HTTP(S) still opens in the local browser. The host must advertise ContentReadV1 — an older Sidecar still streams its terminals, and the click names the machine to update. There is no sidecar open --host; sidecar content resolve|read|describe is the internal transport over the SSH connection already held. Inline edit, file finder, and project search stay unavailable on a remote source, because those would walk this machine. (td-89c1cb, td-87358d, td-925cf9)

Bug Fixes

• A host whose login shell prints one line to stdout is no longer stuck at "not-protocol". The serve stream refused the first non-JSON line, so a motd, a version nag, or a wrapper's log line meant no hello, no snapshot, no Sessions rows and no @ destinations for that machine — with an error naming the exact cause it would not handle. Output before the first protocol message is now skipped, bounded, including JSON that is not a protocol message so a profile logging {"level":"info"} cannot be mistaken for the stream starting. Nothing is skipped after the stream has proven itself, and a stream that is simply not this protocol still fails, quoting what the host actually wrote. A version this viewer refuses still reports as a version mismatch. (td-055768)

• A Claude pane waiting on background subagents no longer announces that the turn is done. Claude Code 2.1.257 reports that state in two places and Sidecar was reading neither: the Waiting for N background agents to finish row is no longer the last line above the prompt box once an Update installed · Restart to update banner sits between them, and the footer that used to say · N shells · now says · ← N agents ·. With both signals missed, the prompt box alone read as a finished turn. Both are read now, and a waiting row left in the scrollback by an earlier turn does not hold the pane on the working lane.

• A pane's detection window no longer drops its topmost visible row. Detection reads the last N rows of a capture where N is the pane's height, and the newline that terminates a capture was being counted as a row — so on a real tmux capture, which pads the visible region to the full pane height and then terminates with a newline, the window started one row too low. Rules anchored on the first row of the screen, such as Codex's first-run trust prompt, could not match.

• The agent verbs resolve a sibling worktree from a managed shell or worktree session without flags, and refusals name the fix. An explicit target is still searched across every registered project, but when the same name exists in several, the caller's own project breaks the tie — the one SIDECAR_SHELL belongs to, or the one owning the worktree session tmux reports; outside a Sidecar session the ambiguity lists the projects and names --project / --shell. --project now also accepts what create worktree --json hands back — the worktree's path or basename resolves to the project that created it — and the create results carry project, the slug every verb accepts. A read-only lookup with --project no longer refuses because several Sidecar instances are showing that project; that check belongs to open, which has to land on one of them. (td-c906c1)

• sidecar agent list reports each live pane once, under the project that owns it. Every registered project that could see a worktree's checkout used to emit it — a worktree opened as its own project, a subdirectory of the repository registered as a project, a state directory with no checkout path at all — so one pane appeared under six project keys, twice with no name, and an explicit worktree target was "ambiguous across 3 Sidecar sessions". Each worktree root now has one owner: the project that created it, then the project whose checkout it is, then a project that merely discovered it through Git; a project with no checkout path owns no worktree rather than claiming the working directory. (td-ebd72c)

• create worktree and create shell start a catalog family with provider arguments, and create worktree --agent with --run records the family. Arguments after -- follow the family's launch command, as agent start -- ARGS takes them: sidecar create worktree orchestrate --agent claude -- --model fable; the name comes before --, and a configured launch override that contains shell syntax refuses them rather than handing them to the wrong process. --agent with --run on a worktree is now the layering create shell had — the family is recorded, the caller's command owns the launch — instead of a refusal that left --run "claude --model fable" with no agentType on record. Usage refusals under --json are {"error":{"code":"usage",...}} on stderr rather than a prose line and the full help text. (td-a658ed)

• sidecar agent read without --source now reads the visible screen, matching its documented default. Omitting the flag previously failed with source "" is not a terminal capture. (td-152978)

• Sessions no longer lists a remote project's main checkout just because Sidecar is running there. sidecar host serve cannot exclude the host's own TUI pane the way a local collector excludes TMUX_PANE, so that pane's cwd used to mark the main worktree LIVE. The TUI is chrome, not a session, and a remote main checkout with no agent is hidden the same way the project sidebar already hides it locally. Linked worktrees, managed shells, and an agent actually running on main still appear.

Changed

• The manifest_detection flag is gone. It ran Herdr's rules in shadow beside Sidecar's own and logged the differences; with every provider now classified by the manifests there is no second lane to compare against, so the flag, its entry on the flags page, and the shadow log it wrote have all been removed.

• Tmux 3.4 is now Sidecar's explicit compatibility floor, with 3.7c continuously tested. One checksum-pinned manifest drives local source builds and an oldest/latest CI matrix, including real private-server coverage for control mode, terminal rendering, paste, metadata and shell lifecycle. A separate latest-client/minimum-server proof models a Homebrew upgrade without touching the live default server and verifies capture fallback when tmux explicitly declines cross-version control mode. Future stable upgrades are one manifest change plus the same repeatable proof. (td-22399a)

Dependencies

• Tasks moves to v1.17.0, which gives a project its own open/closed lifecycle: project drop and project reopen join project complete, a closed project is stamped on the section itself, and the Tasks tab hides closed projects until C reveals them.

v1.12.0

Compare

Choose a tag to compare

v1.11.2

Compare

Choose a tag to compare

Features

• The workspace sidebar reads as a list of cards instead of a wall of text. Two-line workspace entries sat flush against each other, so line 2 of one row and line 1 of the next were adjacent and the eye had nothing to anchor on; section headers were dim muted text with no glyph and no divider, which made a section boundary the hardest transition on the pane to see. Rows now carry a blank line between them and one before each heading, and headings render flush-left and uppercase with a category glyph — 📌 PINNED, ● LIVE, ○ IDLE, ◆ NEEDS ATTENTION, ● WORKING — followed by a horizontal rule that runs to the section's action button. A project-grouped heading takes that project's stable theme hue for both glyph and title, while category and time headings stay neutral. The selected row keeps a full-width fill on both surfaces and changes only its text hierarchy when focus leaves, so a selection is never ambiguous. All of it lives in internal/workspacelist, so the project Workspaces sidebar and the global Sessions browser inherit the same presentation, including the scroll, wheel and scrollbar math that had to learn about the new row heights. (td-fd674e)

• sidecar --version now reports the commit, build date, and build profile. A released binary previously printed only sidecar version v1.9.0, which is the one build that cannot be traced back to source from the outside, so a bug report from a Homebrew install gave no way to tell which commit it came from. Release builds now carry ShortCommit and the build date from the release pipeline, make build and make install stamp the commit and dirty state from the working tree, and anything built without ldflags falls back to debug.ReadBuildInfo. The first line of the output is unchanged and stays a single sidecar version <v> line, because scripts/dev-install.sh matches it by prefix and scripts/verify-release-archives.sh compares it exactly; the new detail sits on indented lines below it. Unmanaged make install builds deliberately still do not stamp a release version, so the update checker keeps offering updates on locally built binaries. Based on the work of @justin13888 in #228. (#227)

Bug Fixes

• A file opened beside Files keeps the shortcuts it has in Files. A document pane composed next to a plugin answered a thin subset of the document keys: E external editor, ctrl+p Find, f project Search, I Info, y contents, Y path, selection copy and select-all, and + / - resize all did nothing, and esc hid the pane instead of clearing a selection. The pane now uses the shared workspace-doc context and answers every file-facing key the primary preview does wherever the shared viewer owns the capability, with Find and Search built on the same internal/panesearch surfaces the project and global Workspace document panes use, rooted at that deck's project and loading their result back into the focused pane. Because the finder, ripgrep and git-info messages are broadcast types Files also consumes, each is now tagged with the deck and leaf that issued it, so one pane can no longer swallow another's scan. y copies the visible selection when there is one and the file otherwise — the Files rule, now implemented once in docview rather than decided separately by each host. Files-only tree operations such as rename and full-screen blame stay with the primary surface and are deliberately not forwarded to a different file behind the focused pane.

• A file finder opened in the global Sessions preview no longer loses its results when the selection moves. The scan and search messages carry no root and no surface identity, so a result could land in whichever pane happened to be current — and moving the Sessions selection to another workspace while a scan was in flight left the originating pane with nothing. Each search command now carries its workspace ID and is routed back to that workspace's pane, live or cached, and previewDocSearchMsg joins the async set the model keeps delivering while the selection is elsewhere.

• An apostrophe in a task description no longer breaks agent launch on macOS. The generated start.sh passed the prompt through a heredoc nested inside $(...), and bash 3.2 — still what /bin/bash is on macOS — mis-tracks single-quote state while scanning for the closing paren. An odd number of apostrophes in the prompt turned the whole script into a syntax error, so fix today's bug failed to launch while don't break the user's code worked, which is why this survived so long: an even count accidentally re-balances the lexer, including in the test that was supposed to cover it. A " or a ) in the prompt was broken by the same pattern, with ) silently truncating the prompt and leaking the heredoc delimiter into the agent's argv. The prompt is now staged in a tmpfile written by a top-level heredoc and read back with a plain cat, which parses correctly on every bash. Thanks to @imsickofmaps for the diagnosis and the fix, and to @jennings, who reported the same bug and sent an equivalent fix in #225 back in March, months before this landed. (#262)

Dependencies

• Tasks moves to v1.16.0, and the Tasks tab can show finished work. C on the Outline reveals DONE and CANCELLED rows in place instead of hiding them, and the same key on the Projects tab nests closed children under their project rather than pruning them and hoisting the open ones. Hidden rows stay honest either way: section badges read 4 · 1 closed, a search whose matches are all closed says so instead of rendering blank, and reordering anchors on the nearest visible sibling so a keypress can't rewrite the file without moving anything on screen. Delegation stamps — tasks show's (since …), the TUI detail pane, the claim-conflict message — now render in the configured timezone and time format, with the year shown only when it isn't the reader's own, so an old handoff can't read as yesterday's. Storage and --json keep the exact UTC instant.

• td moves to v0.65.0, which lets a hosted session approve again. Hosted td-sync handlers have no on-disk BaseDir, so review-policy resolution skipped the resolver and fell back to strict mode: an implementation-involved browser session was offered only reject in available_transitions even though td's documented default is trusted and an attributed approval is valid there. Policy resolution is now centralized across review, approve, close, and transition discovery, and honors process-wide environment overrides in hosted contexts. The release also fixes td's own deploy pipeline — a failed remote build used to be masked into a green health check against the container it had failed to replace — and adopts Sidecar's blocking golangci-lint gate.

v1.10.0

Compare

Choose a tag to compare

Features

• Embedded agent terminals now keep the host terminal's background and honor synchronized redraws. Default-background cells no longer fall through to Sidecar's own canvas, which made Codex look like a dark rectangle compared with the same session in Ghostty; Sidecar asks the host for its real background and uses it only where the child selected the terminal default, while explicit Claude, Grok, and Cursor canvases still win. Canvas inference now also requires vertical reach through the live content, so a localized Codex or Cursor composer cannot become the whole-pane background merely because a one-column rewrap moved another painted row across the viewport edge. Cursor's CLI also brackets composer updates with DEC mode 2026, and Sidecar now holds intermediate emulator frames until that transaction closes instead of flashing partially cleared status and input rows on each keystroke, with a one-second fail-safe for a malformed child. On macOS, Cursor launched as agent is identified from its foreground process group's symlink-resolved argv[0] even when tmux reports the shared runtime node, using the same process-first rule as Herdr without reopening the screen-text false positives. (#313, td-3b8972)

• A shell record that was written by a newer Sidecar is no longer quietly rewritten without the parts this build could not read. shells.json has carried a version field since the beginning and nothing ever read it, so a file from a newer binary would parse into the fields this one knows, lose the rest on the next write, and look fine doing it — the same failure the shell-record durability work is about, one level up in the format itself. The version is now 2 and every writer checks it: a manifest from the future is refused with a message naming both versions, and the file is left byte-identical. A version 1 file upgrades in place on its first write, keeping every field. Reads are unaffected at any version, because a read cannot lose anything. (td-362a41)

• Forgotten shell records stop accumulating forever. Forgetting a shell moves its definition to a tombstone so sidecar shell restore can put it back, and until now nothing ever removed one — a long-lived project's shells.json grew by a record for every shell ever forgotten. Tombstones now expire after shells.tombstoneRetention in config.json, which takes a Go duration, a day count ("30d"), or "forever", and defaults to 14 days. Expiry runs at the writer boundary, so the file is bounded without a background sweeper. One deliberate consequence: once a record's window passes, Sidecar no longer remembers the forget, so a tmux session of that name that is still running becomes an ordinary adoptable row again rather than staying invisible. (td-362a41)

Dependencies

• Tasks moves to v1.15.0, and the Tasks tab gains its new triage surface. N marks the selected open task as a GTD next action in one keypress from the list or detail view, and it refuses politely on proposed and done tasks rather than mutating from an input context. An empty Next tab now explains itself — how many dated items are waiting on Agenda, counted by the same query the Agenda tab paints, and how to mark one — instead of rendering a blank pane beside a full Agenda. The Inbox tab buckets approvals and accepted rows under project headings so a triage pass stays inside one theme, with headings as unselectable chrome the a/r walk steps past. tasks move files a PROPOSED task into a project without the reject-and-re-propose dance that used to mint a new id.

v1.9.0

Compare

Choose a tag to compare

Features

• Quit on Sessions, and the panes come back. The global Sessions browser already restored the tab, but the selected row and anything composed beside it died with the process. Those now live on global state.json: the last row, each composed pane tree, and which leaf had focus. A terminal split reattaches to its still-running tmux session with scrollback intact; a row you only previewed writes nothing. A missing document, issue, unknown kind, or dead split drops that leaf and collapses its split rather than failing the restore. (td-e5a987)

• sidecar layout get and apply answer for Sessions. --sessions [ROW] targets the global surface — the selected row by default, or a durable inventory ID / display name with the same ambiguity rules as --shell. Off-screen is exit 4. Get and apply share the project workspace's report shape and all-or-nothing verdict path, so a tree an agent cannot read or compose is no longer a Sessions-only hole. (td-b6178f)

• The Tasks tab keeps up with work done anywhere else. A Sidecar left open all day only ever reread the local task database, so a task created in the hosted browser, or by a teammate, or on another machine, stayed invisible until some unrelated td command happened to pull it in. td v0.64.0 moves that responsibility into the monitor itself: it subscribes to the server's event stream and applies changes within about a second, falling back to cheap status probes and then to timed sync where a stream cannot be held. Work done in the tab — creating, starting, approving, closing, logging — now pushes as soon as it commits instead of waiting for something else to flush it. Sidecar wires none of this; it comes with the dependency.

• The create modal is steerable with the arrow keys alone. Choosing a pane kind used to mean Shift+Tab up to the list, arrowing to the row, then Tab back down to the Name field — three gestures before the one that mattered. Up and down now reach the kind list from wherever focus sits, so n, a couple of arrows and Enter is the whole interaction, and the fields that give the arrows a meaning of their own — the Project, Base Branch and Agent combos — still keep them for their dropdowns. The hint line says so.

• The global Sessions browser offers its configured resource providers. Its preview has placed Resource panes all along — sidecar open <locator> opened one there, and the surface resolves the target through the same core the project workspace does — but the create modal never listed the provider rows. They shared a flag with Terminal split, which this surface genuinely cannot offer (one terminal producer, bound to the selected row), so a passive row was gated on a live-terminal capability it does not need. The flag now means only what its name says, and the two surfaces' catalogs differ by exactly the Terminal split row.

• The kind list reads as one block. Its rows were chrome-sized to their own text, so the fill ended wherever that row's description happened to, and the list showed a ragged right edge whose shape was an accident of the longest line. Every row now spans the modal's whole content column, and a disabled row keeps the list's fill under its muted text rather than punching a hole in it.

v1.8.0

Compare

Choose a tag to compare

Features

• Agents compose pane layouts in one call: sidecar layout get and sidecar layout apply. Opening a working set of panes used to mean a sequence of sidecar open calls, each placed by a policy the agent could not see and could not address, with no way to read back what was on screen first. layout get --json now answers with the current layout — a columns-of-rows grid projection, every pane's kind, targets, tabs and tmux session, the geometry, and the caps and floors an apply will be held to. layout apply composes onto it, either additively (repeatable --pane descriptors) or as a full layout (--spec, or - for stdin) that replaces the screen. Apply is all-or-nothing: the host resolves every descriptor, builds the whole trial tree, fit-tests it against the pane floors, and either commits atomically or declines with the reason naming the first violation and leaves the layout byte-identical. The ack's items array carries a verdict per requested pane — opened, retargeted, carried, or declined with its own reason — so one round trip shows everything wrong with a refused spec rather than one error at a time. A spec must account for every live terminal by name and is declined if it omits one: apply never destroys a live session implicitly. Unlike open, layout requests never queue — a queued atomic apply would validate against a tree that no longer exists, and a stale get answer is worse than a refusal. (td-e9a089, td-89033c)
• sidecar open <target> --at <col>[.<row>] places a pane at an explicit grid cell. --split expresses a preference and silently no-ops when the open retargets an existing pane; --at expresses a requirement, so a cell that cannot be honored exactly declines rather than landing the pane somewhere else. The two are mutually exclusive. Cells are 1-based col.row against the same columns-of-rows vocabulary layout get prints, and the same requirement semantics apply on all three surfaces that host panes. (td-89033c)
• The create modal is now a pane switcher. Pressing n used to offer Shell, Worktree and Terminal split; opening a file, a diff, a td issue, a note or a configured resource provider beside your work had no keyboard path at all. The modal now lists every pane kind — growing from a horizontal toggle into the vertical list with aligned descriptions once the row count earns it — and continues to a target picker for the kinds that need one: fuzzy path match for files, recent commits and refs for diffs, in-progress and recent issues from td, recent notes, and a locator field for each configured provider instance. Every pane kind shows the placement row, so one click both chooses where the pane goes and creates it. Disabled rows stay visible with the reason inline instead of vanishing. The pickers resolve to exactly the target shape the CLI produces, so the modal is an entry point rather than a second implementation, and the rows work identically from the project workspace and the global Sessions browser. (td-2962e3)
• The pane switcher opens from whatever pane you are reading. Every content pane absorbs the keys it does not own — that is what stops a stray key firing a workspace action behind it — so the switcher used to be reachable only from the sidebar or the terminal, and putting a second pane beside the one you were reading meant leaving it first. n now opens it from a focused Document, Issue, Note, Diff or Resource pane, on both the project workspace and the global Sessions browser. It is the same key the sidebar and the terminal preview already answer with "make me a new thing", so the answer no longer changes with focus. Two consequences, both deliberate: the Diff pane's n / N next-change pair moved to > / < — the shifted forms of its , / . file steps, so the pair reads as one hierarchy — and a live input surface inside a pane still wins, so a committed in-file search keeps n for its next-match while it is up. The terminal preview keeps o, because n there belongs to the list's create. Extending the same entry to Notes, Files and Git under ctrl+n is planned separately (docs/plans/active/pane-switcher-everywhere.md). (td-18e1c1)
• The fourth pane forms a 2×2. Auto placement used to stack a third row in the right column once two content panes were open, which is where the floors start refusing on ordinary terminals. It now fills the emptiest column instead — so the fourth pane opens beside the primary terminal — then opens a new column when every column is full, and refuses at the caps (4 columns, 4 panes per column) with a message naming the rule. LiveLeafCap is unchanged at two live terminals. (td-afa959)

Developer

• A release is now changelog + one command. BUMP=major|minor|patch make release derives the next version from the latest tag, stamps ## [Unreleased] to ## [vX.Y.Z] - <today>, commits release: prepare vX.Y.Z, pushes main, and publishes — the version is stated exactly once, or zero times when BUMP implies it. Previously the operator had to hand-edit the changelog heading to a specific version and then repeat that same version on the command line via RELEASE_VERSION, and nothing caught the two disagreeing. scripts/release.sh now refuses an empty [Unreleased] section, a tree dirty beyond CHANGELOG.md, a tag that already exists, and a RELEASE_VERSION that contradicts an already-stamped heading, naming both versions in that last case. make release-dry-run prints the derived plan and exits before any mutation. RELEASE_VERSION=vX.Y.Z make release still works unchanged as the explicit-version path. Ported from tasks, which already carried this flow. (td-0dda74)

v1.7.0

Compare

Choose a tag to compare

Features

• Shell records survive their tmux server. A tmux server that died or restarted used to empty a project's shells.json, taking every shell's display name, working directory, agent type and skip-perms flag with it — and those records are the only thing that can rebuild a shell, so deleting them deleted the recovery path. On 2026-08-22 that emptied five projects at once. Sidecar now models the tmux server as an identity of its own (socket inode+ctime and the server #{pid}), because liveness is a joint property of a shell and the server it was observed on: when the server is replaced, every signal changes at once for a reason that has nothing to do with any one shell. "No server running" is read as a fact about the server rather than a listing of zero sessions, startup reconciliation is additive-only, and a shell that is not running degrades to an offline row you can press Enter on to recreate. No code path can now write a manifest with fewer entries than it read except the two single-identity removals, and that is enforced by a test at the writer boundary rather than by convention.
• sidecar shell list, forget, and restore. Forgetting a shell record was previously reachable only by pressing a key in the TUI, and Sidecar owns these records outright — nothing underneath it can reconstruct a display name or agent type — so the capability is owed a non-interactive path. forget moves a record to a tombstone rather than dropping it, restore puts it back with its display name, agent type, skip-perms and working directory intact, and list shows live and forgotten records on both the human and --json surfaces. The tmux session itself is never started or killed; this is the record, which is the part Sidecar owns.
• A visible terminal no longer costs most of a CPU core. Leaving an agent actively rendering in a visible Sidecar terminal profiled at 53% CPU against a 12.7% hidden baseline — 40 points of overhead for having the pane on screen. Filesystem and Git resolution are out of View(), project Workspace and global Sessions share one bounded content-link resolution and row analysis path, ordinary frames no longer build diagnostic cell grids, presentations with no consumer-visible change are suppressed, and global terminal updates no longer rebuild the workspace list. Where that still missed the budget, per-feed publication became adaptive: every byte is still consumed immediately, with an immediate leading frame, at most 30 sustained frames per second, and a guaranteed trailing frame. The isolated fixture measures 8.7% visible against 0.4% hidden with output-to-frame p95 of 34 ms. Scrollback, selection, links, cursor and mouse modes, resize and input latency are unchanged.

Bug Fixes

• A terminal whose control client dies is told why. When a tmux control client closed, the notice that a pane's live model had died could be dropped: the close tore down the subscriber state that the notice needed, and whichever of the two paths got there second found nothing to deliver to and returned silently. The consumer was told to fall back to capture — that report goes out on a different path — but never told its model was gone, so it had nothing to re-subscribe from and a pane could sit on capture fallback indefinitely. The closing path now reports any death the ordered actor has not already claimed, with the claim taken under the client mutex in both places so exactly one of them reports each one.
• The td tab survives a td sync. td sync installs snapshots by atomically replacing .todos/issues.db, and the embedded monitor's SQLite connection kept pointing at the unlinked inode, where every later write failed with SQLITE_READONLY — correct file permissions, unwritable database. Sidecar now notices when issues.db names a different file, closes the stale handle, reopens against the current one, and replays the keypress that triggered the check. Thanks to @gvorwaller (#308).
• Restored resource tabs load themselves again. With a provider configured and tickets open in panes, every tab came back after a relaunch saying "Waiting for <provider> to be ready" for a provider that already was, and each one had to be refreshed by hand. Restore now asks for the tab that is on screen — one call, not one per remembered tab — and a request made before any provider is wired up leaves the tab armed instead of failing it, so provider readiness resolves it without the user touching anything. A project or worktree switch republishes providers to the rebuilt surfaces too, which had been silently dropping both the matchers and the resolver.
• Website: the navbar theme switcher's dropdown and caret render correctly, the homepage gained a terminal compatibility section, and the advertised release version and commit count are derived at build time instead of being edited by hand.

Dependencies

• github.com/marcus/tasks v1.13.0 -> v1.14.0 (Sidecar-style modals in the Tasks TUI: boxed fields, real buttons, fixed footer, draggable scrollbars).
• github.com/marcus/td stays at v0.63.0.

v1.6.0

Compare

Choose a tag to compare

Features

• The Files readable view recognizes content links. Rendered Markdown (m / Render) was the one Sidecar reading surface where a td-* id, a path/file.go:42 reference, a commit hash, a URL, a sidecar:// intent, or a provider key went dead — toggling Render removed the links you were about to click, while the byte-identical Workspace document pane kept them live. It now scans what was drawn, the same way Notes and the document viewer already do.
• A file opened beside Files is live too. Document panes in the app content deck scan their bodies through the same seam Workspace uses, so a token inside one activates and stacks a tab in the deck it was drawn in. Issue, note, resource, and diff bodies stay unscanned, matching every other surface.
• Provider keys inside Markdown links open their card. [ZMS-37161](https://<site>.atlassian.net/browse/ZMS-37161) — how a ticket normally appears in a brief — could never reach a provider: the key is only in the label, and an issue-key matcher can never match a whole browse URL. With the destination's host listed in that instance's claimHosts, the label now opens the Resource card and keeps its browser hyperlink, so cmd-click still reaches the ticket. Only frames Sidecar's own Markdown renderer drew are eligible; a program writing to a terminal still means what its destination says. claimHosts is now documented in the provider protocol reference.
• ./scripts/demo.sh ships a sample document exercising every content-link kind that works without an external provider.

Bug Fixes

• Files preview geometry followed the source line count while reading rendered rows. Harmless while rendered Markdown opted out of scanning; the drawn rows and the exported geometry now read one accessor, and a truncated file no longer exports one row more than it draws.

v1.5.0

Compare

Choose a tag to compare

Features

• Scrollbars you can grab, everywhere they appear. A shared interactive scrollbar core with one geometry and inverse mapping now backs the palette, notification centre, file browser (tree, search, and preview), git, conversations, notes, the doc and issue viewers, kanban lanes, the sessions sidebar, the project workspace sidebar, the theme picker, modal viewports, and the project switcher. Bars drag from anywhere on the track, hosted views receive the gesture through the content deck, and a sub-modal opening cancels the parent's in-flight drag.
• Terminal panes scroll interactively too, with the scrollbar wired through both workspace projections rather than reimplemented per surface.
• Cross-project td issue links resolve on a local miss. An issue ID that does not exist in the current project is looked up across the other configured projects instead of dead-ending.
• Carried terminal backgrounds are span-capped. bounded renders short runs — diff hunks, highlighted notices — and drops the background of any run longer than the cap, so an application that paints most of its output one colour degrades to plain text instead of repainting the pane. never suppresses carried backgrounds entirely; auto keeps the previous canvas-detection behaviour. Configurable per surface as plugins.workspace.terminalBackgrounds and terminalBackgroundSpanMax.
• 24-bit colour is advertised to tmux. A fresh tmux server carries no direct-colour capability, so tmux quantized truecolour output to the 256 cube inside sidecar panes. Sidecar now appends one terminal-overrides entry, idempotently. The claim names sidecar's own TERM rather than every terminal type, and is only made when COLORTERM says the terminal renders direct colour — terminal-overrides is a server option that outlives sidecar and applies to every session on the server, so a blanket claim would corrupt colour in terminals sidecar never opened. Failure is never fatal: a colour hint cannot block opening a shell.
• A Feature Flags page listing the whole registry. Configuration → System → Feature Flags shows every flag Sidecar knows about with its real state. Previously only four hand-picked flags had a control, so tmux_interactive_input, tmux_inline_edit, files_auto_refresh, plugin_content_panes, and terminal_resource_providers were settable only by hand-editing config.json. Flags that Panels & Integrations already owns are shown read-only with a jump to the control that owns them, so the flag and the plugin's own enabled key cannot drift apart.
• The split workspace terminal ships on by default.

Bug Fixes

• Relaunching returns to the global tab you left on. Quitting from Sessions, Activity, or Tasks reopened the project workspace: the last global tab was remembered but the space itself was not, so the remembered tab only applied the next time you pressed K. A remembered space whose tabs are no longer available falls back rather than showing an empty surface.
• Sidecar never resizes the tmux pane hosting itself. Scrolling the global Sessions list to its bottom could shrink Sidecar's own screen (td-9cddeb).
• Settings toggles stop drifting right on a wide window. Panel rows right-aligned their ON/OFF pill to the pane's full width, so widening the terminal pulled every toggle away from its label. Rows now stop at a shared cap that lines the pills up with where the widest form field ends.
• Background SGRs are stripped without nesting escape sequences.
• The global Sessions list sees new projects and non-Git projects' shells.
• The files tree shows the full list from the top when it fits the viewport.
• Repeat pane opens stop lying, and create shell opens beside the session.
• The workspace sidebar's free-scroll clears on selection change only.
• g / G can be typed into the conversations session search box instead of jumping the list.

Build

• Go 1.27, matching td and tasks. encoding/json/v2 is the default implementation; sidecar's adapter parsing, config, and state round-trip unchanged.
• make lint works in a go.work checkout again. It computed GOTOOLCHAIN from a go list -m that did not set GOWORK=off, so the workspace answered for tasks and td as well and the recipe expanded to three version words.
• Test binaries no longer inherit the developer's TMUX_PANE, which could silently drop a scripted pane from an inventory assertion after a tmux server restart renumbered panes.

v1.4.0

Compare

Choose a tag to compare

Features

• First-run onboarding that names the next step. Launching in a non-git directory with no configured projects opens Configuration → Add Project instead of an empty td monitor. Initialize this directory (or the Git tab) runs git init -b main after a click or i, then reloads git context without a restart.
• In-app install for td and Tasks. The td uninstalled view and Configuration → Panels offer a confirmed Install button (Homebrew, or go install if brew is missing). Sidecar never uses sudo and does not treat a package-manager exit as success. Diagnostics for missing standalone Tasks points at Panels rather than claiming Sidecar will not install it.
• Empty states that point at the next action. TD monitor empty panes explain how to create work; embedded Sidecar adds a Workspaces hint when there are no tasks yet. Workspaces first-run copy covers n / + once inventory has loaded. An unattached worktree preview is padded and has a Start Agent button that opens the create-workspace form.

Bug Fixes

• Create Workspace kind toggle shows the selected type. Opening the form in Shell mode (or leaving focus on Name) no longer leaves both Shell and Worktree looking unselected; the current kind stays highlighted.
• Note activity in the td monitor says "created note" / "updated note" instead of treating notes as issues. (Requires a td build that includes the matching monitor change.)
• Create Workspace kind row shows when it has keyboard focus. The chosen kind stays filled; [ ] around the row uses the same Primary colour as a focused input so Tab on the toggle is visible without stealing the selection.

Workspaces and panes

• The terminal panel is a Shell leaf of the pane tree. The panel's second, parallel split system is gone; shells, files, notes, issues, and resources are all leaves of one tree with one compositor, one border rule, and one divider renderer. Shell placement is duplicable, respects a live cap, and the sidebar shows layout badges. Pane titles are clickable to rename.
• Split terminals belong to their own workspace. A split's close ends its session and its confirmation says what will actually happen; a wedged split can be closed, a reused session honours --run, and split names are scoped to the owning workspace.
• sidecar create CLI. sidecar create shell, sidecar create shell --split <dir>, and sidecar create worktree let an agent open shells, splits, and worktrees in the running app, with worktree context, journalling, and ack matching.
• Notes open as workspace content panes. Notes lists, archive, search, formatting, and content links were polished together; the archive reloads the right pane with the selected note, and clicking below a note's last line lands the caret at the end of the text.
• Per-tab close buttons with a hover state and tighter tab labels.
• Clickable links in Files panes, symbolic git ranges recognized as diff links, and claimHosts so resource providers can claim built-in URL spans while keeping their OSC-8 hyperlinks.
• Scrollbars in Files fileview panes, workspace document panes, and the switcher/palette modals, which also gained stable height and mouse support.
• opencode auto-approve support in shell creation via --auto, derived from workspaceops rather than hardcoded per launcher.
• Session copy ring — paste-recent over ssh, plus undo aliases in notes.
• Refreshed diagnostics info modal layout, plugin table, and close button.

Bug Fixes — panes, rendering, and input

• Pane geometry is announced to plugins on resize, not every frame (td-fcb03a), and wheel bursts are coalesced and paced across issue viewer surfaces and forwarded pane applications.
• Canvas detection survives the screen model's serialization, abstains on untouched default-background rows, and breaks ties on row starts (td-fb5a9d, td-b8c54e); Grok terminal backgrounds fill on large canvases.
• Issue and document panes render markdown at full pane width via the compact renderer contract, and padded viewers are paired with compact-document renderers (td-85a2be, td-65095b).
• Clicking a commit tab's own header no longer strands it loading, file panes no longer stick on Loading after a split, and plugin-switch keys stay live over a focused content pane.
• Notes preview clicks are only stolen for real content links (td-b57215), and the content pane header × hit rect covers the glyph.
• Footer drops the refresh stamp and aligns shortcut help (td-f6ad90, td-70f800).

Build and tooling

• Managed dev installs track workspace siblings (td, tasks) through go.work, and make install-status reports the sibling revisions compiled in.
• scripts/demo.sh — modular, fully ephemeral demo environments (multi-project, single-project, and fresh onboarding presets) that build a fresh binary from the working tree and clean up on exit.

Dependencies

• td v0.61.0 → v0.62.0 (monitor empty states, note activity verbs, embedded next-step, and the issue-modal CPU fixes).

v1.3.0

Compare

Choose a tag to compare

Bug Fixes

• Create Workspace modal retains keyboard focus across fields. Tabbing or clicking away from the Name field no longer snaps focus back to Name on intermediate view renders. Initial focus resolution now handles declarative modals before and after first paint without overwriting active field selection.
• Retain workspace shell focus when switching plugins.

v1.2.2

Compare

Choose a tag to compare

Bug Fixes

• Text selection is easier to find against the canvas. The highlight sat at 1.2–1.5:1 on every theme — a selected-row fill, not a span — so a drag in Notes, Files, or a document pane disappeared into the shell background. Selection now lifts to at least 2.65:1 against the canvas and stays on the same ink pole, so body text, headings, and syntax colours are not inverted or washed out. Curated tinted selections bring vibrant, theme-matched highlights while supporting chromatic contrast in normalizer calculations.

v1.2.1

Compare

Choose a tag to compare

The footer toast is gone. Notifications stack in the corner, live in a centre you can open from any surface, and take numbered jumps to the thing they name. Clicking a file, a commit, a td id, or a note link opens a pane beside the plugin you were already looking at, instead of yanking you away. Markdown follows the active Sidecar theme. Notes is no longer a beta.

Features

• One Create Workspace form on both surfaces. Project Workspaces and global Sessions share the same Shell | Worktree modal, with auto-approve and base branch on global as well as project. Instant-create shortcuts are unchanged: project ctrl+n, Shells [+], and autoCreateShell still skip the form.
• A notification system instead of a one-line footer echo. Toasts are bordered blocks in the top-right of the content region: they stack, collapse by source, reveal a row at a time, and dismiss on click or d. The centre is an app-level right panel (N / alt+n) with per-source sections, unread dots, wheel scrolling, and a header indicator next to the gear. Settled agent lane transitions post here; so does anything that used to flash the footer. A quieter status-flash tier exists for things that should not take a toast slot. Expiry, stacking, and per-source behaviour live on the existing config screen.
• sidecar notify for agents. post, list, and dismiss write the same log the UI reads. A post appears as a toast in the running instance and stays in the centre until dismissed; with no instance running it is stored and shown at the next start. --target kind:value[:line][@project] attaches numbered calls to action (issue, task, commit, file, session, url), including a jump into another checkout.
• Content links and passive panes on Files, Git, Notes, td, and Tasks. A file path, path:line, td id, commit hash, or sidecar://… link underlines only when it can be activated in the current project. Clicking it keeps the active plugin on screen and opens the same Document, Issue, Diff, or Resource pane Workspaces already uses: first pane to the right, another kind stacked in that column, the same kind as a tab. Plugin content panes are on by default. Tab walks the plugin, then the panes, in visual order; q/esc hides the focused pane and x closes a tab.
• Tab walks into the embedded td and Tasks panels. Those two surfaces now name their own focus stops, so the app's tab ring can enter the monitor's current-work / list / activity panels and Tasks' list and detail regions instead of treating the whole plugin as one opaque box.
• In-file search and inline edit in document panes, on both the project workspace and the global Sessions browser. / searches the focused file (incremental, n/N, wrap-aware highlights); the same tmux-PTY editor the Files plugin uses now edits a doc pane in place. ctrl+p / ctrl+f reach the file finder from the browser as well.
• Markdown follows the active Sidecar theme. Headings, links, inline code, rules, and fenced blocks are derived from the current palette rather than Glamour's generic dark preset. Fenced code uses the same Chroma style as file previews. Switching a theme restyles Markdown that is already on screen without discarding scroll, selection, tabs, or search.
• Notes is a stable project surface. A project that has not run td init gets a setup path rather than a dead screen. Create and delete are optimistic, mouse editing is native (multi-click, click-after-EOL, pane-local $EDITOR forwarding), and the built-in editor honors Mac/Emacs keys plus a persisted Built-in / $EDITOR preference. Layout, filter, and save chrome are tighter; informal numbered outlines render as lists; edit padding matches the markdown view.

Bug Fixes

• make install-worktree / make install-local make sidecar on PATH run the build they just activated. Homebrew is still the managed link; copies that win PATH (typically ~/go/bin from unmanaged make install) are pointed at the same artifact so make install-worktree && sidecar is one build. make install-status still reports resolution without mutating it.
• Unsafe internal link labels stay inert, and only rectangles that are actually rendered as links are decorated — so a label that looks like a path or a td id inside chrome, search, or an editor is not clickable.
• Absolute content paths survive a project switch, so a pane opened by full path does not resolve against the wrong checkout.
• Git full-file staging keeps its identity when a content pane is open beside the Git plugin, instead of staging the wrong file because the pane and the list had drifted apart.
• A path qualifier on a jump names a checkout, not a project, so cross-project notification targets and sidecar open land in the worktree they named.
• Git failure alerts are a headline, not a dump, and the last bottom-status echoes in Notes and git-status are gone — those events are notifications.

Internal

• make lint is the GitHub lint job: full codebase, GOOS=linux, GOWORK=off, golangci-lint v2.12.2. The old --new-from-merge-base gate missed unused leftovers whose function bodies were not edited.
• internal/contentlink owns link recognition and sidecar:// routing; internal/passivedeck owns the app-level content deck both plugin hosts and the workspace surfaces bind to. There is still one compositor and one pane frame.
• Document search lives in internal/docview. Inline edit for Files, Notes, and doc panes shares internal/inlineedit.
• Cross-surface jumps (notification centre, content links, sidecar open) go through one state-free activation service, with a single pending-target slot so a project switch and a landing cannot race.

Dependencies

• td v0.60.0 → v0.61.0. The embedded monitor exposes its three root panels as focus stops the host tab ring can enter.
• tasks v1.11.0 → v1.12.0. Same contract for Tasks' list and detail regions.

v1.2.0

Compare

Choose a tag to compare

Dependencies

• tasks moved to v1.11.0, two releases on from the v1.9.0 v1.1.0 shipped against. It brings three-part delegation (mode and note) through the data model, the CLI, the HTTP surface, and a delegate modal; a user-configurable delegation vocabulary; approving and completing a proposal in one step; and expanded relative date input.

Fixes

• A release can no longer ship against a stale sibling module. v1.1.0 was cut with tasks pinned two minors behind and nothing noticed, because go.work resolves td and tasks to the local checkouts — so the pins in go.mod are the one thing a local build never exercises. The release preflight now reads those requirements with GOWORK=off, compares each github.com/marcus/* module against its newest published tag, and refuses to tag when any of them is behind. make sync-deps is the fix it points at: it pins every sibling to its latest release and tidies, so the correction is one command rather than a per-module go get the operator has to remember.

v1.1.1

Compare

Choose a tag to compare

Text you can see is now text you can select and copy — on every surface, into every clipboard — and the machinery behind panes gained two shared seams so project and global workspaces stay one model rather than two lookalikes.

Features

• Text in a document pane is selectable on both surfaces. A file pane could be read but not copied from. It is one docview.Model in two places — the project workspace and the global Workspaces browser — so the selection binds to the viewer once and both surfaces inherit it, the way live refresh already does. Rows are wrapped and tab-expanded at layout time, in the column space they are actually drawn in, so the columns a selection names are the columns on screen and the selection engine never sees wrapping. The line-number gutter is kept beside the text rather than inside it, so it can never be selected or copied.
• Copies reach both clipboards, and copy-on-select is a choice. Every copy used to end in a local clipboard utility, which does not exist over SSH or inside the tmux control-mode sessions the workspace surfaces run on — so copying put the text nowhere and reported success anyway. internal/clip is now the single path text takes: the system clipboard natively, and the terminal's own over OSC 52. Copy-on-select is a setting rather than an assumption, and one control owns it.
• A sidecar-modern Chroma syntax theme, with red keywords and teal types, plus easier-to-see text selection in that theme.

Bug Fixes

• The global Diff pane accepts file clicks and host shortcuts (td-efbaa9). The Sessions Diff leaf registered file-row hits but never dispatched them, and always claimed leftover keys, so @ never reached the project switcher. Click and wheel rules moved onto the shared workspacediff.View, and host globals now pass through when a content leaf is focused.
• A shell created from the global browser stays live. Creating one wrote the session and manifest, then the next live-only poll treated it as unclaimed and painted the preview "session ended" while tmux was still running (td-ecb0b8). Unclaimed sessions now fall through to path ownership, and an in-flight status pass cannot drop a project re-inventoried mid-cycle.
• Live watches the kernel drops are re-added, and a view that can never perform a re-read is no longer owed one.

Internal

• internal/livepanes owns the live-refresh watcher lifecycle that had been written out once per pane kind per surface — six near-identical copies, and six chances for a new pane kind to silently never refresh. Adding a kind is now one Binding entry per surface.
• The selection engine lives outside the terminal package, so surfaces that are not a PTY can use it.
• make worktree-init lets any harness make a git worktree Go-buildable, and Sidecar-created worktrees run it automatically.

Dependencies

• td v0.59.0 → v0.60.0. The embedded monitor's list, board, and swimlane panes now share one row layout, so keys and columns line up and selecting a row no longer shifts it.

v1.1.0

Compare

Choose a tag to compare