Skip to content

fix(pstack): treat PI_SESSION_FILE as a named path - #15

Open
shishiv wants to merge 1 commit into
feat/robust-port-create-skillfrom
feat/robust-port-session-file
Open

fix(pstack): treat PI_SESSION_FILE as a named path#15
shishiv wants to merge 1 commit into
feat/robust-port-create-skillfrom
feat/robust-port-session-file

Conversation

@shishiv

@shishiv shishiv commented Aug 26, 2026

Copy link
Copy Markdown
Owner

Why

Transcript skills described Cursor globbing. $PI_SESSION_FILE is an explicit path. Reading it does not cross workspace boundaries.

Scope

skills/recall/SKILL.md names the env path. The Users-you-proj slug is gone.

skills/poteto-mode/playbooks/eval.md and session-pickup.md read that path and do not glob.

skills/pstack-reflect/SKILL.md drops the ls -t <agent-transcripts> layout tutorial.

skills/automate-me/SKILL.md keeps "use only that path" and drops the leftover clause.

test/resources/resources.test.mjs bans crosses workspace boundaries.

src/workflows/sessions.ts is unchanged. skills/show-me-your-work/SKILL.md is unchanged.

Tradeoffs

The denylist grows by the leftover sentence this PR can make green. Banning control-ui now would fail CI.

Blast Radius

Agents that mine transcripts read $PI_SESSION_FILE instead of inventing a slug. JSONL is still one message per line.

Verification

The denylist was added first and failed on workspace-boundary leftover remains in active resources.

node --test test/resources/resources.test.mjs passed (4 tests).

npm run verify:deterministic passed (format, lint, typecheck, 79 tests, manifest).

rg "crosses workspace boundaries" skills agents automations is empty.

rg "Users-you-proj" skills agents automations is empty.

Made with Cursor

Transcript skills read the env path. They no longer invent a Cursor slug or warn that reading it crosses workspace boundaries.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant