@tduyng/pi-session 0.0.3 → 0.0.4

package/README.md

@@ -1,47 +1,37 @@
 # @tduyng/pi-session
 
-Sessions name themselves, and a turn killed by a usage limit resumes when the limit resets. No more `untitled` rows in the picker, no more sitting out a quota by hand.
+Two gaps in session handling, both filled from what is already on disk. A session names itself from the first user message. A turn killed by a usage limit resumes when the limit resets.
 
-## What it costs
+Nothing is configured and no tool is registered.
 
-Nothing. No tool is registered, no prompt text is injected, and no session entry is created for the naming. The extension reads at `agent_end` and writes a name.
+## Naming
 
-## Auto-name
+A new session starts unnamed, so a picker fills with `2026-09-01 14:22` rows and the session wanted is the one that cannot be identified.
 
-A new session starts unnamed. On `agent_end` the extension reads the first user message and uses it: first line, a leading `/` or `#` stripped, whitespace collapsed, 60 characters at most, cut at a word boundary.
+On `agent_end` the extension reads the first user message and uses it: first line, a leading `/` or `#` stripped, whitespace collapsed, 60 characters at most, cut at a word boundary.
 
-Before, a week of `2026-09-01 14:22`, `2026-09-01 14:47`, `2026-09-02 09:03`. After, `fix retry backoff`, `review auth diff`, `migrate schema`.
+A week of timestamps becomes `fix retry backoff`, `review auth diff`, `migrate schema`.
 
-An expanded skill uses its argument when one is present, or the skill name when it has none. The extension ignores the expanded instructions and the skill's filesystem path. A `/skill:name task` command follows the same rule and uses `task`. A `Skill invocation protocol` message with no skill block is skipped, because an extension injected it. A name you set with `/name` always wins.
+An expanded skill uses its argument when there is one, otherwise the skill name. A `/skill:name task` command uses `task`. A name set with `/name` always wins, and naming runs last and swallows its own errors, because it is cosmetic and must never block a turn.
 
-Naming runs last and swallows its own errors. It is cosmetic and never blocks a turn.
+## Resuming after a quota reset
 
-## Autoresume
+When a provider quota kills a turn, the error usually carries a reset time. The parser accepts the shapes that appear in practice: epoch, ISO, `try again in 2h 15m`, `resets 11:30pm (Europe/Paris)`, `retry-after: 3600`.
 
-When a provider quota exhaustion kills a turn, the extension parses a reset time out of the error text. It accepts:
+For a `claude-bridge` session with no time in the error, it asks the Anthropic OAuth usage endpoint and takes the latest reset among the exhausted windows. The usage API wins over the error text, since the error is a snapshot and the API is the current state.
 
-- Epoch timestamps: `limit reached|1757193000`
-- ISO timestamps: `resets at 2026-09-06T23:30:00+02:00`
-- Relative times: `try again in 2h 15m`, `retry after 3600 seconds`
-- Clock times: `resets 11:30pm (Europe/Paris)`, `reset at 23:30`
-- Retry-after headers: `retry-after: 3600`
+The resume is a real user message on the same session: "The usage limit has reset. Continue the previous task from where it stopped." Nothing is replayed and nothing is stored.
 
-For a claude-bridge session whose error carries no reset time, it asks the Anthropic OAuth usage endpoint and picks the latest reset among the exhausted windows, with the credential from the macOS keychain or `~/.claude/.credentials.json`.
+A scheduled resume adds a 5 second safety delay past the reset and caps at 24 hours. Further out than that it warns and schedules nothing. Any user turn or session shutdown cancels it, so a timer never fires over work already resumed by hand.
 
-A 5-second safety delay is added past the reset, and the timer caps at 24 hours. A reset further out than 24 hours schedules nothing and posts a warning instead. Any user turn or session shutdown cancels it. The resume sends a real user message: "The usage limit has reset. Continue the previous task from where it stopped."
-
-A quota reset is the cheapest minute of the day to be running: the window opened, the work is ready, and nobody has to be awake for it.
-
-| Command | Effect |
-| --- | --- |
-| `/autoresume` | Status |
-| `/autoresume on` | Arm it |
-| `/autoresume off` | Disarm it |
-| `/autoresume cancel` | Drop the pending resume |
-
-## Design
+```
+/autoresume            status, including the pending resume time
+/autoresume on
+/autoresume off
+/autoresume cancel
+```
 
-Autoresume touches no session storage and adds no tool beyond its command. Session creation, storage, and selection stay with pi.
+The quota lookup reads the Claude Code OAuth credential from the macOS keychain item `Claude Code-credentials`, or from `~/.claude/.credentials.json`. Nothing else is read, and no value is logged.
 
 ## Install
 
@@ -51,4 +41,11 @@ pi install npm:@tduyng/pi-session
 
 Local checkout: `pi install /path/to/dotfiles/pi/agent/extensions/pi-session`
 
-No configuration required.
+Naming needs nothing. The quota lookup needs network access to `api.anthropic.com` and either keychain access (macOS may prompt once) or the credentials file.
+
+## Limits
+
+- Names are cut at 60 characters on a word boundary.
+- The resume polls its timer every 10 seconds, so it can fire up to 10 seconds late.
+- The quota lookup is Anthropic only. Other providers get the error-text path.
+- A provider that changes its error wording gets no resume.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tduyng/pi-session",
-  "version": "0.0.3",
+  "version": "0.0.4",
   "description": "Sessions name themselves, and a turn killed by a usage limit resumes when the limit resets.",
   "keywords": [
     "pi",