Skip to content

Releases

afk-compact 0.1.18

Choose a tag to compare

@RuslanTar RuslanTar released this 16 Nov 23:19

afk-compact 0.1.18 fixes the smoke check's C8 step, which failed on Claude Code 2.1.321 to 2.1.323 and 2.1.325, so /afk-compact:status kept asking you to run smoke. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Fixed

  • On Claude Code 2.1.321 to 2.1.323 and 2.1.325 smoke failed with SMOKE FAIL c8, so /afk-compact:status kept asking you to run it. That is fixed: C8 now compares with the strings of 2.1.325 and passes there; the request goes away once smoke passes. On 2.1.314 C8 now fails.

afk-compact 0.1.17

Choose a tag to compare

@RuslanTar RuslanTar released this 16 Nov 05:25

afk-compact 0.1.17 fixes how the plugin recognises running sessions and reads GSD progress under Git Bash and Cygwin on Windows, lets you name folders /afk-compact:prune never works in, and ignores its internal test switches in normal runs. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Added

  • A prune_protected_roots setting, and prune --protect DIR, name folders /afk-compact:prune never works in. When a folder it would read or delete in is one (also through a link or another spelling), lies inside one or holds one, prune refuses and deletes nothing.

Changed

  • After the update, every session reads its whole transcript once more for the GSD line, on any operating system: the GSD line now reads Windows file paths it used to skip, so its saved progress starts over once. Later reads take only the new part of the transcript again.
  • /afk-compact:prune now marks a manifest row pruned only after its file is deleted, so a file that could not be deleted, or a run that stopped early, never leaves a row saying pruned for a file that is still there.

Fixed

  • Under Git Bash or Cygwin on Windows, GSD work done through Edit and Write is now seen: Claude Code on Windows records those files as C:\…\.planning\STATE.md, which the GSD line missed. Paths on a network share or in WSL (\\server\…) are still not read.
  • Under Git Bash or Cygwin on Windows, when the session's transcript is in more than one project folder, the GSD line now reads it from the folder Claude Code names from the Windows path (C--work-app for C:\work\app).
  • Under Git Bash or Cygwin on Windows, a running Claude Code session started from PowerShell, cmd, Windows Terminal or Git Bash is no longer taken for ended, so another session no longer closes its open work, takes over its handoff or reports its background jobs as lost.
  • Under Git Bash or Cygwin on Windows, the plugin's skills, which run through the Bash tool, now find the session they run in, instead of working as if outside any session.
  • Under Git Bash or Cygwin on Windows, the resume skill's check of background work no longer reports a running Claude Code session started from PowerShell or Git Bash as not running. A session started from PowerShell now reads as unverified, as its start time cannot be read.

Security

  • The plugin's internal test switches no longer take effect when they are only set in the environment of a normal run; before, they could change its clock and path reading, so /afk-compact:prune could list and delete evidence younger than its age limit.

afk-compact 0.1.16

Choose a tag to compare

@RuslanTar RuslanTar released this 15 Nov 20:05

afk-compact 0.1.16 keeps your standing approvals working across the plugin's own handoffs, compactions and resumes, counts an approval as standing only when your words say so, and asks again for denied approvals and pushes that reach every branch. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Changed

  • A standing approval now stays valid after a handoff the plugin asked for itself (idle, before a compaction, at a stop). The plugin puts back each standing approval your previous handoff held as checked. One-time approvals in such a handoff are still asked again.
  • After a compaction or a resume, a standing approval you already used still counts. Before, the resume rule said to act only on an unused one. Deploys, environment, infrastructure and production writes, and protected-branch pushes are still always asked again.
  • An approval counts as standing only when your own words say so, such as "don't ask again", "feel free to" or "from now on". Words like "just this once" or "for now" in the same sentence keep it one-time. Saving a handoff notes a line that calls other words standing.
  • After a compaction or a resume, an approval whose action was refused in the session, or in an earlier session of your chain, is listed as denied and asked again.

Fixed

  • An approval for git push --all, --branches or --mirror now counts as a push to a protected branch and is asked again after a compaction or a resume, since such a push reaches every branch.
  • After a compaction, approvals the summary copied from a handoff (with the question after your words, or a used time with words) were not read, and the resume block said Approvals (checked): none. They are read now, and a line the plugin cannot read is listed to ask again.

afk-compact 0.1.15

Choose a tag to compare

@RuslanTar RuslanTar released this 15 Nov 13:29

