Skip to content

v0.32.0

Latest

Choose a tag to compare

@github-actions github-actions released this 11 Nov 08:49
· 18 commits to main since this release
4a00113

Install: npm i -g @stroq/cli@0.32.0, or npx @stroq/cli@latest init. Every change, with the reasons, is in the changelog.

Added

  • The card reads Cursor sessions as well. Alongside Claude Code and Codex, it counts the sessions in Cursor's local SQLite store, read-only and with the same reader as stroq sent, checks them for keys, and replays them in the order their messages were written; a moment's stroq replay --transcript command takes a Cursor session too. What Cursor has not yet moved out of its write-ahead log is reported as pending, not read, and when the read stops at its limit the card says so. By @Nari-Ab (#298).
  • A moment on the card can be marked as a false alarm in one step. stroq show <n> ends with the line to run, stroq show --false-alarm <id>; the id is the moment's own, so the mark goes to what you read even if the card was made again in between, and the confirmation repeats the sentence it marked. The card stops listing that moment for as long as what it shows stays the same: one more key in that session, a longer command, another command run by the same setting of a folder, or a change to a script, an included file or the package.json behind npm run that the setting names (one step deep) is a new moment and is listed again. A moment whose evidence cannot be read in full (a variable or a glob in the command, a change of directory, more than the 64 MiB hashed for one folder) cannot be marked. The counts do not change, since they are what the rules found, and the card says how many moments it left out. stroq show --false-alarms lists the marks and --clear takes them back. Marking and clearing need a terminal (a pipe or a plain agent shell is refused), and Stroq's hook refuses them through an agent's shell as well. Neither is a wall against an agent that can get itself a terminal; the card says how many moments it left out, so a mark you did not make shows there. A marks file that cannot be read hides nothing. stroq card --json adds coverage.falseAlarms and each moment's key. Asked for on the Show HN thread.

Changed

  • When a sandbox around the agent closes Stroq's own folder, the hook says so. The call is refused as before, and the reason now names ~/.stroq and says to give it read and write access in the sandbox, instead of "the policy file is there but cannot be read (ENOENT)" for a file the sandbox hid.
  • Stroq and a sandbox says how to run Stroq inside one, such as Agent Safehouse, and what happens when ~/.stroq is left out: every shell command, edit, fetch and MCP call is refused, so give the folder read and write access. Asked on the Show HN thread.

Fixed

  • The card shows recent Cursor sessions after a long Cursor history. Its read limit of 30,000 rows and 64 MiB counted every bubble Cursor ever stored, so past that the card showed no Cursor session, only "Cursor's session store could not be read in full". The card now reads each bubble's date first, and only the sessions with a bubble in its window count against that limit. For the whole history, the limit is now the time the read takes, about 2 seconds, not a number of rows: a very large store, or a slow disk on the first run, can still show "could not be read in full". A session with a bubble the card cannot date is read in full, and when the sessions in the window alone go over 30,000 rows or 64 MiB, the card still says the store was not read in full (#311).
  • A Claude Code hook that cannot start no longer lets the call through. Claude Code takes a hook that exits with any code but 2 for a non-blocking error and runs the call, so a Stroq whose entry was gone, or closed to a sandbox around the agent, guarded nothing and said nothing. The line stroq init writes now ends in || { echo '…' >&2; exit 2; }, as the plugin's wrapper already did: such a hook blocks a PreToolUse call and says to run stroq doctor. Run stroq init again to get the new line; init, uninstall, doctor, the card and the console know both.