npm - startup-builder - Versions diffs - 0.1.0 → 0.3.0 - Mend

startup-builder 0.1.0 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (8) hide show

package/LICENSE ADDED Viewed

@@ -0,0 +1,21 @@
+MIT License
+Copyright (c) 2026 Longtail Holdings, LLC.
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md CHANGED Viewed

@@ -1,179 +1,120 @@
 # startup-builder
-Business-as-Code. Define your startup in minutes.
-## Quick Start
+The command line for [api.sb](https://api.sb), with an optional local MCP server. Agents use it to take work from the queue: see open batches, claim one, read its prompt, close its Tasks, and give back what is left. The grammar is in `docs/grammar.md` in the source repository (a sketch).
-```bash
-npx startup-builder
+Requires Node.js 20 or newer. Start by signing in and reading a business:
+```sh
+npx startup-builder --help
+npx startup-builder login
+npx startup-builder whoami
+npx startup-builder show /headless.ly --json
+npx startup-builder help do
 ```
-## Install
+`login` opens id.org.ai in your browser; `login --device` supports terminals without a local browser. Use `--json` where the command's help offers it for structured output.
+`npx startup-builder` can use a locally installed version. Use `npx startup-builder@latest` to explicitly select the stable release channel, or an exact version to reproduce an earlier run. Keep a resolved version for a long-running assignment; new sessions can pick up releases.
+Once assigned work, an agent can use the queue:
-```bash
-npm install startup-builder
+```sh
+npx startup-builder queue for:tom
+npx startup-builder claim
+npx startup-builder prompt
+npx startup-builder close 1 --body r1.json
+npx startup-builder release
 ```
-## What You Get
+Inside a claimed batch, `close <n>` runs in do Mode with the lease's own token. Every write is versioned, so `versions <ref>` and `revert <ref> --to <v>` undo it.
-One command. Complete startup foundation.
+In claude-runner's container the dispatcher holds the claim: with `SB_BATCH` set and no local lease, the CLI builds the lease in memory from `GET <SB_BATCH>` and never writes it; `renew` and `release` are the dispatcher's. A 409 `lease_ended` means stop (exit 4).
-```bash
-startup-builder "AI code review for engineering teams"
-```
+The Owner steers the loop by editing its prompts: `startup-builder prompt coordinate-review --set new.md` writes the next version (versioned and revertible; a lease token is refused, and so is `--set` inside a batch).
+`--api` (and the other global options) go before the command: `startup-builder --api <url> show 1`. Inside a batch (`SB_BATCH` set) the API is the batch's own: `--api` is refused, and so is an `SB_API` on another origin.
+## Hosted MCP with OAuth
+Connect your agent host to `https://api.sb/mcp` using Streamable HTTP and sign in with id.org.ai through that host. No local CLI process is required. For Claude Code:
+```sh
+claude mcp add --transport http sb https://api.sb/mcp
 ```
-✓ Foundation Sprint    Complete problem/solution definition
-✓ Lean Canvas         One-page business model
-✓ ICP                 Ideal customer profile
-✓ Jobs-to-be-Done     Customer motivation map
-✓ StoryBrand          Clear messaging framework
-✓ Name                Startup name + domain
-✓ Landing Page        Ready to deploy
+Then use `/mcp` to authenticate. For Codex, configure the server and authenticate:
+```sh
+codex mcp add sb --url https://api.sb/mcp
+codex mcp login sb
 ```
-## CLI
+The hosted server exposes `search`, `fetch` and `do`. Fetch `/$.d.ts` for the current types; `do` executes TypeScript against `$`, for example `return await $.search('headless.ly')`. Check runtime limitations in the returned definitions. Connecting MCP does not automatically supply an agent's operating instructions or Objectives.
-```bash
-# Full guided experience
-startup-builder
+CLI `do` instead takes a noun verb and a target. The interfaces share api.sb but do not expose identical tools. Hosted HTTP with OAuth is the integration path for remote and web agents; validate it independently of local stdio.
-# Start from idea
-startup-builder "your startup idea"
+## Optional local MCP over stdio
-# Run specific modules
-startup-builder foundation   # Foundation sprint
-startup-builder canvas       # Lean canvas
-startup-builder icp          # Ideal customer profile
-startup-builder jtbd         # Jobs to be done
-startup-builder story        # StoryBrand messaging
-startup-builder name         # Name generation
-startup-builder landing      # Landing page
+The CLI's queue verbs are available as MCP tools (`queue`, `claim`, `prompt`, `show`, `close`, `renew`, `release`, `worklist`, `versions`, `changes`), with the same compact answers:
-# Export everything
-startup-builder export --format md
-startup-builder export --format json
+```sh
+claude mcp add startup-builder -- npx -y startup-builder mcp
+# with a bearer instead of the stored sign-in:
+claude mcp add startup-builder -e SB_TOKEN=… -- npx -y startup-builder mcp
 ```
-## SDK
-```typescript
-import { builder } from 'startup-builder'
-// Build complete startup foundation
-const startup = await builder.create({
-  idea: 'AI code review for engineering teams',
-  founder: {
-    capabilities: ['ML expertise', 'DevTools experience'],
-    insight: 'Code review is the biggest bottleneck',
-    motivation: 'Hated waiting for reviews'
-  }
-})
-// Returns complete startup package
-// {
-//   foundation: { problem, customer, solution, mvp, validation },
-//   canvas: { ... 9 boxes ... },
-//   icp: { firmographics, buyer, problems, goals, buying },
-//   jtbd: { mainJob, relatedJobs, forces },
-//   story: { character, problem, guide, plan, cta, failure, success },
-//   name: { name, tagline, domain },
-//   landing: { url, sections }
-// }
-// Build incrementally
-const foundation = await builder.foundation('AI code review')
-const canvas = await builder.canvas(foundation)
-const icp = await builder.icp(foundation)
-const story = await builder.story(foundation, icp)
-const name = await builder.name(foundation)
-const landing = await builder.landing(name, story)
-```
+Authentication works the same as the CLI: `SB_TOKEN`, else the stored sign-in (`startup-builder login`), and for the claimed batch its lease. Leases live in `~/.config/startup-builder/leases/` (mode 0600), shared by the CLI and the MCP server.
-## The Flow
+The Owner's tools are off by default. `startup-builder mcp --owner` adds `revert` and `prompt`'s `set` (a Prompt's next version), acting with the stored sign-in; without it a client holding the server can do neither.
-```
-┌─────────────────────────────────────────────────────────────────────┐
-│  1. FOUNDATION SPRINT                                               │
-│     Problem → Customer → Solution → MVP → Validation                │
-├─────────────────────────────────────────────────────────────────────┤
-│  2. LEAN CANVAS                                                     │
-│     Complete business model on one page                             │
-├─────────────────────────────────────────────────────────────────────┤
-│  3. IDEAL CUSTOMER PROFILE                                          │
-│     Know exactly who you're building for                            │
-├─────────────────────────────────────────────────────────────────────┤
-│  4. JOBS TO BE DONE                                                 │
-│     Understand why customers will buy                               │
-├─────────────────────────────────────────────────────────────────────┤
-│  5. STORYBRAND                                                      │
-│     Clarify your message                                            │
-├─────────────────────────────────────────────────────────────────────┤
-│  6. NAME + DOMAIN                                                   │
-│     Find the perfect name, claim the domain                         │
-├─────────────────────────────────────────────────────────────────────┤
-│  7. LANDING PAGE                                                    │
-│     Deploy and start collecting signups                             │
-└─────────────────────────────────────────────────────────────────────┘
+```sh
+claude mcp add startup-builder-owner -- npx -y startup-builder mcp --owner
 ```
-## Output
+## Run a worker loop
-Everything syncs to your Startups.Studio dashboard and exports to code:
+`work` claims the next batch, hands its prompt to an agent, renews the lease while it works, and releases the batch when the agent exits. Unclosed Tasks go back to the queue. Then it claims the next batch.
-```
-my-startup/
-├── startup.mdx           # Complete startup definition
-├── canvas.mdx            # Lean canvas
-├── icp.mdx               # Ideal customer profile
-├── messaging.mdx         # StoryBrand script
-├── experiments.mdx       # Validation experiments
-└── landing/              # Deployable landing page
-    ├── index.html
-    └── styles.css
+```sh
+npx startup-builder work --agent claude --for scout           # loop until the queue is empty
+npx startup-builder work --agent claude --once                # one batch
+npx startup-builder work --agent claude --wait --max-batches 20
+npx startup-builder work --agent claude --max-minutes 45        # a batch's wall-clock cap (default 30)
+npx startup-builder work --agent print                        # print the prompt; a person or another harness closes the Tasks
 ```
-## Deploy
+- **`--agent claude`** runs the local Claude Code non-interactively (`claude -p`, stream-json), on the account `claude` is logged into, a Max subscription. Its environment loses API keys, gateway and cloud-provider switches (`ANTHROPIC_API_KEY`, `ANTHROPIC_BASE_URL`, `ANTHROPIC_CUSTOM_HEADERS`, Bedrock, Vertex, Foundry, AWS credentials), other bearers (`SB_RUNNER_TOKEN`) and your lease directory.
+  - The model is `claude-opus-5-5` (`DEFAULT_MODEL` in `src/next/models.ts`); `--model` overrides it.
+  - Its tools are scoped: the batch subcommands of this CLI (`close`, `show`, `prompt`, `versions`), files in its own working directory, and web reads. `run`, `work`, `login`, `logout`, `claim`, `renew`, `release`, `revert`, `do` and anything else are denied.
+  - It is isolated from the machine: `--restricted` ignores your own Claude Code settings (allow rules, auto mode) and keeps file tools inside its working directory, `--strict-mcp-config` loads none of your MCP servers, and `--permission-mode dontAsk` denies anything not allowed.
+  - What it runs is out of its reach. Each batch gets two temp directories side by side: `sb-work-*`, its working directory, and `sb-home-*` (mode 0700), holding the `startup-builder` it finds first on its PATH (read-only, in a read-only directory) and its own config directory (`XDG_CONFIG_HOME`) with only its batch's lease. Its file tools cannot rewrite the CLI it runs, and its CLI cannot read or remove your sign-in or your other leases. Both directories are deleted when the batch ends.
+  - The lease token reaches it only as `SB_TOKEN` in its environment, never in the prompt or on a command line.
-```typescript
-// Deploy everything
-const deployed = await builder.deploy(startup, {
-  domain: 'acme.hq.sb'  // Or your own domain
-})
+### Isolation: what a batch agent can and cannot do
-// {
-//   landing: 'https://acme.hq.sb',
-//   dashboard: 'https://startups.studio/acme'
-// }
-```
+Inside a batch (`SB_BATCH` set) the CLI holds to the batch:
-## MCP Server
-```json
-{
-  "mcpServers": {
-    "startup-builder": {
-      "command": "npx",
-      "args": ["startup-builder", "mcp"]
-    }
-  }
-}
-```
+- **One API.** The lease token is bound to the API its batch was claimed on, and the stored sign-in to the API it was issued for: neither is sent anywhere else. `--api` is refused, and so is an `SB_API` on another origin.
+- **One directory.** `close --body <file>` reads only a regular file inside the agent's working directory (`SB_WORKDIR`), by its real path: no `..`, no absolute path elsewhere, no symlink out. Anything else is refused before it is read. `--body -` reads stdin.
+- **No lease management.** `renew` and `prompt --set` are refused; the loop renews the lease, and never past its own wall-clock cap (`--max-minutes`, default 30), when it stops the agent and releases the batch.
+**Accepted risk: the agent holds its own lease token.** It is `SB_TOKEN` in the agent's environment. Its file tools no longer reach the lease copy and its Bash runs only the batch subcommands, but treat the token as readable by the agent: it keeps web reads (WebFetch, WebSearch), which research needs, so an agent that got hold of the token could carry it off in a URL. The damage is bounded instead of prevented: the token reaches one batch (its Tasks, for as long as the lease, at most the wall-clock cap), the CLI will not send it to any other origin, and every write it can make on api.sb is versioned and revertible (`versions`, `revert`).
+- **`--agent codex`** runs `codex exec -` with the prompt on stdin, the same scrubbed environment (including `OPENAI_API_KEY`: codex uses its own `codex login`) and its own config directory. None of the Claude isolation flags apply: codex's own sandbox and config decide what it may run.
+- **Logs:** each batch writes one compact line per event to stdout, and the agent's stream-json to `~/.config/startup-builder/logs/`. Ctrl-C releases the batch before exiting.
+`run --cloud for:<worker>` hands a Worker's worklist to claude-runner. There is no local `run`: a local agent runs through `work`.
+On Cloudflare the same loop runs without a laptop. claude-runner's dispatcher claims batches and runs each in a Sandbox container, on a pooled Max token that is added only at egress.
+With 15 Max accounts, run one `work` per logged-in account (one machine or container each). Each claims its own batches, and a 409 on a batch someone else just took moves it on to the next.
-> "Build a startup around AI code review"
-> "Create a lean canvas for my idea"
-> "What should my MVP look like?"
+## Library
-## Includes
+`import { Api, Session, work } from 'startup-builder'` uses the same client and work loop as the CLI.
-- [foundation-sprint](../foundation-sprint) - Foundation definition
-- [lean-canvas](../lean-canvas) - Business model canvas
-- [ideal-customer-profile](../ideal-customer-profile) - Customer targeting
-- [jobs-to-be-done](../jobs-to-be-done) - Customer jobs
-- [storybrand](../storybrand) - Messaging framework
-- [startup-names](../startup-names) - Name generation
-- [landing-page](../landing-page) - Page generation
+### Migrating from 0.2
-## License
+0.3 replaces the Foundation Sprint interface with the api.sb CLI. The former Sprint commands and state-machine exports have been removed; there is no `startup-builder/machines` export. Applications using 0.2's library API must migrate before upgrading. The current exports are listed in the package's TypeScript declarations.
-MIT
+The client sends its bearer only to the API's own origin (https, or http on loopback). A URL on another origin is read without it, and a write to one is refused.