Windows Save Token Jev Setup

No. The installer only places the skill files under CODEX_HOME or the default Codex skills folder. You must restart Codex, invoke the skill, back up settings, merge hooks, and trust them separately.

Run the bundled PowerShell script, which writes only to the current-user OPENROUTER_API_KEY variable. Later steps copy it to TYPESAFE_API_KEY without writing plaintext into hooks, docs, or backups.

Open /hooks and confirm PreCompact for manual and auto with 120s timeout and SessionStart for compact with 10s timeout both show Trusted and Active. Config files alone prove nothing.

No. A passing config check is not a live test. Use a fresh session with a unique non-private marker, run /compact manually, then confirm fresh selection, native compression, restore, and cross-task isolation.

Three steps. A PreCompact hook sends the candidate session and tool records to Jev and keeps the ones worth retaining, Codex then runs its own native compression, and a SessionStart hook on compact puts the selected content back into later model requests. The Skill also inspects an older sidecar, so a failed preparation cannot silently restore the previous session's stale context.

Windows 10 or 11 with Codex desktop or the CLI, Node.js 20 or newer including npm and npx, Git, and a usable OpenRouter API key you never paste into chat, a command argument, or a repository. In PowerShell, winget install --id OpenJS.NodeJS.LTS -e --source winget and winget install --id Git.Git -e --source winget, then reopen Windows Terminal and check node, npm, npx and git versions.

Deleting the skill directory does not remove a configured save-token-jev, does not remove the two hooks from hooks.json, and does not clear the Windows user environment variable. Confirm the target path under CODEX_HOME or %USERPROFILE%\.codex first, then treat the hooks and the environment variable as separate states to review and handle yourself.