parse: derive row titles from prompts, not instruction files or path drops - #15
Merged
Conversation
…drops The title took the first user message verbatim. Codex rollouts embed AGENTS.md as their first user message, so every codex row was titled '# AGENTS.md instructions for …'; claude sessions opened by a file drop titled as the dropped path. TitleFrom replaces the bare usableTitle gate at all three capture sites: messages that open like a markdown document (# headers, code fences) are rejected in favor of a later message, and leading file-drop path tokens (plus joining punctuation) are trimmed so '/tmp/notes.md - review this' titles as 'review this'. A message that is only paths titles nothing. Ordinary prompts, including ones that mention paths mid-sentence or start with a numbered list, pass through unchanged. README documents the derivation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Defect
Row titles took the first user message verbatim. Codex embeds AGENTS.md as every rollout's first user message → every codex row titled
# AGENTS.md instructions for …. Claude sessions opened by a file drop titled as the dropped path (/tmp/…-drop-….md - re…). The board's WORK column was unscannable — observed live on the devbox board and in the mac app's deck.Fix
parse.TitleFromreplaces the bareusableTitlegate at all three capture sites (claude text, codexevent_msg, codexresponse_itemparts):#headers, code fences) are rejected — the next user message (the real prompt) titles the row;/tmp/notes.md - review this→review this; a message that is only paths titles nothing;fix /code/foo/bar.go please) and numbered-list openers.Labels and summaries still take precedence, unchanged. Same
task/title_userfields — no--jsonshape change. README's "TASK" derivation paragraph updated.Evidence
TestTitleFromtable +TestTitleUserSkipsInstructionFilesAndDrops(codex instructions-then-prompt, claude drop-then-request).review the synth app and veri…/Read SPEC.md and ROADMAP.md. …; the drop-opened claude row titlesreview this and help me with ….go test ./... -race,FuzzApply20s,tools/parity.sh,bats tests/,golangci-lint0 issues, vet, darwin build.Note for a follow-up (not this PR)
While A/B-ing cached vs fresh scans, CTX%% for unchanged files differed (e.g. 16%% cached vs 80%% fresh on an 8d-idle session) — the incremental cache looks like it can hold a stale
ctx. Filed in the session report as a D-round candidate.🤖 Generated with Claude Code