dcdpr / jp / 24579266447 / 1
65%
main: 65%

DEFAULT BRANCH: main
Ran
Files 290
Run time 8s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 64.082% (+0.06%) from 64.024%
24579266447.1

push

github

web-flow 
feat(cli, workspace): Add `--scope` filter to `conversation grep` (#577)

Add a `-s`/`--scope` flag to `jp conversation grep` that restricts the
search to specific parts of a conversation. The available scopes are
`title`, `user`, `assistant`, `reasoning`, `structured`, `tool-call`,
`tool-result`, and `inquiry`. Two meta-scopes expand to their concrete
members: `chat` covers user, assistant, reasoning, and structured;
`tool` covers tool-call and tool-result. Omitting `--scope` searches
every part, preserving the existing behaviour.

Conversation titles were not previously searchable at all; they are now
a first-class scope. Tool call arguments are pretty-printed before
matching so individual keys and values land on their own lines, giving
`--context` meaningful results.

When more than one scope is passed, a right-aligned scope column appears
in the text output so hits from different parts are easy to distinguish.
A bare invocation or a single `--scope` value keeps the pre-existing
output shape unchanged. The JSON output gains a `scope` field on every
hit regardless.

For workspace-wide searches that require the event stream,
`Workspace::ensure_all_events_loaded` pre-warms every conversation in
parallel, amortising the per-file disk reads across cores. Narrow
(handle-specific) searches still lazy-load sequentially.

Signed-off-by: Jean Mertz <git@jeanmertz.com>

23340 of 36422 relevant lines covered (64.08%)

183.24 hits per line

Source Files on job 24579266447.1