Skip to content

Use cached launch path for explicit workspace - #432

Merged
lilly-luo merged 3 commits into
mainfrom
workspace-cache-fast-path
Aug 31, 2026
Merged

Use cached launch path for explicit workspace#432
lilly-luo merged 3 commits into
mainfrom
workspace-cache-fast-path

Conversation

@lilly-luo

Copy link
Copy Markdown
Collaborator

Summary

  • allow an explicit workspace to use cached launch state when the normalized workspace matches
  • retain protection against launching with mismatched workspace state
  • add focused coverage proving the cached Codex path skips preflight

Testing

  • env -u ENABLE_SMART_ROUTING_V2 .venv/bin/pytest tests/test_cli.py -q
  • uv run ruff check src/ucode/cli.py tests/test_cli.py

@lilly-luo
lilly-luo force-pushed the workspace-cache-fast-path branch from 22b0ca1 to 9885496 Compare August 31, 2026 22:40
@lilly-luo
lilly-luo requested a review from rohita5l August 31, 2026 22:42
@lilly-luo
lilly-luo enabled auto-merge (squash) August 31, 2026 22:51
@lilly-luo
lilly-luo merged commit fcc9470 into main Aug 31, 2026
2 checks passed
@lilly-luo
lilly-luo deleted the workspace-cache-fast-path branch August 31, 2026 22:53
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.

2 participants