feat(acp): unify provider run workspaces#50
Merged
Conversation
jomeswang
marked this pull request as ready for review
July 17, 2026 13:22
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
Why
Only Claude and the Codex-compatible providers previously had explicit run-scoped preparation. Generic ACP providers ignored skillManifest and could write provider scratch files directly into a shared temp location. Codex also performed avoidable cwd marker churn and lacked atomic duplicate preparation protection.
Impact
Formal application projects remain canonical in TUTTI_APP_DATA_DIR. Selected skills, generated provider configuration, logs, and scratch files live under the resolved runtime temp directory and are removed at run completion. Generic ACP providers retain their existing authentication HOME, so Cursor/OpenCode login state remains compatible.
Provider behavior
Validation
Plan
See plan/architecture-provider-run-workspace-1.md for requirements, storage boundaries, alternatives, implementation phases, risks, and the validation record.