afk-compact 0.1.15 fixes the status line meter: it reads 0m as soon as you send a prompt and stays compacted after a compaction until your next request. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Fixed

  • The status line meter now reads 0m as soon as you send a prompt, instead of a brief cold or the old cache's age while the request is under way. After a compaction it stays compacted until your next request, however long the session is idle.

afk-compact 0.1.14

Choose a tag to compare

@RuslanTar RuslanTar released this 15 Nov 07:26

afk-compact 0.1.14 moves keep-warm's first request, in an idle gap where Claude Code's own idle compaction can run, to after that compaction, so the request is no longer wasted. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Changed

  • In an idle gap at Claude Code's idle minimum (200,000 tokens by default) or more on the one-hour cache, keep-warm's first request now comes at about minute 55, not 50. Claude Code compacts such a gap at about minute 54, and a request at 50 did not stop that.
  • Keep-warm now sends that first request only when Claude Code did not compact; when it did, keep-warm stops (compacted) without a request. A failed request is still tried again a minute later, at minutes 56 and 57.
  • The later timing needs the plugin to have seen the gap's last request; after a reload during the turn, the first request stays at minute 50.
  • With the later timing, a machine put to sleep between minutes 50 and 55 of such a gap loses the cache, and the status line meter shows no keep-warm mark until that first request. With "idleCompaction": false in settings.json, the first request still comes at minute 50.
  • The log's keep_warm_start row and a refused keep_warm_stop row now say which timing applied, in first_due_s and first_why (native-window or default).

afk-compact 0.1.13

Choose a tag to compare

@RuslanTar RuslanTar released this 15 Nov 06:24

afk-compact 0.1.13 adds a prompt cache meter for your status line, with a /afk-compact:settings step that prints its snippet, keeps a status line quiet once the plugin's folder is gone, and stops a false copy-mismatch warning for Claude Code's trailer. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Added

  • A cache meter for your status line: cache --stdin --bar prints ██████░░░░░░ 30m, 12 cells filling as the cache nears expiry (blue, yellow from half its lifetime, red from 90%) and the cache's age. Before the first response, or with an unknown lifetime, it prints nothing.
  • The meter reads ↻3/7 in cyan while keep-warm runs, cold 1h02m or cold miss in magenta for a cold cache, and compacted after a compaction. Its flags are stable but its text may change, so use --json if you parse the output.
  • Meter options: --left shows time left instead of age, --short drops the cells, --ascii draws # and -, and --color auto|always|never follows NO_COLOR and TERM=dumb. A locale that is not UTF-8 turns on --ascii, and a COLUMNS below 60 turns on --short.
  • Where the plugin's helper cannot run, --bar prints nothing and exits 0 instead of REFUSED: helper-runtime. A plugin copy older than 0.1.13 does not know --bar and shows nothing until you update.
  • /afk-compact:settings has a "Status line meter" step that reads which status line your user, project and local settings run (only the name of what it runs, never the full command), previews the meter and prints a snippet for your case to paste. It changes no file.
  • The snippet is a settings entry, a script adding the meter as a second line under your own, or values for a ccstatusline Custom Command widget. It runs the meter only once the plugin's fixed path exists, so before the plugin's first session the line stays empty, not an error.

Fixed

  • A status line that calls ~/.local/state/afk-compact/bin/afk-compact-store no longer prints sh errors after an uninstall, a prune or a failed update: with the installed copy gone it now prints nothing and exits 0.
  • The file at that path is rewritten at the next session start if an earlier version wrote it, and is now also written when the plugin folder's path contains a '.
  • After a downgrade to 0.1.12 or earlier, that file keeps running the 0.1.13 copy while it exists, as older versions leave it alone; once that copy is gone the segment stays blank. Delete the file and the older version writes its own at its next session start (without --bar).
  • When the installed summary differed from the saved copy only by lines Claude Code added after the end marker, a complete copy got a false copy-mismatch toast and an escalations: count in /afk-compact:status. Not any more; a real difference is still shown and counted.

afk-compact 0.1.12

Choose a tag to compare

@RuslanTar RuslanTar released this 14 Nov 12:57

afk-compact 0.1.12 stops ordinary file paths from reading as secrets, and fixes repo mode, GSD re-entry and checkout paths with letters outside ASCII under Git Bash on Windows. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.325.

