fix(server): keep workspace reuse as the default - #171
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 45 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryThe PR updates model-facing descriptions and instructions so existing workspace IDs are reused by default, while preserving the underlying workspace lifecycle behavior.
Confidence Score: 5/5The PR appears safe to merge with no actionable defects identified in the wording-only workspace contract changes. The revised descriptions consistently preserve initial workspace creation, continued ID reuse, and unknown-ID recovery while leaving checkout, worktree, registry, and context-loading mechanics unchanged.
|
| Filename | Overview |
|---|---|
| src/server.ts | Updates MCP server, tool, and workspace-response wording to consistently promote reuse without changing execution behavior. |
| src/workspaces.ts | Revises the unknown-workspace error to describe reopening the target and continuing with the replacement ID. |
| src/artifact-tools.ts | Aligns artifact download metadata with the reuse-first workspace contract. |
| src/server.test.ts | Adds contract coverage for reuse-first descriptions and updates assertions for the revised response wording. |
Reviews (1): Last reviewed commit: "fix(workspace): make unknown id recovery..." | Re-trigger Greptile
Long-running MCP sessions could repeatedly call
open_workspacebecause normal tool descriptions presented it as a prerequisite, even while an existing workspaceId was still usable. That made reopening feel like the default action instead of continuing in the current workspace.\n\nThis makes the model-facing contract reuse-first: the server description is intentionally short,open_workspaceis only for establishing a missing workspace, downstream tools simply consume the existing workspaceId, and unknown IDs provide the recovery path. The change is wording-only for workspace lifecycle behavior; existing checkout/worktree mechanics stay unchanged.