A command for listing, searching, and restoring Grok's saved conversations, called sessions. These sessions are separate from the plugin's records of jobs it started.

Use it to browse recent sessions, search their contents, restore one, or resume it with another Grok command.

It helps you find earlier work and continue a previous conversation instead of starting again. It also distinguishes Grok's native history from plugin job tracking.

sessions — Command for Claude Code by LovelaceLoom/grok-plugin-cc

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add LovelaceLoom/grok-plugin-cc

Claude Code

/plugin install grok

Made for: Claude Code.

Or install grok, the plugin that ships this one along with the rest of its 8 skills, 21 commands, 2 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/sessions/github.svg)](https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/sessions)

Your own site

<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/sessions"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/sessions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/sessions"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/sessions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 370 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00370
Opus 5.5	$0.00007	$0.00148
Sonnet 5.5	$0.00003	$0.00074
Haiku 4.5	$0.00002	$0.00037

Measured 1mo ago against content hash 5462f40255c0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sessions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/grok/commands/sessions.md · 39 lines

What it actually says

Wrap grok sessions. The plugin tracks its OWN job ids (/grok:status, /grok:result) — those are wrappers around invocations the plugin launched. This command surfaces Grok's native sessions (~/.grok/sessions/...), which include everything Grok has run in this workspace (including outside the plugin).

Subcommands match the underlying CLI:

/grok:sessions or /grok:sessions list — list recent Grok sessions
/grok:sessions search <query> — search session contents. If the query starts with - or -- (e.g. searching for previous --timeout mentions), use the POSIX -- terminator to escape it: /grok:sessions search -- --timeout. Everything after -- is treated as a literal search term and forwarded to grok as a positional argv after a re-emitted --.
/grok:sessions restore <id> — restore a prior session for resume

Pair with --resume <id> on /grok:ask, /grok:research, /grok:rescue, etc. to continue an existing session.

Raw user input: $ARGUMENTS

Run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" sessions "$ARGUMENTS"

Output rules:

Return the companion's stdout verbatim.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 39 lines · 17 tokens per session scan A 5462f40255c0

Subscribe to this mod's changes

sessions is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 370 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Memory and context ai-assistant ai-tools claude-code-plugin developer-tools

sessions

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checkpoint

dream

recall

status

comms-import

promote