agent-canvas 0.1.5 → 0.1.8

package/daemon/tsconfig.json

@@ -0,0 +1,20 @@
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "jsx": "react-jsx",
+    "strict": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "noEmit": true,
+    "rootDir": ".",
+    "types": ["@types/bun"],
+    "paths": {
+      "#canvas/runtime": ["./client/runtime.ts"],
+      "#canvas/components": ["./client/components/index.ts"]
+    }
+  },
+  "include": ["src/**/*", "client/**/*"],
+  "exclude": ["client/compat/**/*"]
+}

package/package.json

@@ -1,28 +1,18 @@
 {
   "name": "agent-canvas",
-  "version": "0.1.5",
+  "version": "0.1.8",
   "description": "Interactive visual canvas for Claude Code — rich annotatable documents in the browser",
   "bin": {
     "agent-canvas": "bin/agent-canvas.js"
   },
-  "files": [
-    "bin/",
-    "daemon/src/",
-    "daemon/client/",
-    "daemon/dist/",
-    "daemon/build.ts",
-    "daemon/package.json",
-    "skills/",
-    "hooks/"
-  ],
-  "scripts": {
+"scripts": {
     "build": "bun daemon/build.ts",
     "typecheck": "tsc --noEmit && tsc --noEmit -p daemon/tsconfig.json",
     "prepublishOnly": "bun daemon/build.ts"
   },
   "dependencies": {
-    "react": "^18.3.1",
-    "react-dom": "^18.3.1"
+    "marked": "^17.0.4",
+    "preact": "^10.25.0"
   },
   "devDependencies": {
     "@tailwindcss/cli": "4",

package/skills/canvas/SKILL.md

@@ -15,18 +15,18 @@ disable-model-invocation: true
 
 Canvas opens a rich, annotatable document in the user's browser. You write JSX, the user reviews and annotates it like Google Docs, and feedback comes back as markdown. Use it whenever structured visual communication beats inline chat.
 
-**Read the flow reference before starting**: Check `flows.md` to pick the right flow for your task. Each flow has a specific sequence of canvases with templates.
+**Read the flow reference before starting**: Check `${CLAUDE_SKILL_DIR}/flows.md` to pick the right flow for your task. Each flow has a specific sequence of canvases with templates.
 
-**Read the component reference as needed**: Check `components.md` for the full component API.
+**Read the component reference as needed**: Check `${CLAUDE_SKILL_DIR}/components.md` for the full component API.
 
 ## Core Mechanics
 
 ### Writing a Canvas
 
-Use the **Write** tool to create a `.jsx` file in `.claude/agent-canvas/`:
+Use the **Write** tool to create a `.jsx` file in `.claude/agent-canvas/${CLAUDE_SESSION_ID}/`:
 
 ```jsx
-// Write to: .claude/agent-canvas/plan.jsx
+// Write to: .claude/agent-canvas/${CLAUDE_SESSION_ID}/plan.jsx
 
 <Section title="Authentication Redesign">
   A proposal to replace session-based auth with JWT tokens.
@@ -50,7 +50,7 @@ Components are auto-available — no imports needed. The file is a JSX fragment
 After writing the file, push it to open the canvas in the browser:
 
 ```bash
-bunx agent-canvas push .claude/agent-canvas/plan.jsx --label "Implementation Plan"
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/plan.jsx --session ${CLAUDE_SESSION_ID} --label "Implementation Plan"
 ```
 
 This opens the canvas in the user's browser (first time) and exits immediately. The round label defaults to the filename if `--label` is omitted. **Always show the `browserUrl` from the push output to the user** so they can open the canvas manually if auto-open didn't work.
@@ -60,46 +60,71 @@ This opens the canvas in the user's browser (first time) and exits immediately.
 After pushing, wait for the user to review and submit:
 
 ```bash
-bunx agent-canvas wait
+bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}
 ```
 
-This **blocks until the user submits feedback**, then prints feedback markdown to stdout. If feedback was already submitted (e.g. retrying after a disconnect), it returns immediately with the existing feedback.
+This **blocks until the user submits feedback**, then prints feedback markdown to stdout. If feedback was already submitted but not yet consumed, it returns immediately with the existing feedback.
 
-> **Note:** If `push` outputs a warning "CANVAS_SESSION_ID not set, using generated ID: ...", you must pass that ID to wait: `bunx agent-canvas wait --session <id>`
+**Timeout handling**: The watch command may time out if the user takes a while to review. If it times out, don't retry automatically — wait for the user to tell you they've submitted feedback, then run the watch command again (or use `fetch`) to retrieve it.
+
+### Checking for feedback without blocking
+
+Use `fetch` to check for feedback without waiting:
+
+```bash
+bunx agent-canvas fetch --session ${CLAUDE_SESSION_ID}
+```
+
+Returns immediately — prints feedback to stdout if available, otherwise produces no output. Use this to retry after a timeout or when the user tells you they've submitted.
 
 ### Iterating
 
 Use the **Edit** tool to modify the existing JSX based on feedback — targeted edits, not full rewrites. Then push and wait again:
 
 ```bash
-bunx agent-canvas push .claude/agent-canvas/plan.jsx --label "Implementation Plan (revised)"
-bunx agent-canvas wait
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/plan.jsx --session ${CLAUDE_SESSION_ID} --label "Implementation Plan (revised)"
+bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}
 ```
 
 Each push creates a new **round** — the user sees previous rounds and their feedback in the UI.
 
+### Responding to feedback
+
+When pushing a revised canvas after receiving user feedback, use `--response` to tell the user how you addressed their feedback. The response renders as a short banner at the top of the canvas.
+
+```bash
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/plan.jsx --session ${CLAUDE_SESSION_ID} --label "Plan (revised)" --response "Incorporated all feedback. Switched to connection pooling as suggested. I kept the sync approach for writes — see the note in Phase 2 for my reasoning."
+```
+
+Use `--response` to:
+- Confirm what you incorporated and how
+- Explain any opposing stance — if you disagree with a suggestion, say why
+- Call out anything you intentionally did NOT change and why
+
+Keep it concise (2-4 sentences). The user can see the diff in the canvas UI, so focus on the "why" not the "what".
+
 ### Multiple Canvases
 
 Maintain separate files for different phases:
 
 ```bash
-bunx agent-canvas push .claude/agent-canvas/discovery.jsx --label "Discovery"
-bunx agent-canvas wait
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/discovery.jsx --session ${CLAUDE_SESSION_ID} --label "Discovery"
+bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}
 # ... process feedback ...
