dashboard+skill: first-run onboarding + opencomputer skill rewrite#191
Merged
dashboard+skill: first-run onboarding + opencomputer skill rewrite#191
Conversation
Replace the empty-dashboard placeholder with a two-step Getting Started panel (install command + Generate API Key button) so new accounts have a clear path from signup to first sandbox. Also consolidates the project-local openqemu skill into the opencomputer skill, and rewrites its setup section to auto-install the oc CLI and walk users through API-key creation when missing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Drop the non-existent --template flag from sandbox-create examples and correct the exec section: oc exec streams by default since #189, so --json only makes sense paired with --wait. Also document the new exec session subcommands (list/attach/kill) and --detach mode. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Drop the intermediate name-input dialog. Clicking "Create Key" now
generates a key immediately with a date-based name ("Key YYYY-MM-DD",
suffixed (2), (3)... if multiple are created on the same day) and
reveals it inline with a Copy button — same flow as the dashboard
onboarding.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This reverts commit 40b16fa.
Drop the "Generate API Key" button from the onboarding panel. When a new user lands on the dashboard with no existing keys, we now create the Default key automatically on mount and reveal it inline. The user can copy it without any clicks — the key feels like it was already provisioned at signup. If the user already has keys (e.g. created earlier in another session), we show a note explaining we can't re-display existing values for security and link to /api-keys to rotate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The WorkOS provisioning path was creating a Default API key the moment a new org was provisioned, then discarding the plaintext value. The user could never see or use that key — only its hash existed in the DB. This blocked the dashboard's onboarding flow: on first login the user already had 1 (unusable) key, so the auto-create-and-reveal step correctly bailed out. Removing the signup-time create lets the dashboard create the first key when the user lands and show its plaintext, which is the only way they can actually use it. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Stop displaying the freshly-created API key in plain text. Render it as bullets by default with explicit "Reveal" and "Copy" buttons — copy works without revealing, so the user can paste into their terminal without ever shoulder-surfing the value on screen. Same treatment for the embedded key in the 'oc config set api-key …' command row. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
🌊 Waiting for deployment on commit Detected prompts matching ⏳ complete the getting started guide at https://opencomputer.d — current: no baseline yet · View metricsPrompt text:
Evaluating agent experience using 2027.dev · View dashboard |
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
2 participants
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.
Summary
npx skills add diggerhq/opencomputerinstall command with a Copy button, and (2) a "Generate API Key" button that calls the existingcreateAPIKey('Default')mutation and reveals the key + a ready-to-pasteoc config set api-key <key>command. After the first sandbox runs, the normal dashboard view returns automatically..claude/skills/openqemu/skill (raw curl against the OpenSandbox API) in favor of the canonicalskills/opencomputer/skill (uses theocCLI).occommand: it checks forocand installs via the officialscripts/install.shone-liner if missing, then checksoc config showand (on missing key / 401) opens https://app.opencomputer.dev in the user's browser and instructs them to pasteoc config set api-key …into their own terminal. Allowed-tools widened so install + browser-launch don't trigger permission prompts.Test plan
make infra-up && make run-pg-workos+make web-dev, sign up with a fresh org, confirm the Dashboard shows "Welcome to OpenComputer" with both step cards./api-keys(no redirect loop).ocinstalled, no API key configured), invoke the opencomputer skill and confirm it (a) installs the CLI, (b) opens the dashboard in the browser, and (c) waits for the user before running sandbox commands.🤖 Generated with Claude Code