You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/session-info.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,9 +47,10 @@ For agents that expose a resumable CLI, lazyagent builds the exact shell command
47
47
- OpenCode: `opencode -s <id>`
48
48
- Kilo: `kilo --session=<id>`
49
49
- Cursor: `cursor-agent --resume="<id>"`
50
+
- Grok: `grok --resume '<session-id>'`
50
51
- Kimi Code: `kimi --resume <session-id>`
51
52
52
-
Grok CLI does not currently expose a direct resume command that lazyagent can invoke, so Grok sessions omit this field. In the TUI, <kbd>c</kbd> copies the command to the clipboard when one exists. The GUI has a copy button next to the command. The API exposes it as `resume_command` on the session detail response.
53
+
In the TUI, <kbd>c</kbd> copies the command to the clipboard when one exists. The GUI has a copy button next to the command. The API exposes it as `resume_command` on the session detail response.
Copy file name to clipboardExpand all lines: docs/maintenance/search.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,12 +74,11 @@ Type a 1-based result number to open that session in the originating agent when
74
74
| codex |`codex resume <session-id>`|
75
75
| amp |`amp threads continue <session-id>`|
76
76
| pi |`pi --session <session-id>`|
77
+
| grok |`grok --resume '<session-id>'`|
77
78
| kimi |`kimi --resume <session-id>`|
78
79
79
80
The command runs from the session's original CWD when that directory still exists, otherwise from the current shell directory. Pressing <kbd>Enter</kbd> on an empty line exits without opening anything.
80
81
81
-
> **Grok sessions** are indexed and searchable, but `search` cannot resume them directly — Grok exposes no resume command, so selecting a Grok result reports that and exits.
82
-
83
82
## Index management
84
83
85
84
The index updates *incrementally* on every run — there's normally no reason to think about it. Two situations call for a manual rebuild:
After printing results in an interactive terminal, `search` prompts for a result number; entering one opens that chat via the originating agent's resume command when lazyagent knows one. Grok sessions are searchable but not directly resumable, because Grok CLI does not expose a resume command. Piped output stays non-interactive.
174
+
After printing results in an interactive terminal, `search` prompts for a result number; entering one opens that chat via the originating agent's resume command when lazyagent knows one. Grok sessions resume with `grok --resume '<session-id>'`. Piped output stays non-interactive.
175
175
176
-
Full reference, including the index location, ranking, resume commands, and Grok caveat: [`search`](../maintenance/search.md).
176
+
Full reference, including the index location, ranking, and resume commands: [`search`](../maintenance/search.md).
0 commit comments