patchwork-os 0.2.0-beta.8.canary.74 → 0.2.0-beta.8.canary.76

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchwork-os",
-  "version": "0.2.0-beta.8.canary.74",
+  "version": "0.2.0-beta.8.canary.76",
   "description": "Your personal AI runtime, local-first. Patchwork OS gives any AI model a consistent set of tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all on your machine, all under your policy.",
   "type": "module",
   "main": "dist/index.js",

package/templates/recipes/morning-brief.yaml

@@ -61,8 +61,11 @@ steps:
         6. **Linear** — list in-progress and unstarted issues by priority; omit this section entirely if the list is empty or returned an error
 
         Be concise. Skip newsletters and automated notifications.
-      # Use claude (not gemini) — Gemini free tier hits daily quota mid-recipe
-      driver: claude
+      # Use the claude-code driver (subprocess `claude -p`) — runs under
+      # your existing Claude Code subscription, no ANTHROPIC_API_KEY
+      # required. Switch to `driver: claude` only if you have an API key
+      # set and want the Anthropic API path (different billing).
+      driver: claude-code
       into: brief
   - tool: file.write
     path: ~/.patchwork/inbox/morning-brief-{{date}}.md

package/templates/recipes/project-health-check.yaml

@@ -38,7 +38,10 @@ steps:
         2. **Issues** — issues needing attention today; omit if empty
         3. **PRs** — PRs waiting on review or action; omit if empty
         4. **Health** — one-sentence overall assessment (on track / needs attention / blocked)
-      driver: claude
+      # Use the claude-code driver (subprocess `claude -p`) — runs under
+      # your existing Claude Code subscription. Switch to `driver: claude`
+      # only if you have ANTHROPIC_API_KEY set and prefer the API path.
+      driver: claude-code
     awaits: [gather]
   - id: write
     tool: file.write

package/templates/recipes/webhook/customer-escalation.yaml

@@ -25,22 +25,21 @@ trigger:
   path: /customer-escalation
 
 steps:
-  - tool: hubspot.find_contact
-    email: "{{payload.customer_email}}"
+  # Look the contact up by email. HubSpot's search API accepts a free-form
+  # query string (matches name / email / company) — the email itself is a
+  # specific enough literal that we get a one-row hit when the email is on
+  # file. If you need stricter matching, post-filter in the agent step.
+  - tool: hubspot.searchContacts
+    query: "{{payload.customer_email}}"
     into: contact
-  - tool: hubspot.list_recent_deals
-    contact_id: "{{contact.id}}"
-    max: 3
-    into: deals
   - agent:
       prompt: |
         Compose a Slack alert for the customer-success team. Keep it under
         12 lines. Include: customer name + company, tier (from contact.tier
-        if present), recent deal context, what they said, and the ticket
-        link. End with a single suggested first move.
+        if present), what they said, and the ticket link. End with a single
+        suggested first move.
 
         Contact: {{contact}}
-        Deals:   {{deals}}
         Summary: {{payload.summary}}
         Ticket:  {{payload.ticket_url}}
       into: alert

package/templates/recipes/webhook/meeting-prep.yaml

@@ -19,13 +19,18 @@ trigger:
   path: /meeting-prep
 
 steps:
-  - tool: gmail.search_threads
+  - tool: gmail.search
     query: "from:({{payload.attendees}}) newer_than:7d"
     max: 10
     into: recent_threads
-  - tool: linear.search_issues
-    query: "{{payload.topic}}"
-    max: 5
+  # linear.list_issues filters by assignee / team / state — there is no
+  # free-text topic search in the connector. We pull the user's own
+  # started/unstarted issues and let the agent correlate them to the
+  # meeting topic. Lossier than a real search, but useful + works
+  # without a Linear MCP setup.
+  - tool: linear.list_issues
+    state: "started,unstarted"
+    max: 10
     into: related_issues
   - agent:
       prompt: |
@@ -34,7 +39,8 @@ steps:
         Topic: {{payload.topic}}
         Attendees: {{payload.attendees}}
         Recent email threads with attendees: {{recent_threads}}
-        Related Linear issues: {{related_issues}}
+        My in-flight Linear issues: {{related_issues}}
+        — only mention issues that look related to the topic above.
 
         Output sections: Context, Open questions, Suggested first move.
       into: brief