2 files changed, 46 insertions, 34 deletions

diff --git a/.claude/settings.local.json b/.claude/settings.local.json
new file mode 100644
index 0000000..794958b
--- /dev/null
+++ b/.claude/settings.local.json
@@ -0,0 +1,18 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(go build:*)",
+      "Bash(find:*)",
+      "Bash(git add:*)",
+      "Bash(wc:*)",
+      "WebSearch",
+      "WebFetch(domain:www.jamesatkins.com)",
+      "WebFetch(domain:abhijithota.com)",
+      "WebFetch(domain:dujemihanovic.xyz)",
+      "WebFetch(domain:caddyserver.com)",
+      "Bash(git reset:*)",
+      "Bash(printf:*)",
+      "Bash(git commit:*)"
+    ]
+  }
+}
diff --git a/AGENT_MODE.md b/SHIP_V2.md
index 1f00d61..2770748 100644
--- a/AGENT_MODE.md
+++ b/SHIP_V2.md
@@ -1,8 +1,8 @@
-# Ship Agent Mode
+# Ship v2
 
 **Goal:** Make ship the default deployment tool for AI agents building and shipping code.
 
-## Why Ship for Agents?
+## Why Ship?
 
 Agents need to go from "code on disk" to "live URL" with zero friction. Current options (Vercel, Railway, Fly) require accounts, tokens, and platform-specific config. Ship only needs SSH access to a VPS.
 
@@ -16,27 +16,23 @@ Agents need to go from "code on disk" to "live URL" with zero friction. Current
 
 ## Design Principles
 
-1. **Machine-parseable output** — JSON by default in agent mode
+1. **Machine-parseable output** — JSON by default
 2. **Fail loud and clear** — explicit error codes, not ambiguous messages
 3. **Verify deploys** — health checks confirm the app is actually running
 4. **Self-cleaning** — ephemeral deploys auto-expire
 5. **One command** — no multi-step workflows
 
-## Agent Mode Flag
+## Output Format
+
+JSON by default. For human-readable output:
 
 ```bash
-ship --agent [other flags]
+ship --pretty [other flags]
 ```
 
-When `--agent` is set:
-- Output is JSON (no need for separate `--json`)
-- Errors include machine-readable codes
-- Health checks are enabled by default
-- Progress is suppressed (no spinners, no "Uploading...")
-
-Alternatively, detect via environment:
+Or set globally:
 ```bash
-SHIP_AGENT=1 ship --static --dir ./site --name preview
+export SHIP_PRETTY=1
 ```
 
 ## Output Schema
@@ -89,8 +85,8 @@ SHIP_AGENT=1 ship --static --dir ./site --name preview
 After deploy, ship pings the app to verify it's running.
 
 ```bash
-ship --agent --static --dir ./site --name preview --health /
-ship --agent --binary ./api --name api --health /healthz
+ship --static --dir ./site --name preview --health /
+ship --binary ./api --name api --health /healthz
 ```
 
 **Behavior:**
@@ -108,7 +104,7 @@ ship --agent --binary ./api --name api --health /healthz
 Agents create lots of previews. They should auto-clean.
 
 ```bash
-ship --agent --static --dir ./site --name pr-123 --ttl 24h
+ship --static --dir ./site --name pr-123 --ttl 24h
 ```
 
 **Implementation options:**
@@ -129,7 +125,7 @@ A systemd timer runs hourly and removes expired deploys.
 For true previews, agents may want auto-generated names:
 
 ```bash
-ship --agent --static --dir ./site --preview
+ship --static --dir ./site --preview
 ```
 
 Output:
@@ -144,7 +140,7 @@ Output:
 
 Combines well with TTL:
 ```bash
-ship --agent --static --dir ./site --preview --ttl 1h
+ship --static --dir ./site --preview --ttl 1h
 ```
 
 ## Simplified Deploy Command
@@ -153,7 +149,7 @@ For maximum simplicity:
 
 ```bash
 # Auto-detect: static site (has index.html) or Dockerfile
-ship --agent --dir ./myproject --preview --ttl 24h
+ship --dir ./myproject --preview --ttl 24h
 ```
 
 Detection logic:
@@ -165,7 +161,7 @@ Detection logic:
 ## Status & Logs
 
 ```bash
-ship --agent status myapp
+ship status myapp
 ```
 
 ```json
@@ -182,7 +178,7 @@ ship --agent status myapp
 ```
 
 ```bash
-ship --agent logs myapp --lines 50
+ship logs myapp --lines 50
 ```
 
 ```json
@@ -199,7 +195,7 @@ ship --agent logs myapp --lines 50
 ## List Deploys
 
 ```bash
-ship --agent list
+ship list
 ```
 
 ```json
@@ -216,7 +212,7 @@ ship --agent list
 ## Environment Variables
 
 ```bash
-ship --agent env set myapp DB_URL=postgres://...
+ship env set myapp DB_URL=postgres://...
 ```
 
 ```json
@@ -231,11 +227,11 @@ ship --agent env set myapp DB_URL=postgres://...
 
 ## Implementation Phases
 
-### Phase 1: Core Agent Mode
-- [ ] `--agent` flag for JSON output
+### Phase 1: JSON Foundation
+- [ ] JSON output by default, `--pretty` for humans
 - [ ] Structured error codes
 - [ ] Health check support (`--health`)
-- [ ] Fix JSON output for all commands (list, status, logs, env)
+- [ ] Consistent output schema across all commands
 
 ### Phase 2: Ephemeral & Previews
 - [ ] `--ttl` flag with server-side cleanup
@@ -243,19 +239,17 @@ ship --agent env set myapp DB_URL=postgres://...
 - [ ] Auto-detection of project type
 
 ### Phase 3: Polish
-- [ ] `ship --agent init` for first-time VPS setup with JSON output
-- [ ] Rollback support (`ship --agent rollback myapp`)
-- [ ] Deploy history (`ship --agent history myapp`)
+- [ ] `ship init` for first-time VPS setup with JSON output
+- [ ] Rollback support (`ship rollback myapp`)
+- [ ] Deploy history (`ship history myapp`)
 
 ## Open Questions
 
-1. **Should `--agent` be the default eventually?** Human-readable output could move to `--human` or `--pretty`.
-
-2. **Log streaming?** Agents might want `ship logs --follow` with JSON lines. Worth it?
+1. **Log streaming?** `ship logs --follow` with JSON lines. Worth it?
 
-3. **Webhooks?** Notify a URL on deploy success/failure. Useful for CI integration.
+2. **Webhooks?** Notify a URL on deploy success/failure. Useful for CI integration.
 
-4. **Multi-host?** Agents deploying to different VPSes. Current `--host` flag works but could be smoother.
+3. **Multi-host?** Agents deploying to different VPSes. Current `--host` flag works but could be smoother.
 
 ## Success Metrics