[Improve] Mark Daytona recommended and clarify API key scopes#172
Merged
Conversation
Contributor
Author
|
No code issues found. See task |
mrubens
marked this pull request as ready for review
July 11, 2026 05:48
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 11, 2026 05:48
8 tasks
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.
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
What changed
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 lintandpnpm check-typespassedpnpm --filter @roomote/docs checkpassedScreenshots
Checklist
[Fix],[Feat],[Improve],[Refactor],[Docs], or[Chore]followed by a user-facing descriptionpnpm lintandpnpm check-typespass locallypnpm changeset