Skip to content

[Improve] Mark Daytona recommended and clarify API key scopes#172

Merged
mrubens merged 1 commit into
developfrom
feature/daytona-recommended-3hwsdo3in8zqv
Jul 11, 2026
Merged

[Improve] Mark Daytona recommended and clarify API key scopes#172
mrubens merged 1 commit into
developfrom
feature/daytona-recommended-3hwsdo3in8zqv

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

Opened on behalf of Matt Rubens. Follow up by mentioning @openmote, in the web UI, or in Slack.

Important

Roomote does not generally accept unsolicited community pull requests. Unless a maintainer invited this PR in an issue or discussion, it will likely be closed without review. A well-written issue is the best way to contribute.

Related issue

Internal product request (Slack): mark Daytona as Recommended and clarify required API key scopes.

Why this PR exists

  • A maintainer explicitly invited this PR in the linked issue or discussion
  • I am a maintainer / this is internal Roomote work

What changed

  • Marks Daytona as Recommended in the compute provider catalog (same badge as Modal and E2B in setup).
  • Setup and Settings Sandboxes credentials copy now tells operators to create an API key with write and delete on Sandboxes and Snapshots only, linking to the API Keys page.
  • Public Daytona docs include the same permission guidance and link.

Why this change was made

Daytona should appear as a recommended sandbox option, and operators need clear least-privilege guidance when creating Daytona API keys.

Impact

Operators see Daytona labeled Recommended during setup and get explicit scope instructions (with a dashboard link) when entering a Daytona API key in setup or Settings → Sandboxes. Docs match the product copy.

How it was tested

  • pnpm lint and pnpm check-types passed
  • pnpm --filter @roomote/docs check passed
  • Manual UI: Settings → Sandboxes Daytona setup shows the new API key permission text and API Keys page link

Screenshots

Daytona API key setup help text with write/delete Sandboxes and Snapshots guidance

Checklist

  • The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
  • This PR is small and scoped to one change
  • pnpm lint and pnpm check-types pass locally
  • I added tests or included a clear manual validation note above
  • I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
  • If this change should appear in the changelog, I ran pnpm changeset

@roomote-roomote

roomote-roomote Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor Author

No code issues found. See task

@mrubens
mrubens marked this pull request as ready for review July 11, 2026 05:48
@mrubens
mrubens merged commit a331b79 into develop Jul 11, 2026
1 check passed
@mrubens
mrubens deleted the feature/daytona-recommended-3hwsdo3in8zqv branch July 11, 2026 05:49
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