Add durable Session provenance and safe workspace indexes#532
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Jul 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
issue showcompact by default, with--mode detailedfor full promptsalice-workspace peer sessionsas a safe Workspace Session directory keyed by productresumeIdWhy
Cross-Session follow-up needs a durable answer to “which product Session produced this?” before collaboration can safely resume or recruit an agent. Existing Issue and Inbox views either omitted this identity or exposed backend-native fields, and Issue CLI output repeated large prompts per run.
Impact
Agents and UI consumers can now trace Inbox/Issue activity to OpenAlice-owned
resumeIdhandles without learning Codex/Pi/Claude native session ids. Missing provenance remains explicit; the Session directory is an audit/addressing surface and does not guess an owner.Validation
pnpm test— 217 files passed, 2548 tests passed, 6 skippedpnpm buildnpx tsc --noEmit/cliverification against the dev service:peer sessionsreturned real Codex/Claude/Pi histories with no native idsresumeId, omitted repeated prompts, and contained noagentSessionId