-bunx agent-canvas push .claude/agent-canvas/requirements.jsx --label "Requirements"
-bunx agent-canvas wait
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/requirements.jsx --session ${CLAUDE_SESSION_ID} --label "Requirements"
+bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}
 # ... process feedback ...
-bunx agent-canvas push .claude/agent-canvas/plan.jsx --label "Implementation Plan"
-bunx agent-canvas wait
+bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/plan.jsx --session ${CLAUDE_SESSION_ID} --label "Implementation Plan"
+bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}
 ```
 
 ### File Location
 
-All canvas files go in `.claude/agent-canvas/` within the project root. Add `.claude/agent-canvas/` to `.gitignore` — these are ephemeral working files.
+All canvas files go in `.claude/agent-canvas/${CLAUDE_SESSION_ID}/` within the project root. Add `.claude/agent-canvas/` to `.gitignore` — these are ephemeral working files.
 
 ## Choosing a Flow
 
-Determine which flow fits before starting. See `flows.md` for full details with templates.
+Determine which flow fits before starting. See `${CLAUDE_SKILL_DIR}/flows.md` for full details with templates.
 
 ```
 User wants something built/changed?
@@ -129,10 +154,10 @@ User wants to make a decision?
 
 1. **Determine flow** from user intent
 2. **Announce** briefly: "I'll start with discovery, then create a detailed plan."
-3. **Write canvas JSX** with the Write tool to `.claude/agent-canvas/<name>.jsx`
-4. **Push**: `bunx agent-canvas push .claude/agent-canvas/<name>.jsx --label "<Label>"`
+3. **Write canvas JSX** with the Write tool to `.claude/agent-canvas/${CLAUDE_SESSION_ID}/<name>.jsx`
+4. **Push**: `bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/<name>.jsx --session ${CLAUDE_SESSION_ID} --label "<Label>"`
 5. **Tell the user** the canvas is ready for review (they see it in their browser)
-6. **Wait**: `bunx agent-canvas wait` — this blocks until the user submits feedback
+6. **Wait**: `bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}` — this blocks until the user submits feedback
 7. **Read feedback** — check for annotations, answers, added context files, approval
 8. **Edit with the Edit tool and re-push + wait**, or advance to next phase
 9. **After implementation**, push a summary canvas
@@ -165,7 +190,7 @@ Then interview deeply in each selected area across subsequent rounds. Or ask in
 
 ## Important Rules
 
-- **Write** canvas files to `.claude/agent-canvas/` using the Write tool. Never use bash heredocs or cat.
+- **Write** canvas files to `.claude/agent-canvas/${CLAUDE_SESSION_ID}/` using the Write tool. Never use bash heredocs or cat.
 - **Edit** canvas files using the Edit tool. Never rewrite entire files — make targeted edits.
 - JSX can be a fragment (just tags) or a full module with `export default function Canvas()`.
 - Every `<Item>` and interactive component needs a unique `id`.

package/skills/canvas/components.md

@@ -100,6 +100,37 @@ Inline code block with syntax highlighting. For code that's part of the narrativ
 **Props:**
 - `language` (string) — syntax highlighting language
 
