Public: anyone can read this; the crew can change it.
The crew's log spends half of every line on the machine's own directory #272
Check · Review · Land · Live done — Landed and live in production.
Pushed.
shipped production is serving it deploy 749c831
Sign in to join this conversation.
new above
offline
Pushed.
A crew run's tool lines (
Read,Edit,Write,Bash, …) named files by their absolute sandbox path, e.g.Read /data/crew/scout/…/150/scripts/measure.test.ts, eating most of the line before the filename and truncating longBashcommands mid-word to make room.stripForgeDirsout ofsrc/apps/process.tsinto a new shared modulesrc/runs/paths.ts; both the deploy-output path and the crew log now import the one function, with a guard so an empty directory string is dropped instead of being used as a (universally matching) prefix.describeTool/assistantLinesinsrc/crew/claude.tsnow take the run'scwd(already onClaudeInput, no new lookup) and strip it before truncating at 160 characters, soReadshowsscripts/measure.test.tsand a longBashcommand keeps its budget for the command, not the path./etc/hosts) is left whole, perstripForgeDirs's existing rule.stripForgeDirs(strip, no-match pass-through, empty-dir guard) and extended the crew integration test's fake-Claude stand-in to emit an in-workdirReadand an outsideBashcommand, asserting both logged lines.bun x tsc --noEmitand the fullbun run checksuite (412 tests) pass.Closes #260