Fixed

  • Ordinary file paths, such as a macOS or Windows temp folder or a long project path, no longer read as secrets, so you no longer get a false ADVISORY secret-warn, a refused repo-mode export, a secret question on resume or a redacted evidence copy.
  • A real key with / inside, one that starts with /, and one kept as a single part of a path are still caught, and the report's own secret scan applies the same path rule.
  • Under Git Bash, a repository listed in repo_roots and the worktrees git made for it are now accepted, and the hint names the folder in the form the settings read; before, git's drive-letter paths (C:/…) were read as relative, so no listed repository was accepted.
  • Under Git Bash, a repo_roots entry written with its drive letter (C:/work/app, C:\work\app) is now accepted. Repo mode with drive-letter repository paths was checked only by emulation on macOS, not yet on a real Windows machine, so it may still misbehave there.
  • Under Git Bash, the GSD re-entry, Was driving and Active driver commands for work in the session's own checkout no longer get a stray --cwd <this checkout>, and measure and locate print the checkout's folder in the same form as the current folder.
  • Under Git Bash, measure <handoff> with a GSD line no longer stops with Out of memory! before any output when the checkout's path holds a letter outside ASCII, such as ë.

afk-compact 0.1.11

Choose a tag to compare

@RuslanTar RuslanTar released this 12 Nov 22:49

afk-compact 0.1.11 makes keep-warm easier to follow: it says why it stays off for an idle gap, shows a request while it is out, and its results appear in reports. It also reads usage near a limit more strictly and fixes several problems under Git Bash on Windows. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.322.

Added

  • When keep-warm does not start in an idle gap, /afk-compact:status shows keep-warm off (<why>), or the last gap: keep-warm off (<why>) after a later request, and the log records the reason (such as no-jobs, ttl-5m, near-limit, no-idle-path or cutoff).
  • The status line command adds · keep-warm off (<why>) to its cache line when keep-warm stays off, except for no-jobs (no background job of the session is open), which is the normal idle case.
  • While a keep-warm request is out, the status line command adds · ping pending, for at most 150 seconds.
  • The JSON output of the status line command (cache --stdin --json) gains a label key (warm, compacted, cold or unknown), plus keep_warm.pending and keep_warm.off for the two new status line parts.
  • A keep-warm request that reads the cache but takes over about 2 minutes, or returns over 58 minutes after the last cache refresh, is logged as late, counts for nothing and ends keep-warm for the gap. A slow request that did not read the cache, or failed, keeps its own result.
  • /afk-compact:report adds keep-warm.json to its zip and watch report adds a Keep-warm section, both built from the log and holding only counts, durations, reasons and versions.
  • The keep-warm report lists idle gaps warmed and refused (by reason), requests sent and how they came back (warm, fork-miss, late or failed), why warming stopped, gaps handed back to plugin idle compaction or the idle handoff turn, and the next main request's cache result.
  • After a pause of 5 minutes or more, the log records the pause and whether the first main response read the cache (hit, miss or none), with its cache reads, cache writes and uncached input, and Claude Code's cache miss reason and missed tokens when given. It holds no text.

Changed

  • Breaking: After a compaction the status line reads cache compacted, not cache cold (compacted), as the next request writes the cache anew. If your script matched cold (compacted), read the JSON label key (compacted) instead; state still reads cold.
  • Near a usage limit, plugin idle compaction, keep-warm and the idle handoff turn treat a reading as new only when a limit's share moved or a response came. A report that only the context or cost moved no longer lets them go past 90% on a reading that says nothing of usage since.
  • A usage reading dated more than a minute ahead of the clock is now stale for going past 90%, since its time is not known.
  • A limit reset time further ahead than its window is long (over about 5 hours for the five-hour limit, about 7 days for the seven-day one) is no longer believed; the reading counts as one with no reset time, in the shared usage record too.
  • /afk-compact:report, and watch report with --out, still never replace an existing file, but now print REFUSED: output file exists (exit 73) instead of REFUSED: output folder not writable.