+### `<Markdown>`
+
+Renders markdown content with full GFM support (headings, lists, tables, code blocks, links, etc.). Two modes:
+
+**Inline source** — markdown as children:
+```jsx
+<Markdown>{`
+# Summary
+
+This is **bold** and *italic*. Here's a list:
+
+- First item
+- Second item
+  - Nested item
+
+\`\`\`typescript
+const x = 42;
+\`\`\`
+`}</Markdown>
+```
+
+**File reference** — loads file content at compile time:
+```jsx
+<Markdown file="docs/architecture.md" />
+<Markdown file="CHANGELOG.md" />
+```
+
+**Props:**
+- `file` (string) — path relative to project root. Content is resolved at compile time.
+- Children (string) — inline markdown source. Used when `file` is not specified.
+
 ### `<ImageView src="string">`
 
 Displays an image from the project directory.

package/skills/canvas/flows.md

@@ -2,7 +2,7 @@
 
 Each flow is a sequence of canvas rounds. Phases can be skipped or combined based on context.
 
-**Tooling reminder**: Write all `.jsx` files using the **Write** tool to `.claude/agent-canvas/`. Edit them with the **Edit** tool. Push with `bunx agent-canvas push .claude/agent-canvas/<file>.jsx --label "<Label>"`, then `bunx agent-canvas wait` to block for feedback. The JSX blocks below show what to write — they are the file content, not bash commands.
+**Tooling reminder**: Write all `.jsx` files using the **Write** tool to `.claude/agent-canvas/${CLAUDE_SESSION_ID}/`. Edit them with the **Edit** tool. Push with `bunx agent-canvas push .claude/agent-canvas/${CLAUDE_SESSION_ID}/<file>.jsx --session ${CLAUDE_SESSION_ID} --label "<Label>"`, then `bunx agent-canvas watch --session ${CLAUDE_SESSION_ID}` to block for feedback. The JSX blocks below show what to write — they are the file content, not bash commands.
 
 ---
 
@@ -16,7 +16,7 @@ Each flow is a sequence of canvas rounds. Phases can be skipped or combined base
 
 Goal: understand scope, constraints, and user expectations. Start broad, go deep.
 
-Write to `.claude/agent-canvas/discovery.jsx`, then push and wait:
+Write to `.claude/agent-canvas/${CLAUDE_SESSION_ID}/discovery.jsx`, then push and wait:
 
 ```jsx
 <Section title="Discovery: [Feature Name]">

package/tsconfig.json

@@ -0,0 +1,14 @@
+{
+  "compilerOptions": {
+    "target": "ESNext",
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "strict": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true,
+    "allowImportingTsExtensions": true,
+    "noEmit": true,
+    "types": ["@types/bun"]
+  },
+  "include": ["bin/**/*"]
+}

package/daemon/dist/jsx-dev-runtime-shim.js

@@ -1,17 +0,0 @@
-
-const R = window.React;
-export const Fragment = R.Fragment;
-function _jsx(type, props, key) {
-  if (props && 'children' in props) {
-    const { children, ...rest } = props;
-    if (key !== undefined && key !== null) rest.key = key;
-    return Array.isArray(children)
-      ? R.createElement(type, rest, ...children)
-      : R.createElement(type, rest, children);
-  }
-  if (key !== undefined && key !== null) props = { ...props, key };
-  return R.createElement(type, props);
-}
-export const jsx = _jsx;
-export const jsxs = _jsx;
-export function jsxDEV(type, props, key) { return _jsx(type, props, key); }

package/daemon/dist/jsx-runtime-shim.js

@@ -1,17 +0,0 @@
-
-const R = window.React;
-export const Fragment = R.Fragment;
-function _jsx(type, props, key) {
-  if (props && 'children' in props) {
-    const { children, ...rest } = props;
-    if (key !== undefined && key !== null) rest.key = key;
-    return Array.isArray(children)
-      ? R.createElement(type, rest, ...children)
-      : R.createElement(type, rest, children);
-  }
-  if (key !== undefined && key !== null) props = { ...props, key };
-  return R.createElement(type, props);
-}
-export const jsx = _jsx;
-export const jsxs = _jsx;
-export function jsxDEV(type, props, key) { return _jsx(type, props, key); }

package/daemon/dist/react-dom-client-shim.js

@@ -1,4 +0,0 @@
-
-const RD = window.ReactDOM;
-export const { createRoot, hydrateRoot } = RD;
-export default { createRoot: RD.createRoot, hydrateRoot: RD.hydrateRoot };

package/daemon/dist/react-dom-shim.js

@@ -1,4 +0,0 @@
-
-const RD = window.ReactDOM;
-export default RD;
-export const { createPortal, flushSync, hydrate, render, unmountComponentAtNode, findDOMNode, unstable_batchedUpdates } = RD;

package/daemon/dist/react-shim.js

@@ -1,4 +0,0 @@
-
-const R = window.React;
-export default R;
-export const { useState, useEffect, useRef, useCallback, useContext, useMemo, useReducer, createContext, createElement, Fragment, Children, cloneElement, isValidElement, memo, forwardRef, lazy, Suspense, startTransition, useTransition, useDeferredValue, useId, useSyncExternalStore, useInsertionEffect, useImperativeHandle, useLayoutEffect, useDebugValue, Component, PureComponent } = R;