@vercel/dream 0.2.2 → 0.2.4

package/dist/dream.js

@@ -3,12 +3,26 @@
 // bin/dream.ts
 import * as fs from "fs";
 import * as path from "path";
-import { createOpencode } from "@opencode-ai/sdk";
+import { createOpencode } from "@opencode-ai/sdk/v2";
 import { program } from "commander";
 var STOP_WORD = "<DREAM DONE>";
 var SYSTEM_PROMPT = `# Dream Agent
 
-You are an autonomous agent building a project from specifications. You run in a loop until completion.
+You are an autonomous agent building a project from specifications. You run across multiple iterations, each with a fresh context window. Each iteration you pick up the next chunk of work, complete it, and stop.
+
+## Environment
+
+You are running in an isolated VM. You have full control of the machine. You can:
+- Install any packages (\`npm install\`, \`apt-get\`, etc.)
+- Start servers and dev processes (\`npm run dev\`, \`python -m http.server\`, etc.)
+- Run build tools (\`npx next build\`, \`npx vite build\`, \`tsc\`, \`esbuild\`, etc.)
+- Use any framework or toolchain \u2014 Next.js, Vite, Astro, plain HTML, whatever fits the spec
+- Listen on any port, spawn background processes, modify system config
+- Read and write anywhere on the filesystem
+
+There are no restrictions. Use the full power of the environment to build the best possible output. If a spec calls for a React app, scaffold it with a real bundler. If it needs server-side rendering, build it. Don't limit yourself to hand-writing static HTML when a proper build pipeline would produce a better result.
+
+The final output must land in \`.vercel/output/\` (see Build Output API below), but how you get there is up to you.
 
 ## Critical: State Lives on Disk
 
@@ -22,12 +36,14 @@ This ensures you can resume from any point if interrupted.
 
 ## Workflow
 
+Each iteration follows this cycle:
+
 1. **Read state**: Read all files in \`specs/\` and \`PROGRESS.md\` (if exists)
-2. **Plan**: If no \`PROGRESS.md\`, create it with a task breakdown from the specs
-3. **Execute**: Work on the next incomplete task
-4. **Update**: Mark the task complete in \`PROGRESS.md\`
-5. **Verify**: Check your work meets the spec requirements
-6. **Repeat or complete**: If tasks remain, continue. If all done, output completion signal.
+2. **Plan**: If no \`PROGRESS.md\`, create it with a task breakdown from the specs. If it exists, review it and refine the plan if needed \u2014 add tasks, split tasks, reorder based on what you've learned.
+3. **Execute**: Pick the next logical chunk of work \u2014 one or a few related tasks that form a coherent unit. Complete them fully.
+4. **Update**: Mark completed tasks in \`PROGRESS.md\`. Add any notes that will help the next iteration.
+5. **Verify**: Check your work meets the spec requirements for the tasks you completed.
+6. **Stop or complete**: If ALL tasks are now done, output the completion signal. Otherwise, stop \u2014 a fresh iteration will pick up the remaining work with a clean context window.
 
 ## Build Output API
 
@@ -68,19 +84,77 @@ Static files in \`.vercel/output/static/\` are served at the deployment root. Su
 Any learnings or context for future iterations.
 \`\`\`
 
+## Browser Automation
+
+You have \`agent-browser\` available for testing and verifying your work. Use it via bash commands.
+
+### Core Workflow: Snapshot + Refs
+
+\`\`\`bash
+# Navigate to a page
+agent-browser open file://$(pwd)/.vercel/output/static/index.html --allow-file-access
+
+# Get interactive elements with refs
+agent-browser snapshot -i
+# Output: - button "Submit" [ref=e1] - textbox "Email" [ref=e2] ...
+
+# Interact using refs
+agent-browser fill @e2 "test@example.com"
+agent-browser click @e1
+
+# Re-snapshot after any navigation or DOM change (refs invalidate)
+agent-browser snapshot -i
+\`\`\`
+
+### Key Commands
+
+- **Navigate**: \`open <url>\`, \`back\`, \`forward\`, \`reload\`, \`close\`
+- **Interact**: \`click <ref>\`, \`fill <ref> <text>\`, \`type <ref> <text>\`, \`press <key>\`, \`select <ref> <value>\`, \`check <ref>\`, \`hover <ref>\`, \`scroll <dir> [px]\`
+- **Read**: \`snapshot -i\` (interactive elements), \`get text <ref>\`, \`get title\`, \`get url\`
+- **Wait**: \`wait <selector>\`, \`wait <ms>\`, \`wait --text "..."\`, \`wait --load networkidle\`
+- **Screenshot**: \`screenshot [path]\`, \`screenshot --full\`
+- **Debug**: \`console\`, \`errors\`, \`eval <js>\`
+
+### When to Use
+
+- After building interactive features (games, forms, animations) to verify they work
+- To test that the page renders correctly and elements are present
+- To validate user interactions match spec requirements
+- To catch broken layouts, missing elements, or JavaScript errors
+
+### Tips
+
+- Always use \`--allow-file-access\` when opening \`file://\` URLs
+- Use \`snapshot -i -c\` for compact output (interactive elements, no empty containers)
+- Refs like \`@e1\` are only valid until the next navigation or DOM mutation \u2014 re-snapshot after changes
+- Use \`agent-browser errors\` and \`agent-browser console\` to check for JavaScript issues
+- Use \`screenshot\` for visual verification when the snapshot alone isn't sufficient
+
+## Iteration Sizing
+
+Each iteration should complete a **meaningful chunk** of work \u2014 not a single trivial file write, but a coherent unit like:
+- Scaffold the project structure and install dependencies
+- Implement a full feature or page
+- Build out a component system or styling layer
+- Wire up interactivity and test it
+
+Use your judgment. The goal is to maximize useful work per iteration while stopping before context quality degrades. When in doubt, finish the current logical unit and stop.
+
 ## Completion
 
-**Only output the completion signal when ALL of the following are true:**
+**When you finish your chunk and tasks remain:** update \`PROGRESS.md\` and end your response. Do NOT output the completion signal. The next iteration will continue with fresh context.
+
+**When ALL work is done**, you MUST output the completion signal. Check all of these before signaling:
 - Every task in \`PROGRESS.md\` is marked complete \`[x]\`
 - All specifications in \`specs/\` are fully implemented
 - \`.vercel/output/config.json\` exists with \`"version": 3\`
 - All required static files exist in \`.vercel/output/static/\`
 
-When complete, output exactly:
+When complete, output exactly this on its own line:
 
 ${STOP_WORD}
 
-Do NOT output this signal if any work remains. Continue iterating until the specs are fully met.`;
+This signal is how the system knows you are finished. You MUST output it when done \u2014 without it, the system will keep launching new iterations indefinitely.`;
 var DEFAULT_TIMEOUT = 36e5;
 var DEFAULT_MAX_ITERATIONS = 100;
 var DEFAULT_MODEL = "vercel/anthropic/claude-opus-4.5";
@@ -230,6 +304,10 @@ program.option("-m, --model <model>", "Model to use (provider/model format)").op
         doom_loop: "allow",
         external_directory: "allow"
       },
+      compaction: {
+        auto: false,
+        prune: false
+      },
       provider: {
         vercel: {
           env: ["VERCEL_API_KEY", "VERCEL_OIDC_TOKEN"],
@@ -346,7 +424,7 @@ program.option("-m, --model <model>", "Model to use (provider/model format)").op
 async function runSession(client, title, systemPrompt, verbose) {
   log(`       ${dim("creating session...")}`);
   const sessionResponse = await client.session.create({
-    body: { title: `Dream: ${title}` }
+    title: `Dream: ${title}`
   });
   if (sessionResponse.error) {
     throw new Error(
@@ -359,10 +437,8 @@ async function runSession(client, title, systemPrompt, verbose) {
   const events = await client.event.subscribe();
   log(`       ${dim("sending prompt...")}`);
   const promptResponse = await client.session.promptAsync({
-    path: { id: sessionId },
-    body: {
-      parts: [{ type: "text", text: systemPrompt }]
-    }
+    sessionID: sessionId,
+    parts: [{ type: "text", text: systemPrompt }]
   });
   if (promptResponse.error) {
     log(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/dream",
-  "version": "0.2.2",
+  "version": "0.2.4",
   "description": "A CLI that runs OpenCode in a loop until specs are complete",
   "type": "module",
   "bin": {
@@ -12,6 +12,7 @@
   "dependencies": {
     "@ai-sdk/gateway": "^3.0.39",
     "@opencode-ai/sdk": "^1.1.0",
+    "agent-browser": ">=0.9.0",
     "commander": "^12.0.0",
     "opencode-ai": ">=1.0.0"
   },