Fixed

  • When the shared usage record is full, a reading dated ahead of the clock with a smaller share no longer pushes out the real latest reading of its period; the record now keeps the same latest reading the plugin decides by.
  • Two watch report runs on one date could pick the same file name, so one report replaced the other or the second said the folder was not writable. Without --out it now takes the next free number, and skips a name held by a broken link instead of writing through it.
  • A wait --for path starting with a drive letter (file:C:/work/out.log, exit:C:\…, marker:C:/…:<regex>), as Claude Code gives paths on Windows, was refused as a usage error. It now parses.
  • Under Git Bash on Windows, the worktree's path has a drive letter, so the handoff check read every GSD STATE.md as outside it and a handoff never got its GSD state. It now reads it, and a nested checkout is still refused.
  • In a folder outside git whose name has non-ASCII characters, handoffs were saved under a second, wrongly encoded folder, and the session's own handoff was taken for another session's.
  • Under Git Bash the helper took process 1 for Claude Code, so the session's alive record, sessions and locks all named it. Under Git Bash and Cygwin it now uses Claude Code's own CLAUDE_PID; on macOS and Linux an orphaned helper keeps process 1, as before.
  • /afk-compact:status grouped only other sessions' usage readings by period, so the session's own reading could look like the deciding one when it was not. It now says when another session read the same period later, with that share.
  • In /afk-compact:status, on a full tie the session's own usage reading stays the latest, as in the plugin, and a reading dated more than a minute ahead of the clock shows as of unknown time.

afk-compact 0.1.10

Choose a tag to compare

@RuslanTar RuslanTar released this 12 Nov 20:06

This release fixes a hang on the first prompt after claude --resume, a fault present since 0.1.4, and makes a resumed session pick up halt mode before that prompt. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.322.

Fixed

  • After claude --resume, the first prompt no longer hangs with no request sent (seen on Claude Code 2.1.322). The plugin no longer waits for the compaction window reading before that prompt; it still reads the window once and uses it as soon as it arrives.
  • A resumed session now reads halt mode and its idle state from the earlier session before handling the first prompt, so a note restored on that prompt shows halt mode when it is on.

afk-compact 0.1.9

Choose a tag to compare

@RuslanTar RuslanTar released this 12 Nov 01:02

afk-compact 0.1.9 keeps near-limit stops in force through long idle gaps, because a usage reading now counts until its limit resets instead of for only 10 minutes. It also supports installs that Claude Code reads in place from a local folder marketplace. The one-line install needs 2.1.292 or newer. Requires Claude Code 2.1.287 or newer; tested against 2.1.319.

Changed

  • Near a usage limit, plugin idle compaction, keep-warm and the idle handoff turn count a reading until its limit resets, as the share only grows and an idle session's reading is never refreshed, even by keep-warm. Past the reset it counts for nothing; without one, 10 minutes.
  • Readings of one limit with the same reset time (within a minute) form one period, its share being the latest. A limit stops these actions only when every period is at or over it, so behind a proxy that spreads requests over several accounts, an account with room lets them run.
  • With an agent, a workflow or a working teammate open, these actions still run past 90% only on a reading from the last 10 minutes. An older one stops them at 90%, and the log row says rule: stale.
  • A reading of unknown time, such as one dated more than a minute ahead of the clock or the session's own reading just after a plugin reload, before Claude Code refreshes it, becomes its period's latest only when its share is larger.
  • When no limit is reported, for example in a session restarted during an idle gap before its first response, the session's own entries in the shared usage record stand for it, beside other sessions' entries. After a plugin reload they are also read beside the reported reading.
  • The shared usage record keeps an entry until its limit resets, and one with no reset time for 10 minutes after it was last read or shown. A full record never drops a period's latest reading.
  • /afk-compact:status lists each of the session's usage readings with its age and reset time, marking as "not counted" one past its reset or one with no reset time after 10 minutes. It also lists the other sessions' counted readings, the latest of each period.
  • Usage writes are throttled: one runs at a time, a refresh during a write is folded into one check after it, and shares are compared in whole points. Many parallel subagents now start one helper process instead of one each.

Fixed

  • A copy Claude Code reads in place from a local folder marketplace now counts as installed: its first session writes the status line's fixed command path, and options and version scope resolve as for other installs. A --plugin-dir load of that folder never changes the path.
  • After you uninstall such a copy, the status line's fixed command path keeps running that folder while it exists, because Claude Code never deletes it. Delete ~/.local/state/afk-compact/bin/afk-compact-store yourself and remove its call from your status line.
  • A session whose marketplace was later pointed at another folder keeps its install by its data folder, and a --plugin-dir data folder under CLAUDE_CODE_PLUGIN_CACHE_DIR stays a --plugin-dir load.
  • The status line's next keep-warm time (keep_warm.next_due_at) now follows the gap's own ping interval, which the keep_warm_start log row now records as ping_s.