Skip to content

Teach the skills the resume_session join path - #166

Draft
Cammisuli wants to merge 2 commits into
mainfrom
resume-session-skill-verb
Draft

Teach the skills the resume_session join path#166
Cammisuli wants to merge 2 commits into
mainfrom
resume-session-skill-verb

Conversation

@Cammisuli

Copy link
Copy Markdown
Member

Teaches the Polygraph skills that resuming a session is a tracked join, not an untracked read or an ad-hoc clone.

polygraph skill

  • Tool table gains resume_session — join an existing session from this conversation: full reconstruct, tracked (CLI: polygraph session resume --session <id> --json).
  • Join flow: before doing ad-hoc work in another repo or reading a session untracked, the agent asks whether an existing session covers the work, and asks the user for the session when unknown. Working in a session's context goes through resume_session; show_session remains the read-only path.
  • Explore an Existing Session: the no-changes-until-asked rule is unchanged; what changed is the mechanics — continuing work joins via resume_session, and the resume itself is recorded in the session's history (who picked it up, when). Recording the adoption is not making changes to the work.
  • The "operates on the current repo in place" principle now states honestly that resuming performs the full reconstruct: it may switch branches inside the session's materialized repositories (refusing over uncommitted changes and explaining each refusal) and never modifies clones outside the session folder.

session-start skill

  • The existing-session path picks by intent: continue work in the session via resume_session (the primer comes back in the tool result); read-only exploration stays on show_session.

All three platform dists rebuilt; tests pass.


View Polygraph session ↗

- Add resume_session to the tool table beside start_session/show_session
- Join flow: ask whether an existing session covers the work before ad-hoc
  clones or untracked reads; resume_session to work, show_session to read
- Explore section: keep the no-changes-until-asked rule; the join is
  recorded in the session's history (who picked it up, when)
- Qualify the current-repo principle: resume's full reconstruct may switch
  branches inside session-materialized repositories, refusing dirty trees
…on path

When a session already exists and the intent is to continue work in it,
join via resume_session (tracked adoption; restored context returned in
the tool result); show_session stays the read-only alternative.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant