Skip to content

docs: quickstart leads with prompts, CLI on the second tab #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CarmenDou merged 4 commits into from
Sep 4, 2026
+20 −18
Merged

docs: quickstart leads with prompts, CLI on the second tab #92

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
54b4256
docs: quickstart leads with prompts, CLI on the second tab
CarmenDou Sep 4, 2026
bbd9652
docs: trim the skip-the-console lead to one sentence
CarmenDou Sep 4, 2026
bdae60d
docs: step 2 back to console plus CLI only, intro says prompts start …
CarmenDou Sep 4, 2026
55e0d92
docs: drop the added intro sentence, keep the original opening
CarmenDou Sep 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 20 additions & 18 deletions docs/quickstart.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,35 +23,43 @@ This guide takes you from no account to a coding agent deploying on InstaCloud.
</Step>

@cubic-dev-ai cubic-dev-ai Bot Sep 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: This delta removes the step-2 Prompt tab, so the file no longer matches the PR title ("quickstart leads with prompts, CLI on the second tab"), the step-2 bullet in the description ("add a Prompt/CLI path for the skip-the-console flow"), and the Verification criteria ("steps 2–4 render Prompt/CLI tabs with Prompt selected by default"). Step 2 now renders a single standalone bash block with no tabs and no prompt alternative. The recent commit bdae60d1 shows the removal was intentional, but the PR description, title, and verification checklist still describe the pre-walk-back state and should be updated (or the step-2 prompt restored) so the merged docs and the PR's stated goal agree.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At docs/quickstart.mdx, line 18:

<comment>This delta removes the step-2 Prompt tab, so the file no longer matches the PR title ("quickstart leads with prompts, CLI on the second tab"), the step-2 bullet in the description ("add a Prompt/CLI path for the skip-the-console flow"), and the Verification criteria ("steps 2–4 render Prompt/CLI tabs with Prompt selected by default"). Step 2 now renders a single standalone `bash` block with no tabs and no prompt alternative. The recent commit `bdae60d1` shows the removal was intentional, but the PR description, title, and verification checklist still describe the pre-walk-back state and should be updated (or the step-2 prompt restored) so the merged docs and the PR's stated goal agree.</comment>

<file context>
@@ -5,31 +5,21 @@ description: "Connect your coding agent to an InstaCloud project and deploy some
-    Prefer to skip the console? Either of these also does the next step in the same run.
-
-    <CodeGroup>
+    Prefer to stay in the terminal? Skip the console. This creates a project named after the current directory and links it in the same run:
 
-    ```text title="Prompt" wrap
</file context>


<Step title="Connect your agent" titleSize="h2">
Copy the line from the console, or use either form below with your project id.
Copy the prompt or the command from the console, or use either form below with your project id.

<CodeGroup>

```bash title="One command"
npx -y insta@latest setup agent --project <project-id>
```text title="Prompt" wrap
Fetch and execute the appropriate instructions to set me up for InstaCloud from https://instacloud.com/prompt.md. Project id: <project-id>.
```

```text title="One prompt" wrap
Fetch and execute the appropriate instructions to set me up for InstaCloud from https://instacloud.com/prompt.md. Project id: <project-id>.
```bash title="CLI"
npx -y insta@latest setup agent --project <project-id>
```

</CodeGroup>

Both paths do the same work. The `insta` CLI is installed globally, the `insta` skill and the remote MCP server are registered for every coding agent on this machine, the console opens in your browser once so you can approve the sign-in, and the current directory is linked to the project. The command is safe to run again.
Both do the same work. The `insta` CLI is installed globally, the `insta` skill and the remote MCP server are registered for every coding agent on this machine, the console opens in your browser once so you can approve the sign-in, and the current directory is linked to the project. Both are safe to run again.

<Note>
The command targets production. Machines without Node, native Windows shells, and the staging deployment are covered in [Set up your coding agent](/agents/setup).
Setup targets production. Machines without Node, native Windows shells, and the staging deployment are covered in [Set up your coding agent](/agents/setup).
</Note>
</Step>

<Step title="Verify" titleSize="h2">
Check the CLI first:
Start a new agent session so it picks up the MCP server, then ask it to check the wiring. Or run the check yourself.

```bash
<CodeGroup>

```text title="Prompt" wrap
Check my InstaCloud setup: run insta status and call insta_whoami.
```

```bash title="CLI"
insta status
```

It prints the environment, the signed-in user, and the linked project and branch:
</CodeGroup>

Either way you should see the environment, the signed-in user, and the linked project and branch:

```text
env: prod
Expand All @@ -60,13 +68,7 @@ This guide takes you from no account to a coding agent deploying on InstaCloud.
project: 7d3c2a10-5b8e-4f61-9a2c-0e4f6b1d8c35 (branch main)
```

Then start a new session in your agent and send it this prompt:

```text wrap
Check my InstaCloud setup: run insta status and call insta_whoami.
```

If both answer, the CLI, the skill, and the MCP server are all wired. In Claude Code, `claude mcp list` also shows `insta-cloud` as connected.
If the agent gets answers from both `insta status` and `insta_whoami`, the CLI, the skill, and the MCP server are all wired. In Claude Code, `claude mcp list` also shows `insta-cloud` as connected.
</Step>

<Step title="Deploy something" titleSize="h2">
Expand All @@ -91,7 +93,7 @@ This guide takes you from no account to a coding agent deploying on InstaCloud.

The agent adds the services, wires the database credentials into compute, and deploys. When it finishes it reports the service URL. You approve the sign-in, and the agent drives the rest.

<Accordion title="What the agent runs">
<Accordion title="CLI: the commands the agent runs">
The same commands work by hand:

```bash
Expand Down
Loading