Menu

Individual skill

rekall

0upvotes

Compact the current Codex VS Code extension thread through Rekall with a verified handoff and optional one-time continuation. Use on an explicit compaction request or after a substantial completed stage; standalone Codex CLI sessions are unsupported.

plugins/DitriXNew/rekall/skills/rekall/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,541
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Rekall

Rekall requires a thread owned by the Codex extension in VS Code, on Windows, macOS, or Linux. It uses that extension's IPC owner and lifecycle events. Standalone Codex CLI sessions, the Codex desktop app, and Claude Code are unsupported. Installing the plugin with the Codex CLI does not change this host requirement. Do not start a separate App Server or resume another process to work around a missing extension owner.

Use Rekall only for the current thread. Obtain `CODEX_THREAD_ID` from the environment; never guess an identifier or select a thread from history.

Before scheduling, finish and verify the current stage. Call `compaction_status` to ensure there is no unfinished job, then call `probe_compaction` to verify the owner, IPC compatibility, and thread state. Rekall has no context-use threshold for scheduling a user-requested compaction.

Create a handoff containing:

- `summary`: the task, constraints, decisions, completed work, validation, and work that remains.
- `preserve`: facts and instructions that need detailed retention.
- `discard`: repeated or obsolete conversation history that may be summarized. This never authorizes deleting files.
- `nextStep`: the exact already-authorized continuation and where it must stop.