Skip to content

Move Pi workspace under remote home#36

Merged
aniketmaurya merged 1 commit into
mainfrom
feat/pi-home-workspace
Jul 10, 2026
Merged

Move Pi workspace under remote home#36
aniketmaurya merged 1 commit into
mainfrom
feat/pi-home-workspace

Conversation

@aniketmaurya

Copy link
Copy Markdown
Collaborator

Summary

  • use $HOME/workspace as the canonical project directory on Celesto computers
  • resolve the remote home directory to a safe absolute path before registering Pi tools
  • keep file tools, shell cwd, synchronization, status, and prompts on the same resolved path
  • automatically move a non-empty legacy /workspace into the home workspace when the new location is empty
  • stage workspace replacements beside the target directory so atomic renames stay on the same filesystem
  • prepare @celestoai/pi@0.1.3

Compatibility

Existing session revisions remain valid because migration preserves the workspace files and .celesto-sync.json. If both locations contain files, $HOME/workspace wins and legacy /workspace is left untouched.

Validation

  • npm run check --prefix pi — 14 tests passed
  • package dry run for @celestoai/pi@0.1.3
  • integration test executes the workspace-preparation shell command with a temporary home and verifies legacy-file migration
  • live computer creation was attempted but the free-plan computer slot was already occupied

@coderabbitai

coderabbitai Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@aniketmaurya, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 31 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dd24d9b8-2713-40fb-a2df-1ca408c00a51

📥 Commits

Reviewing files that changed from the base of the PR and between 5ac6f53 and 477e22a.

⛔ Files ignored due to path filters (1)
  • pi/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (8)
  • README.md
  • pi/README.md
  • pi/package.json
  • pi/src/index.ts
  • pi/src/operations.ts
  • pi/src/workspace.ts
  • pi/tests/operations.test.ts
  • pi/tests/workspace.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/pi-home-workspace

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@aniketmaurya
aniketmaurya merged commit bdeb00a into main Jul 10, 2026
8 checks passed
@aniketmaurya
aniketmaurya deleted the feat/pi-home-workspace branch July 10, 2026 22:29
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.

1 participant