+16
-19
@@ -77,3 +77,3 @@ // `insta setup agent` — make this machine's coding agents InstaCloud-native in one step | ||
| if (count === 0) | ||
| return '✓ insta skill installed for your coding agents'; | ||
| return '✓ Agents set up'; | ||
| const shown = names.slice(0, 6); | ||
@@ -84,3 +84,3 @@ const more = count - shown.length; | ||
| : `${count} agent${count === 1 ? '' : 's'}`; | ||
| return `✓ Agent skills — ${list}`; | ||
| return `✓ Agents — ${list}`; | ||
| } | ||
@@ -397,4 +397,4 @@ // ---- CLI self-install (makes `npx -y insta setup agent` a complete one-liner) ---- | ||
| info(env && env !== DEFAULT_ENV | ||
| ? `setting up coding-agent skills (${env}) …` | ||
| : 'setting up coding-agent skills …'); | ||
| ? `setting up your coding agents (${env}) …` | ||
| : 'setting up your coding agents …'); | ||
| const res = await run('npx', args); | ||
@@ -415,5 +415,5 @@ if (!res.ok) { | ||
| } | ||
| info(summarizeInstall(res.output ?? '')); | ||
| // Register everything first, summarize ONCE below: Claude Code via `claude mcp add`, every other | ||
| // agent via a config-file entry — different mechanisms, one outcome, one line. | ||
| // Register everything first, then summarize ONCE below: the skill files, Claude Code's | ||
| // `claude mcp add`, and the config-file MCP entries are three mechanisms with one outcome — | ||
| // "your agents are ready" — so they get one line, not three inventories of agent names. | ||
| let claude = await registerMcp(run, mint, !!opts.mcpToken, false); | ||
@@ -441,19 +441,16 @@ const others = await installConfigs(); | ||
| } | ||
| // The one MCP line. The restart note exists because config-file agents only read their config | ||
| // at startup; Claude Code picks it up live. | ||
| const mcpTargets = [...(claude === 'new' || claude === 'existing' ? ['Claude Code'] : []), ...others]; | ||
| if (mcpTargets.length) { | ||
| info(`✓ MCP — ${mcpTargets.join(', ')}${others.length ? ' (already-running tools load it on restart)' : ''}`); | ||
| } | ||
| // THE summary line. The restart note exists because config-file agents only read their MCP | ||
| // config at startup; the skill files need no restart. | ||
| const mcpOk = claude === 'new' || claude === 'existing' || others.length > 0; | ||
| info(`${summarizeInstall(res.output ?? '')} — ready to use InstaCloud${mcpOk ? ' (skill + MCP; restart any open tools)' : ''}`); | ||
| if (claude === 'new' && !opts.mcpToken) { | ||
| info(' Claude Code first use: run `/mcp` and authorize in the browser (headless machines: `insta setup agent --mcp-token`)'); | ||
| } | ||
| // The checkmarks end the install, but the user's next move shouldn't be guesswork. Agent-first: | ||
| // the whole point of setup is that the machine's coding agents now know InstaCloud (skill + MCP) | ||
| // and can drive `insta` themselves — project create/link, deploys, and (via the device flow) | ||
| // even login. The human's next move is simply to go build. | ||
| // The user's next move: one concrete action, not a concept. The agents drive `insta` themselves | ||
| // (project create/link, deploys, login via the device flow), so the human just asks for the | ||
| // thing they actually want. | ||
| info(loggedIn | ||
| ? 'next: open a coding-agent session in your app directory and keep building — your agents know InstaCloud now' | ||
| : 'next: open a coding-agent session in your app directory and keep building — your agents know InstaCloud now (they will walk you through `insta login` when it is needed)'); | ||
| ? 'next: open your coding agent inside your app and ask it to "deploy this app on InstaCloud"' | ||
| : 'next: open your coding agent inside your app and ask it to "deploy this app on InstaCloud" — it will walk you through `insta login`'); | ||
| } | ||
| //# sourceMappingURL=setup.js.map |
+1
-1
| { | ||
| "name": "insta", | ||
| "version": "0.0.42", | ||
| "version": "0.0.43", | ||
| "type": "module", | ||
@@ -5,0 +5,0 @@ "description": "InstaCloud CLI — a thin client of the platform control-plane API.", |
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
AI-detected potential code anomaly
Supply chain riskAI has identified unusual behaviors that may pose a security risk.
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
331006
-0.07%5772
-0.05%