From 54b4256c8239a4bedc30639e19395370f71df9f5 Mon Sep 17 00:00:00 2001 From: CarmenDou <15951653662@163.com> Date: Fri, 4 Sep 2026 16:25:30 -0700 Subject: [PATCH 1/4] docs: quickstart leads with prompts, CLI on the second tab CTO feedback on PR #88: some steps had no prompt alternative and the prompt tab was not the default. Steps 2, 3 and 4 now each carry a Prompt / CLI code group with Prompt first, the intro says so up front, and the deploy step's collapsed block is labelled as the CLI path. Consistent tab titles let Mintlify carry the reader's Prompt or CLI choice across the page. --- docs/quickstart.mdx | 54 +++++++++++++++++++++++++++------------------ 1 file changed, 33 insertions(+), 21 deletions(-) diff --git a/docs/quickstart.mdx b/docs/quickstart.mdx index 9468c09..02b2739 100644 --- a/docs/quickstart.mdx +++ b/docs/quickstart.mdx @@ -5,53 +5,71 @@ description: "Connect your coding agent to an InstaCloud project and deploy some This guide takes you from no account to a coding agent deploying on InstaCloud. You need a coding agent (Claude Code, Cursor, Codex, or any other) and Node.js 18 or newer. No Dockerfile is needed until the last step. +Every step after the first works two ways: hand your agent a prompt, or run the CLI yourself. Where both are shown, the prompt comes first and the CLI sits on the second tab. + [Sign up](https://console.instacloud.com/signup) with GitHub, Google, or email. Already have an account? [Sign in](https://console.instacloud.com/signin) and go to the next step. - In the console, click **Create Project**. The console opens the project's **Quick Start** page, which prints the setup command for this project with its project id already filled in. + In the console, click **Create Project**. The console opens the project's **Quick Start** page, which prints the setup prompt and command for this project with its project id already filled in. {/* screenshot: console project Quick Start page, Connect-agent panel with the one-liner */} - 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: + Prefer to skip the console? Either of these also does the next step in the same run. The prompt has the agent ask whether to create a new project or link an existing one. The command creates a project named after the current directory and links it. + + + + ```text title="Prompt" wrap + Fetch and execute the appropriate instructions to set me up for InstaCloud from https://instacloud.com/prompt.md. + ``` - ```bash + ```bash title="CLI" npx -y insta@latest setup agent --create ``` + + - 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. - ```bash title="One command" - npx -y insta@latest setup agent --project + ```text title="Prompt" wrap + Fetch and execute the appropriate instructions to set me up for InstaCloud from https://instacloud.com/prompt.md. 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: . + ```bash title="CLI" + npx -y insta@latest setup agent --project ``` - 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. - 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). - 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 + + + ```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: + + + Either way you should see the environment, the signed-in user, and the linked project and branch: ```text env: prod @@ -60,13 +78,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. @@ -91,7 +103,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. - + The same commands work by hand: ```bash From bbd96524de88bc005655227dc9dd7b8e72611764 Mon Sep 17 00:00:00 2001 From: CarmenDou <15951653662@163.com> Date: Fri, 4 Sep 2026 16:36:33 -0700 Subject: [PATCH 2/4] docs: trim the skip-the-console lead to one sentence --- docs/quickstart.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/quickstart.mdx b/docs/quickstart.mdx index 02b2739..c312b3f 100644 --- a/docs/quickstart.mdx +++ b/docs/quickstart.mdx @@ -17,7 +17,7 @@ Every step after the first works two ways: hand your agent a prompt, or run the {/* screenshot: console project Quick Start page, Connect-agent panel with the one-liner */} - Prefer to skip the console? Either of these also does the next step in the same run. The prompt has the agent ask whether to create a new project or link an existing one. The command creates a project named after the current directory and links it. + Prefer to skip the console? Either of these also does the next step in the same run. From bdae60d14ce923c7583a2fd01238af2d3b53d3e6 Mon Sep 17 00:00:00 2001 From: CarmenDou <15951653662@163.com> Date: Fri, 4 Sep 2026 16:40:12 -0700 Subject: [PATCH 3/4] docs: step 2 back to console plus CLI only, intro says prompts start at step 3 --- docs/quickstart.mdx | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/docs/quickstart.mdx b/docs/quickstart.mdx index c312b3f..2ec604c 100644 --- a/docs/quickstart.mdx +++ b/docs/quickstart.mdx @@ -5,7 +5,7 @@ description: "Connect your coding agent to an InstaCloud project and deploy some This guide takes you from no account to a coding agent deploying on InstaCloud. You need a coding agent (Claude Code, Cursor, Codex, or any other) and Node.js 18 or newer. No Dockerfile is needed until the last step. -Every step after the first works two ways: hand your agent a prompt, or run the CLI yourself. Where both are shown, the prompt comes first and the CLI sits on the second tab. +From step 3 on, everything works two ways: hand your agent a prompt, or run the CLI yourself. Where both are shown, the prompt comes first and the CLI sits on the second tab. @@ -13,23 +13,15 @@ Every step after the first works two ways: hand your agent a prompt, or run the - In the console, click **Create Project**. The console opens the project's **Quick Start** page, which prints the setup prompt and command for this project with its project id already filled in. + In the console, click **Create Project**. The console opens the project's **Quick Start** page, which prints the setup command for this project with its project id already filled in. {/* screenshot: console project Quick Start page, Connect-agent panel with the one-liner */} - Prefer to skip the console? Either of these also does the next step in the same run. + 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 - Fetch and execute the appropriate instructions to set me up for InstaCloud from https://instacloud.com/prompt.md. - ``` - - ```bash title="CLI" + ```bash npx -y insta@latest setup agent --create ``` - - From 55e0d92b876be14eca23411f233e5567ead98fb0 Mon Sep 17 00:00:00 2001 From: CarmenDou <15951653662@163.com> Date: Fri, 4 Sep 2026 16:41:25 -0700 Subject: [PATCH 4/4] docs: drop the added intro sentence, keep the original opening --- docs/quickstart.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/quickstart.mdx b/docs/quickstart.mdx index 2ec604c..ed58535 100644 --- a/docs/quickstart.mdx +++ b/docs/quickstart.mdx @@ -5,8 +5,6 @@ description: "Connect your coding agent to an InstaCloud project and deploy some This guide takes you from no account to a coding agent deploying on InstaCloud. You need a coding agent (Claude Code, Cursor, Codex, or any other) and Node.js 18 or newer. No Dockerfile is needed until the last step. -From step 3 on, everything works two ways: hand your agent a prompt, or run the CLI yourself. Where both are shown, the prompt comes first and the CLI sits on the second tab. - [Sign up](https://console.instacloud.com/signup) with GitHub, Google, or email. Already have an account? [Sign in](https://console.instacloud.com/signin) and go to the next step.