Now I have content for three new wiki pages. Let me also check the `cwc-long-running-agents` one — I see there's a "Long-Running Agent Primitives.md" already in the tools directory. Let me check that.

Actually let me check if we already have a page for cwc-long-running-agents before writing a new one.


1	# Long-Running Agent Primitives
2
3	**Type:** Engineering patterns / reusable building blocks
4	**By:** Anthropic
5	**Repo:** https://github.com/anthropics/cwc-long-running-agents
6	**Use:** Copy `.claude/` directory or cherry-pick individual files
7
8	## What it is
9	Reusable primitives for Claude agents that run for extended periods without human supervision. Based on Anthropic's own engineering patterns. Solves the specific failure modes that emerge when agents work autonomously over hours or days.
10
11	## The 3 core primitives
12
13	### 1. Default-FAIL contract
14	Features start in a failing state; the agent must open evidence files to mark them complete. Prevents false positives — if the agent stops mid-run, nothing is silently marked done.
15
16	### 2. Fresh-context evaluator
17	A separate agent instance independently grades the primary agent's work. Avoids the primary agent convincing itself its own output is correct.
18
19	### 3. Agent-maintained handoff (`PROGRESS.md` + git commits)
20	The agent tracks its own progress in a `PROGRESS.md` file and commits to git at checkpoints. If the agent is interrupted, a new instance can resume from the last commit without losing context.
21
22	## The 2 operator-control hooks
23
24	### Kill switch
25	Drop an `AGENT_STOP` file to halt the agent at the next checkpoint. Clean, no-force-kill needed.
26
27	### Steering (`STEER.md`)
28	Drop a `STEER.md` file mid-run to redirect the agent without stopping it. The agent reads it and adjusts course.
29
30	## Usage
31
32	### Built-in `/goal` (no primitives needed)
33	```bash
34	/goal every feature in PROGRESS.md is implemented, committed, and its tests pass
35	```
36	After every turn, a separate fast model checks the condition and keeps the session running until it's met. Works in interactive Claude Code, `claude -p` (headless), and Remote Control.
37
38	### Custom harness (use the primitives)
39	```bash
40	# Copy the whole .claude/ structure into your project
41	cp -r .claude/ /your/project/
42	chmod +x /your/project/.claude/hooks/*.sh
43
44	# Headless loop example
45	while grep -q '"passes": false' test-results.json; do
46	  claude -p "Read PROGRESS.md and build the next unfinished feature."
47	  VERDICT=$(claude --agent evaluator -p "Review the most recent commit against its spec.")
48	done
49	```
50
51	Includes a bash wrapper for headless (no-terminal) operation.
52
53	## Monitoring a live run (no dashboard needed)
54
55	```bash
56	watch -n 2 'tail -20 PROGRESS.md'            # agent's own notes
57	watch -n 5 'git log --oneline -8'             # work saved
58	watch -n 5 'find screenshots -name "*.png" | tail -5'  # what it sees
59	watch -n 2 'wc -l < .claude/.evidence-reads 2>/dev/null'  # evidence reads
60	```
61
62	## Going further (advanced patterns)
63
64	| Pattern | What it adds |
65	|---------|-------------|
66	| **Unattended loop** | Outer script caps session length, starts next one automatically. `ralph-loop` plugin in `claude-plugins-official`. |
67	| **Planner agent** | First session expands a one-line ask into a `BUILD_PLAN.md` the loop runs against |
68	| **Grading rubrics** | Evaluator uses scoring principles (functionality, design, craft) with few-shot examples instead of binary pass/fail. `frontend-design` plugin. |
69	| **Browser-verified evaluator** | Evaluator opens the running app itself via Playwright MCP instead of trusting screenshots |
70	| **Re-simplify on upgrades** | After each model release, comment out harness pieces one at a time to see what's still load-bearing |
71	| **Hosted runtime** | Claude Managed Agents hosts the loop, sandbox, and scheduling |
72
73	## Source engineering posts
74
75	- [Effective Harnesses for Long-Running Agents](https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents) — Nov 2025
76	- [Harness Design for Long-Running Application Development](https://www.anthropic.com/engineering/harness-design-long-running-apps) — Mar 2026
77
78	## Why it matters
79	Addresses the "runaway agent" and "silent failure" problems that are the main operational risks of autonomous agents in production. The kill switch and steering hook are especially relevant for agentic systems that need human override without code changes.
80
81	## Applicability
82	- **nanoclaw** — kill switch and steering patterns are directly applicable to long-running NanoClaw agents
83	- **congressional-trading** — autonomous monitoring agent that runs for days; PROGRESS.md handoff + kill switch fit this use case
84	- **qip-qien** — agents handling tickets over extended periods benefit from the Default-FAIL contract and fresh-context evaluator
85
86	## Related
87	- [[Claude Agent SDK Demos]]
88	- [[Claude Agent SDK TypeScript]]
89	- [[Claude Code]]
90	- [[Claude Plugins Official]] — `ralph-loop` and `frontend-design` plugins referenced here
91

# Long-Running Agent Primitives

**Type:** Engineering patterns / reusable building blocks
**By:** Anthropic
**Repo:** https://github.com/anthropics/cwc-long-running-agents
**Use:** Copy `.claude/` directory or cherry-pick individual files

## What it is
Reusable primitives for Claude agents that run for extended periods without human supervision. Based on Anthropic's own engineering patterns. Solves the specific failure modes that emerge when agents work autonomously over hours or days.

## The 3 core primitives

### 1. Default-FAIL contract
Features start in a failing state; the agent must open evidence files to mark them complete. Prevents false positives — if the agent stops mid-run, nothing is silently marked done.

### 2. Fresh-context evaluator
A separate agent instance independently grades the primary agent's work. Avoids the primary agent convincing itself its own output is correct.

### 3. Agent-maintained handoff (`PROGRESS.md` + git commits)
The agent tracks its own progress in a `PROGRESS.md` file and commits to git at checkpoints. If the agent is interrupted, a new instance can resume from the last commit without losing context.

## The 2 operator-control hooks

### Kill switch
Drop an `AGENT_STOP` file to halt the agent at the next checkpoint. Clean, no-force-kill needed.

### Steering (`STEER.md`)
Drop a `STEER.md` file mid-run to redirect the agent without stopping it. The agent reads it and adjusts course.

## Usage

### Built-in `/goal` (no primitives needed)
```bash
/goal every feature in PROGRESS.md is implemented, committed, and its tests pass
```
After every turn, a separate fast model checks the condition and keeps the session running until it's met. Works in interactive Claude Code, `claude -p` (headless), and Remote Control.

### Custom harness (use the primitives)
```bash
# Copy the whole .claude/ structure into your project
cp -r .claude/ /your/project/
chmod +x /your/project/.claude/hooks/*.sh

# Headless loop example
while grep -q '"passes": false' test-results.json; do
  claude -p "Read PROGRESS.md and build the next unfinished feature."
  VERDICT=$(claude --agent evaluator -p "Review the most recent commit against its spec.")
done
```

Includes a bash wrapper for headless (no-terminal) operation.

## Monitoring a live run (no dashboard needed)

```bash
watch -n 2 'tail -20 PROGRESS.md'            # agent's own notes
watch -n 5 'git log --oneline -8'             # work saved
watch -n 5 'find screenshots -name "*.png" | tail -5'  # what it sees
watch -n 2 'wc -l < .claude/.evidence-reads 2>/dev/null'  # evidence reads
```

## Going further (advanced patterns)

| Pattern | What it adds |
|---------|-------------|
| **Unattended loop** | Outer script caps session length, starts next one automatically. `ralph-loop` plugin in `claude-plugins-official`. |
| **Planner agent** | First session expands a one-line ask into a `BUILD_PLAN.md` the loop runs against |
| **Grading rubrics** | Evaluator uses scoring principles (functionality, design, craft) with few-shot examples instead of binary pass/fail. `frontend-design` plugin. |
| **Browser-verified evaluator** | Evaluator opens the running app itself via Playwright MCP instead of trusting screenshots |
| **Re-simplify on upgrades** | After each model release, comment out harness pieces one at a time to see what's still load-bearing |
| **Hosted runtime** | Claude Managed Agents hosts the loop, sandbox, and scheduling |

## Source engineering posts

- [Effective Harnesses for Long-Running Agents](https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents) — Nov 2025
- [Harness Design for Long-Running Application Development](https://www.anthropic.com/engineering/harness-design-long-running-apps) — Mar 2026

## Why it matters
Addresses the "runaway agent" and "silent failure" problems that are the main operational risks of autonomous agents in production. The kill switch and steering hook are especially relevant for agentic systems that need human override without code changes.

## Applicability
- **nanoclaw** — kill switch and steering patterns are directly applicable to long-running NanoClaw agents
- **congressional-trading** — autonomous monitoring agent that runs for days; PROGRESS.md handoff + kill switch fit this use case
- **qip-qien** — agents handling tickets over extended periods benefit from the Default-FAIL contract and fresh-context evaluator

## Related
- [[Claude Agent SDK Demos]]
- [[Claude Agent SDK TypeScript]]
- [[Claude Code]]
- [[Claude Plugins Official]] — `ralph-loop` and `frontend-design` plugins referenced here


1	# Ingest Log
2
3	Chronological record of everything added to this wiki.
4
5	---
6
7	## 2026-07-06
8
9	- **[[Claude Blog - Field Guide to Claude Fable]]** (new source) — July 6. Thariq Shihipar. Practical field guide for working with Claude Fable: the 4-quadrant unknowns model (Known/Unknown × Knowns/Unknowns) and 8 elicitation techniques (blind spot pass, interview mode, reference-based prompting, implementation plan, explainer artifact, quiz mode). Core claim: output quality is now bottlenecked by user clarity, not model capability. Worked example: end-to-end video editing.
10	- **[[Finding Your Unknowns Framework]]** (new concept) — Distilled from the field guide. Pre-flight protocol for agentic work. Includes applicability notes for qip-qien (build blind spot pass into triage prompt), TradingBot25 (interview before new strategy sessions), and congressional-trading (reference-based scoring examples).
11	- **[[Claude Fable 5 and Mythos 5]]** (updated) — Added "Practical usage guidance" section linking to the field guide and the unknowns framework.
12
13	- **[[CLAUDE.md Progressive Disclosure]]** (new concept, internal-origin) — Method from the root CLAUDE.md audit: measure per-section token cost, classify sections by *when needed* (always-relevant stays inline compressed; situational moves to `.claude/docs/` behind trigger-phrased pointers), add a size-budget guardrail against regrowth. First application: 16.3KB → ~9KB, zero facts lost.
14	- **[[X - EXM7777 - Do This On Your Last Day With Fable]]** (new source) — X Article by @EXM7777 (Machina). Tactical playbook for extracting durable artifacts from a frontier model before it moves to pay-per-token. Five moves: workspace standards, consultant audit, second brain run, `/goal` + dynamic workflows, extract-approach skill.
15	- **[[Frontier Model Extraction Strategy]]** (new concept) — The underlying pattern: frontier judgment required to *create*, ordinary intelligence sufficient to *use*. The irreversibility filter test: "Can a cheaper model redo this tomorrow?"
16	- **CLAUDE.md: Learning Law** (root instruction, internal-origin) — Formalized the extract-approach idea from the EXM7777 article as a standing rule, routed through the second brain instead of a new skill: after every non-trivial solved problem, write an atomized `wiki/concepts/` note (approach, why it worked, when to reuse). Mechanics added to `second-brain/SCHEMA.md` → "Internal learning capture."
17	- **[[Question-Led Selling Arc]]** (updated concept) — Added a stage-2 profiling block (how they heard about us, role, prior tool, what they're building) answered via buttons, kept distinct from the arc's own-words questions. Generalized as a cross-project pattern in root CLAUDE.md for any solution-selling / end-user-facing site.
18
19	## 2026-07-03 (AgenticLever discovery flow)
20	- **[[Question-Led Selling Arc]]** (new concept) — Synthesis of SPIN / Sandler / NEPQ / Oren Klaff / Chris Do into a four-step ask-don't-pitch arc (problem → change → cost → worth). Deployed as the stage-2 discovery form on the AgenticLever landing page; full playbook in `projects/AgenticLever/docs/discovery-playbook.md`.
21
22	## 2026-06-13 (Anthropic GitHub sweep #22)
23	- **[[Claude Fable 5 and Mythos 5]]** (updated) — Added full classifier fallback API reference: `stop_details.category` values (cyber/bio/reasoning_extraction), server-side fallback via `fallbacks` param + `anthropic-beta: server-side-fallback-2026-06-01`, billing change for client-side fallback (`fallback_credit_token` → cache-read rate), `recommended_model` field. Source: new `fable_5_fallback_billing/guide.ipynb` in claude-cookbooks.
24	- **[[Claude Cookbooks]]** (updated) — Added three new notable additions: Fable 5 fallback/billing guide, Sentry triage scheduled Managed Agent (vault credentials, cron, `sentry-cli`), async multi-agent orchestration patterns.
25	- **[[Claude for Healthcare]]** (updated) — Added missing ICD-10 Codes MCP server to the remote MCP table.
26	- Skipped: anthropic-tools (deprecated alpha SDK), all SDKs (changelog bumps), coursework repos, infra libs (riegeli-rs).
27
28	## 2026-06-12 (Anthropic GitHub sweep #21)
29	- **Nothing new.** 30 repos updated — all maintenance: automated SHA bumps, version increments, changelog updates. All relevant repos already ingested in prior sweeps.
30

# Ingest Log

Chronological record of everything added to this wiki.

---

## 2026-07-06

- **[[Claude Blog - Field Guide to Claude Fable]]** (new source) — July 6. Thariq Shihipar. Practical field guide for working with Claude Fable: the 4-quadrant unknowns model (Known/Unknown × Knowns/Unknowns) and 8 elicitation techniques (blind spot pass, interview mode, reference-based prompting, implementation plan, explainer artifact, quiz mode). Core claim: output quality is now bottlenecked by user clarity, not model capability. Worked example: end-to-end video editing.
- **[[Finding Your Unknowns Framework]]** (new concept) — Distilled from the field guide. Pre-flight protocol for agentic work. Includes applicability notes for qip-qien (build blind spot pass into triage prompt), TradingBot25 (interview before new strategy sessions), and congressional-trading (reference-based scoring examples).
- **[[Claude Fable 5 and Mythos 5]]** (updated) — Added "Practical usage guidance" section linking to the field guide and the unknowns framework.

- **[[CLAUDE.md Progressive Disclosure]]** (new concept, internal-origin) — Method from the root CLAUDE.md audit: measure per-section token cost, classify sections by *when needed* (always-relevant stays inline compressed; situational moves to `.claude/docs/` behind trigger-phrased pointers), add a size-budget guardrail against regrowth. First application: 16.3KB → ~9KB, zero facts lost.
- **[[X - EXM7777 - Do This On Your Last Day With Fable]]** (new source) — X Article by @EXM7777 (Machina). Tactical playbook for extracting durable artifacts from a frontier model before it moves to pay-per-token. Five moves: workspace standards, consultant audit, second brain run, `/goal` + dynamic workflows, extract-approach skill.
- **[[Frontier Model Extraction Strategy]]** (new concept) — The underlying pattern: frontier judgment required to *create*, ordinary intelligence sufficient to *use*. The irreversibility filter test: "Can a cheaper model redo this tomorrow?"
- **CLAUDE.md: Learning Law** (root instruction, internal-origin) — Formalized the extract-approach idea from the EXM7777 article as a standing rule, routed through the second brain instead of a new skill: after every non-trivial solved problem, write an atomized `wiki/concepts/` note (approach, why it worked, when to reuse). Mechanics added to `second-brain/SCHEMA.md` → "Internal learning capture."
- **[[Question-Led Selling Arc]]** (updated concept) — Added a stage-2 profiling block (how they heard about us, role, prior tool, what they're building) answered via buttons, kept distinct from the arc's own-words questions. Generalized as a cross-project pattern in root CLAUDE.md for any solution-selling / end-user-facing site.

## 2026-07-03 (AgenticLever discovery flow)
- **[[Question-Led Selling Arc]]** (new concept) — Synthesis of SPIN / Sandler / NEPQ / Oren Klaff / Chris Do into a four-step ask-don't-pitch arc (problem → change → cost → worth). Deployed as the stage-2 discovery form on the AgenticLever landing page; full playbook in `projects/AgenticLever/docs/discovery-playbook.md`.

## 2026-06-13 (Anthropic GitHub sweep #22)
- **[[Claude Fable 5 and Mythos 5]]** (updated) — Added full classifier fallback API reference: `stop_details.category` values (cyber/bio/reasoning_extraction), server-side fallback via `fallbacks` param + `anthropic-beta: server-side-fallback-2026-06-01`, billing change for client-side fallback (`fallback_credit_token` → cache-read rate), `recommended_model` field. Source: new `fable_5_fallback_billing/guide.ipynb` in claude-cookbooks.
- **[[Claude Cookbooks]]** (updated) — Added three new notable additions: Fable 5 fallback/billing guide, Sentry triage scheduled Managed Agent (vault credentials, cron, `sentry-cli`), async multi-agent orchestration patterns.
- **[[Claude for Healthcare]]** (updated) — Added missing ICD-10 Codes MCP server to the remote MCP table.
- Skipped: anthropic-tools (deprecated alpha SDK), all SDKs (changelog bumps), coursework repos, infra libs (riegeli-rs).

## 2026-06-12 (Anthropic GitHub sweep #21)
- **Nothing new.** 30 repos updated — all maintenance: automated SHA bumps, version increments, changelog updates. All relevant repos already ingested in prior sweeps.


Expand Roadsense to new areas and plan public launch


The Long-Running Agent Primitives page is already comprehensive.

Now I need to:
1. Create a new wiki page for `launch-your-agent` (genuinely new, no page exists)
2. Create a new wiki page for `claude-tag-plugins` (doesn't exist - I see no page for it)
3. Update the ingest log
4. Update the wiki index (Home.md or index.md)
5. Message James

Let me also check the Home.md to see what structure I need to update.

Actually, let me also check if there's a tools index.md or if the wiki Home.md lists things.


1	# Wiki Index
2
3	A catalog of everything in this knowledge base. Updated by Nano on every ingest.
4
5	## Tools & Software
6	*Guest-endorsed or actively used — not sponsors.*
7	- [[Agent Browser]] — Vercel Labs Rust CLI for AI-driven browser automation. Credential vault, accessibility-tree refs, React introspection, HAR recording.
8	- [[Devin]] — AI coding agent by Cognition. 15-thread code factory model.
9	- [[OpenClaw]] — Open-source AI executive assistant / chief of staff.
10	- [[ClawChief]] — Ryan Carson's open-sourced OpenClaw chief-of-staff config.
11	- [[Claude Code]] — Anthropic's coding agent. Ryan Carson's preferred coding tool.
12	- [[Codex]] — OpenAI's coding agent / browser testing tool.
13	- [[Sentry]] — Error monitoring. Used with Devin for automated bug triage.
14	- [[Tailscale]] — WireGuard mesh network. Used for remote access to Mac Mini services from phone. Includes full recipe for exposing any local port via `tailscale serve` + launchd.
15	- [[Figma]] — Design/wireframing. Visual context layer in Ravi Mehta's system.
16	- [[AgentsView]] — Agent token/cost accounting tool. Useful when new frontier-model pricing appears before dashboards and pricing databases catch up.
17	- [[Teach Skill]] — `/teach` by Matt Pocock. ZPD-based personalized tutor with persistent learning records. Trigger-based (no idle context cost). Claude Code only. Install: `npx skills add mattpocock/skills --skill teach`.
18
19	## Anthropic Official Repos & Resources
20	*Official Anthropic repositories — tools, SDKs, plugins, and reference implementations.*
21	- [[Anthropic Skills Repo]] — Reference implementations of the Claude Agent Skills system. Template for building custom skills.
22	- [[Claude Plugins Official]] — Anthropic's curated plugin marketplace for Claude Code. Install via `/plugin install`.
23	- [[Ralph Loop Plugin]] — Stop-hook-based autonomous iteration loop. Feeds Claude the same prompt until it outputs a completion promise. For well-defined tasks with clear success criteria and automatic verification.
24	- [[Hookify Plugin]] — Create Claude Code hooks from natural language. `/hookify warn me when I use rm -rf` → working hook instantly. No hooks.json editing required.
25	- [[Knowledge Work Plugins]] — 18 open-source role-specific plugins (sales, legal, finance, design, engineering, HR, ops, etc.) built on Claude Agent SDK.
26	- [[Claude for Legal]] — Deep legal workflow plugin suite (transactional + litigation + learning). Integrates with Westlaw, CourtListener.
27	- [[Claude for Life Sciences]] — Research marketplace: PubMed, BioRender, Synapse, Consensus + RNA-seq/Nextflow skills.
28	- [[Claude for Healthcare]] — Healthcare marketplace: FHIR developer, prior-auth review, clinical trial protocols + CMS/NPI servers.
29	- [[Claude for Financial Services]] — 10 named agents (Pitch Agent, GL Reconciler, Market Researcher, KYC Screener, etc.) + 9 vertical skill bundles (IB, ER, PE, WM, fund admin). Deployable as Cowork plugins or Managed Agent templates.
30	- [[Managed Agents]] — Anthropic's hosted agent orchestration platform. Self-hosted sandbox option (tool execution on your infra via outbound-polling worker), mid-session tool/MCP updates, large MCP output auto-offload. Scheduled deployments (cron, no custom infra). Env vars in vaults (credentials injected at network boundary). Opus 4.8 tool-description guidance included.
31	- [[Claude Agent SDK Demos]] — 8 local demo apps showcasing Claude Agent SDK patterns (multi-agent, streaming, email, docs).
32	- [[Claude Agent SDK TypeScript]] — `npm install @anthropic-ai/claude-agent-sdk`. Node.js 18+. Renamed from Claude Code SDK.
33	- [[Claude Agent SDK Python]] — `pip install claude-agent-sdk`. Python 3.10+. In-process MCP servers, hooks as Python functions, CLI bundled in wheel.
34	- [[Claude Cookbooks]] — Copy-paste code recipes and notebooks for Claude API (RAG, tool use, multimodal, agents).
35	- [[Claude Quickstarts]] — Production-ready starter projects: customer support, computer use, browser automation, coding agent.
36	- [[Anthropic Courses]] — 5-course official curriculum: API fundamentals → prompt engineering → real-world prompting → evals → tool use. Jupyter notebooks.
37	- [[Anthropic Prompt Engineering Tutorial]] — 9-chapter interactive prompt engineering course with exercise playgrounds. Available direct API and Amazon Bedrock variants.
38	- [[Claude Code Action]] — GitHub Action that brings Claude into PR review and CI/CD workflows.
39	- [[Defending Code Reference Harness]] — Reference impl for autonomous vuln discovery + human-reviewed patching. gVisor-sandboxed agents. Not actively maintained; Claude Security is the hosted version.
40	- [[Scone Bench]] — 417-task benchmark for evaluating LLM agents on smart-contract vuln discovery/exploitation. Historical DeFi incidents, MCP-based, Docker-sandboxed. From Anthropic Red Team.
41	- [[Claudes C Compiler]] — Claude Opus 4.6 wrote a dependency-free C compiler in Rust from scratch. Compiles PostgreSQL, SQLite, Linux kernel, FFmpeg. Capability showcase, not production-validated.
42	- [[Anthropic Performance Take-Home]] — Open version of Anthropic's original performance engineering take-home. Optimize a VLIW SIMD kernel; Claude Opus 4.5 scored 1,363 cycles vs 147,734 baseline (108× improvement).
43	- [[Claude Code Security Review]] — GitHub Action that auto-scans PRs for security vulnerabilities using Claude.
44	- [[Claude Desktop Buddy]] — ESP32 desk pet + Bluetooth API reference for makers integrating with Claude Desktop.
45	- [[HTML Effectiveness Examples]] — Anthropic's reference collection of single-file HTML artifacts (slide decks, dashboards, editing UIs, diagrams).
46	- [[Claude Code Setup Plugin]] — Official Anthropic plugin that scans your codebase and recommends tailored hooks, skills, MCP servers, subagents, and plugins. Read-only, 1-2 recs per category.
47	- [[Claude Code Monitoring Guide]] — Prometheus + OpenTelemetry toolkit for tracking Claude Code ROI, token spend, and team adoption.
48	- [[GitHub MCP Server]] — GitHub's official MCP server.
49	- [[PineForge MCP]] — Hosted MCP server for real Pine Script v6 backtests. `claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcp`. No key/signup. 245/246 TradingView parity, 100 backtests/week, 13mo Binance data. Docker route for unlimited/custom data. 60+ tools: repos, issues, PRs, code search, security scanning.
50	- [[Devcontainer Features]] — One-line devcontainer.json feature that installs Claude Code CLI in any dev container.
51	- [[Claude Code Routines]] — Scheduled/triggered cloud automation. Runs on Anthropic infrastructure, not your machine. `/schedule` command, API + GitHub + time triggers. Research preview.
52	- [[Long-Running Agent Primitives]] — 3 core primitives (Default-FAIL, Fresh-context evaluator, Handoff) + 2 operator hooks (kill switch, STEER.md). From Anthropic's own patterns.
53	- [[Claude Plugins Community]] — Community plugin marketplace (security-reviewed). Submit at clau.de/plugin-directory-submission.
54	- [[Anthropic CLI]] — `ant` CLI for the Claude Developer Platform API. `brew install anthropics/tap/ant`.
55	- [[Anthropic CWC Workshops]] — 8 Code-with-Claude workshop curricula: Managed Agents, memory primitives (Dreaming Service), eval-driven dev, multi-agent decomposition, Deal Desk reference impl.
56	- [[Agent SDK Workshop]] — Hands-on workshop for Claude Agent SDK: 4-stage guided demo (chat → tools → subagents → memory) + breakout scenarios. Python 3.10+, flip switches in config.py.
57	- [[Long-Horizon Coding Agent Demo]] — Archived AWS re:Invent 2025 demo. GitHub issue → agent builds full-stack app → CloudFront preview → human approval gate. Bedrock AgentCore + Claude Agent SDK.
58	- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
59	- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.
60

# Wiki Index

A catalog of everything in this knowledge base. Updated by Nano on every ingest.

## Tools & Software
*Guest-endorsed or actively used — not sponsors.*
- [[Agent Browser]] — Vercel Labs Rust CLI for AI-driven browser automation. Credential vault, accessibility-tree refs, React introspection, HAR recording.
- [[Devin]] — AI coding agent by Cognition. 15-thread code factory model.
- [[OpenClaw]] — Open-source AI executive assistant / chief of staff.
- [[ClawChief]] — Ryan Carson's open-sourced OpenClaw chief-of-staff config.
- [[Claude Code]] — Anthropic's coding agent. Ryan Carson's preferred coding tool.
- [[Codex]] — OpenAI's coding agent / browser testing tool.
- [[Sentry]] — Error monitoring. Used with Devin for automated bug triage.
- [[Tailscale]] — WireGuard mesh network. Used for remote access to Mac Mini services from phone. Includes full recipe for exposing any local port via `tailscale serve` + launchd.
- [[Figma]] — Design/wireframing. Visual context layer in Ravi Mehta's system.
- [[AgentsView]] — Agent token/cost accounting tool. Useful when new frontier-model pricing appears before dashboards and pricing databases catch up.
- [[Teach Skill]] — `/teach` by Matt Pocock. ZPD-based personalized tutor with persistent learning records. Trigger-based (no idle context cost). Claude Code only. Install: `npx skills add mattpocock/skills --skill teach`.

## Anthropic Official Repos & Resources
*Official Anthropic repositories — tools, SDKs, plugins, and reference implementations.*
- [[Anthropic Skills Repo]] — Reference implementations of the Claude Agent Skills system. Template for building custom skills.
- [[Claude Plugins Official]] — Anthropic's curated plugin marketplace for Claude Code. Install via `/plugin install`.
- [[Ralph Loop Plugin]] — Stop-hook-based autonomous iteration loop. Feeds Claude the same prompt until it outputs a completion promise. For well-defined tasks with clear success criteria and automatic verification.
- [[Hookify Plugin]] — Create Claude Code hooks from natural language. `/hookify warn me when I use rm -rf` → working hook instantly. No hooks.json editing required.
- [[Knowledge Work Plugins]] — 18 open-source role-specific plugins (sales, legal, finance, design, engineering, HR, ops, etc.) built on Claude Agent SDK.
- [[Claude for Legal]] — Deep legal workflow plugin suite (transactional + litigation + learning). Integrates with Westlaw, CourtListener.
- [[Claude for Life Sciences]] — Research marketplace: PubMed, BioRender, Synapse, Consensus + RNA-seq/Nextflow skills.
- [[Claude for Healthcare]] — Healthcare marketplace: FHIR developer, prior-auth review, clinical trial protocols + CMS/NPI servers.
- [[Claude for Financial Services]] — 10 named agents (Pitch Agent, GL Reconciler, Market Researcher, KYC Screener, etc.) + 9 vertical skill bundles (IB, ER, PE, WM, fund admin). Deployable as Cowork plugins or Managed Agent templates.
- [[Managed Agents]] — Anthropic's hosted agent orchestration platform. Self-hosted sandbox option (tool execution on your infra via outbound-polling worker), mid-session tool/MCP updates, large MCP output auto-offload. Scheduled deployments (cron, no custom infra). Env vars in vaults (credentials injected at network boundary). Opus 4.8 tool-description guidance included.
- [[Claude Agent SDK Demos]] — 8 local demo apps showcasing Claude Agent SDK patterns (multi-agent, streaming, email, docs).
- [[Claude Agent SDK TypeScript]] — `npm install @anthropic-ai/claude-agent-sdk`. Node.js 18+. Renamed from Claude Code SDK.
- [[Claude Agent SDK Python]] — `pip install claude-agent-sdk`. Python 3.10+. In-process MCP servers, hooks as Python functions, CLI bundled in wheel.
- [[Claude Cookbooks]] — Copy-paste code recipes and notebooks for Claude API (RAG, tool use, multimodal, agents).
- [[Claude Quickstarts]] — Production-ready starter projects: customer support, computer use, browser automation, coding agent.
- [[Anthropic Courses]] — 5-course official curriculum: API fundamentals → prompt engineering → real-world prompting → evals → tool use. Jupyter notebooks.
- [[Anthropic Prompt Engineering Tutorial]] — 9-chapter interactive prompt engineering course with exercise playgrounds. Available direct API and Amazon Bedrock variants.
- [[Claude Code Action]] — GitHub Action that brings Claude into PR review and CI/CD workflows.
- [[Defending Code Reference Harness]] — Reference impl for autonomous vuln discovery + human-reviewed patching. gVisor-sandboxed agents. Not actively maintained; Claude Security is the hosted version.
- [[Scone Bench]] — 417-task benchmark for evaluating LLM agents on smart-contract vuln discovery/exploitation. Historical DeFi incidents, MCP-based, Docker-sandboxed. From Anthropic Red Team.
- [[Claudes C Compiler]] — Claude Opus 4.6 wrote a dependency-free C compiler in Rust from scratch. Compiles PostgreSQL, SQLite, Linux kernel, FFmpeg. Capability showcase, not production-validated.
- [[Anthropic Performance Take-Home]] — Open version of Anthropic's original performance engineering take-home. Optimize a VLIW SIMD kernel; Claude Opus 4.5 scored 1,363 cycles vs 147,734 baseline (108× improvement).
- [[Claude Code Security Review]] — GitHub Action that auto-scans PRs for security vulnerabilities using Claude.
- [[Claude Desktop Buddy]] — ESP32 desk pet + Bluetooth API reference for makers integrating with Claude Desktop.
- [[HTML Effectiveness Examples]] — Anthropic's reference collection of single-file HTML artifacts (slide decks, dashboards, editing UIs, diagrams).
- [[Claude Code Setup Plugin]] — Official Anthropic plugin that scans your codebase and recommends tailored hooks, skills, MCP servers, subagents, and plugins. Read-only, 1-2 recs per category.
- [[Claude Code Monitoring Guide]] — Prometheus + OpenTelemetry toolkit for tracking Claude Code ROI, token spend, and team adoption.
- [[GitHub MCP Server]] — GitHub's official MCP server.
- [[PineForge MCP]] — Hosted MCP server for real Pine Script v6 backtests. `claude mcp add --transport http pineforge https://mcp.pineforge.dev/mcp`. No key/signup. 245/246 TradingView parity, 100 backtests/week, 13mo Binance data. Docker route for unlimited/custom data. 60+ tools: repos, issues, PRs, code search, security scanning.
- [[Devcontainer Features]] — One-line devcontainer.json feature that installs Claude Code CLI in any dev container.
- [[Claude Code Routines]] — Scheduled/triggered cloud automation. Runs on Anthropic infrastructure, not your machine. `/schedule` command, API + GitHub + time triggers. Research preview.
- [[Long-Running Agent Primitives]] — 3 core primitives (Default-FAIL, Fresh-context evaluator, Handoff) + 2 operator hooks (kill switch, STEER.md). From Anthropic's own patterns.
- [[Claude Plugins Community]] — Community plugin marketplace (security-reviewed). Submit at clau.de/plugin-directory-submission.
- [[Anthropic CLI]] — `ant` CLI for the Claude Developer Platform API. `brew install anthropics/tap/ant`.
- [[Anthropic CWC Workshops]] — 8 Code-with-Claude workshop curricula: Managed Agents, memory primitives (Dreaming Service), eval-driven dev, multi-agent decomposition, Deal Desk reference impl.
- [[Agent SDK Workshop]] — Hands-on workshop for Claude Agent SDK: 4-stage guided demo (chat → tools → subagents → memory) + breakout scenarios. Python 3.10+, flip switches in config.py.
- [[Long-Horizon Coding Agent Demo]] — Archived AWS re:Invent 2025 demo. GitHub issue → agent builds full-stack app → CloudFront preview → human approval gate. Bedrock AgentCore + Claude Agent SDK.
- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.


Now I have a clear picture. I need to:
1. Create a wiki page for `launch-your-agent` (genuinely new)
2. Create a wiki page for `claude-tag-plugins` (genuinely new - 19 SaaS integrations)
3. Update `Home.md` to add both
4. Update the ingest log

Let me write these pages now.

I've got everything I need to proceed.

Two genuinely new pages to write. Creating them now.

Write

# Launch Your Agent

**Type:** Claude Code skill / founder tool
**By:** Anthropic
**Repo:** https://github.com/anthropics/launch-your-agent
**Platform:** Claude Code

## What it is

A Claude Code skill that takes a founder or developer from a raw agent idea to a live Claude Managed Agent — in one guided session. Handles the full pipeline: interview → scope → deploy → grade → schedule.

## Skills

| Skill | What it does |
|---|---|
| `/launch-your-agent` | Main entry point — kicks off the full build workflow |
| `/wrap-up` | Generates completion summary, recaps primitives built, suggests v2 upgrades |

## Workflow (4 phases)

1. **Interview** — Guided questions to gather requirements and clarify what the agent should do
2. **Stage & Launch** — Scopes a minimum viable version, deploys it to the user's Anthropic Console account
3. **Grade & Iterate** — Evaluates the live agent against success criteria, refines based on results
4. **Run Without You** — Optional: configures a scheduled deployment for recurring tasks

## What gets created

- Live managed agent in the user's Anthropic Console
- Local `my-agent/` project folder containing:
  - Build documentation and API payloads
  - Resumable launch script (in case the session is interrupted)
  - Evaluation scaffolding
  - Overview page + roadmap (v1/v2 planning)

## Notable details

- API key stays local in `.env` — never exposed in chat
- Designed to cost cents, not dollars
- Works with any Claude Managed Agent use case: internal workers, product features, customer-facing agents

## Applicability

- **nanoclaw** — directly applicable pattern: this is essentially an automated version of spinning up NanoClaw agents. The interview → scope → grade loop is worth studying for how Nano could help James spec and launch new agents.
- **qip-qien** — the grade-and-iterate phase mirrors the feedback loop qip-qien uses for expert review

## Related

- [[Managed Agents]] — the platform this deploys to
- [[Claude Agent SDK TypeScript]] / [[Claude Agent SDK Python]] — the SDK under the hood
- [[Claude Plugins Official]] — distribution channel for the skill
- [[Long-Running Agent Primitives]] — patterns for making the deployed agent reliable

# Claude Tag Plugins

**Type:** SaaS integration plugin collection
**By:** Anthropic
**Repo:** https://github.com/anthropics/claude-tag-plugins
**Platform:** Claude (via Claude Tag CLI)

## What it is

19 service integration plugins that connect Claude to common SaaS tools. Each plugin is independent — install only what you need. Skills activate automatically when relevant (no manual invocation required). Credentials are injected at runtime; no hardcoded keys.

## Included integrations

| Category | Services |
|---|---|
| Project management | Asana, Jira, Linear |
| Analytics / data warehouses | BigQuery, Redshift, Snowflake |
| Knowledge / docs | Confluence, Google Drive, Notion |
| CRM | HubSpot, Salesforce |
| Incident / monitoring | PagerDuty, Datadog, Grafana, Sentry |
| Utilities | Data viz, Troubleshoot (agent debugging) |

## How to install

```bash
# Add the marketplace, then selectively install plugins
claude-tag add marketplace anthropics/claude-tag-plugins
claude-tag install linear
claude-tag install sentry
```

## How it works

- Each plugin has a manifest + skills organized by service
- Skills activate contextually — no need to invoke manually
- Credential env vars are placeholders; the runtime injects real credentials (never stored in plugin files)

## Related

- [[Knowledge Work Plugins]] — role-focused plugins (sales, finance, legal, etc.) vs. these service-focused ones
- [[Claude Plugins Official]] — official plugin marketplace
- [[Claude Plugins Community]] — community plugin marketplace


File created successfully at: /workspace/extra/second-brain/wiki/tools/Launch Your Agent.md (file state is current in your context — no need to Read it back)

# Launch Your Agent

**Type:** Claude Code skill / founder tool
**By:** Anthropic
**Repo:** https://github.com/anthropics/launch-your-agent
**Platform:** Claude Code

## What it is

A Claude Code skill that takes a founder or developer from a raw agent idea to a live Claude Managed Agent — in one guided session. Handles the full pipeline: interview → scope → deploy → grade → schedule.

## Skills

| Skill | What it does |
|---|---|
| `/launch-your-agent` | Main entry point — kicks off the full build workflow |
| `/wrap-up` | Generates completion summary, recaps primitives built, suggests v2 upgrades |

## Workflow (4 phases)

1. **Interview** — Guided questions to gather requirements and clarify what the agent should do
2. **Stage & Launch** — Scopes a minimum viable version, deploys it to the user's Anthropic Console account
3. **Grade & Iterate** — Evaluates the live agent against success criteria, refines based on results
4. **Run Without You** — Optional: configures a scheduled deployment for recurring tasks

## What gets created

- Live managed agent in the user's Anthropic Console
- Local `my-agent/` project folder containing:
  - Build documentation and API payloads
  - Resumable launch script (in case the session is interrupted)
  - Evaluation scaffolding
  - Overview page + roadmap (v1/v2 planning)

## Notable details

- API key stays local in `.env` — never exposed in chat
- Designed to cost cents, not dollars
- Works with any Claude Managed Agent use case: internal workers, product features, customer-facing agents

## Applicability

- **nanoclaw** — directly applicable pattern: this is essentially an automated version of spinning up NanoClaw agents. The interview → scope → grade loop is worth studying for how Nano could help James spec and launch new agents.
- **qip-qien** — the grade-and-iterate phase mirrors the feedback loop qip-qien uses for expert review

## Related

- [[Managed Agents]] — the platform this deploys to
- [[Claude Agent SDK TypeScript]] / [[Claude Agent SDK Python]] — the SDK under the hood
- [[Claude Plugins Official]] — distribution channel for the skill
- [[Long-Running Agent Primitives]] — patterns for making the deployed agent reliable


File created successfully at: /workspace/extra/second-brain/wiki/tools/Claude Tag Plugins.md (file state is current in your context — no need to Read it back)

# Claude Tag Plugins

**Type:** SaaS integration plugin collection
**By:** Anthropic
**Repo:** https://github.com/anthropics/claude-tag-plugins
**Platform:** Claude (via Claude Tag CLI)

## What it is

19 service integration plugins that connect Claude to common SaaS tools. Each plugin is independent — install only what you need. Skills activate automatically when relevant (no manual invocation required). Credentials are injected at runtime; no hardcoded keys.

## Included integrations

| Category | Services |
|---|---|
| Project management | Asana, Jira, Linear |
| Analytics / data warehouses | BigQuery, Redshift, Snowflake |
| Knowledge / docs | Confluence, Google Drive, Notion |
| CRM | HubSpot, Salesforce |
| Incident / monitoring | PagerDuty, Datadog, Grafana, Sentry |
| Utilities | Data viz, Troubleshoot (agent debugging) |

## How to install

```bash
# Add the marketplace, then selectively install plugins
claude-tag add marketplace anthropics/claude-tag-plugins
claude-tag install linear
claude-tag install sentry
```

## How it works

- Each plugin has a manifest + skills organized by service
- Skills activate contextually — no need to invoke manually
- Credential env vars are placeholders; the runtime injects real credentials (never stored in plugin files)

## Related

- [[Knowledge Work Plugins]] — role-focused plugins (sales, finance, legal, etc.) vs. these service-focused ones
- [[Claude Plugins Official]] — official plugin marketplace
- [[Claude Plugins Community]] — community plugin marketplace


Edit

- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.

- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Tag Plugins]] — 19 SaaS integration plugins (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Credentials injected at runtime; install only what you need.
- [[Launch Your Agent]] — Claude Code skill that guides a founder from raw idea to live Claude Managed Agent: interview → scope → deploy → grade → schedule. One session, costs cents.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.


The file /workspace/extra/second-brain/wiki/Home.md has been updated successfully. (file state is current in your context — no need to Read it back)

- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.

- [[Claude Foundation Models Swift Package]] — Swift package for hybrid Apple-platform apps: on-device model for fast/private tasks, Claude for reasoning + web search. iOS 27+, SPM install. Announced June 2026.
- [[Claude Tag Plugins]] — 19 SaaS integration plugins (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Credentials injected at runtime; install only what you need.
- [[Launch Your Agent]] — Claude Code skill that guides a founder from raw idea to live Claude Managed Agent: interview → scope → deploy → grade → schedule. One session, costs cents.
- [[Claude Fable 5 and Mythos 5]] — Anthropic's latest frontier models. Always-on adaptive thinking, new tokenizer (~30% more tokens), refusal stop reason + SDK fallback middleware, 30-day data-retention requirement. Fable 5 = GA; Mythos 5 = Preview.

- [[Agent SDK Workshop]] — Hands-on workshop for Claude Agent SDK: 4-stage guided demo (chat → tools → subagents → memory) + breakout scenarios. Python 3.10+, flip switches in config.py.

- [[Long-Horizon Coding Agent Demo]] — Archived AWS re:Invent 2025 demo. GitHub issue → agent builds full-stack app → CloudFront preview → human approval gate. Bedrock AgentCore + Claude Agent SDK.

+- [[Claude Tag Plugins]] — 19 SaaS integration plugins (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Credentials injected at runtime; install only what you need.

+- [[Launch Your Agent]] — Claude Code skill that guides a founder from raw idea to live Claude Managed Agent: interview → scope → deploy → grade → schedule. One session, costs cents.


## 2026-07-07 (Anthropic GitHub sweep #23)

- **[[Launch Your Agent]]** (new) — Claude Code skill that takes a founder from raw agent idea to a live Claude Managed Agent in one guided session: interview → scope → deploy → grade → optional schedule. Creates `my-agent/` folder with build docs, resumable script, and eval scaffolding. Deployable in the Anthropic Console.
- **[[Claude Tag Plugins]]** (new) — 19 SaaS integration plugins (Jira, Linear, Asana, Snowflake, BigQuery, Salesforce, HubSpot, Sentry, Datadog, Grafana, PagerDuty, Confluence, Google Drive, Notion, etc.) via Claude Tag CLI. Skills activate contextually, credentials runtime-injected.
- Skipped (already current): `defending-code-reference-harness`, `claude-plugins-official`, `knowledge-work-plugins`, `claude-code-security-review`, `claude-agent-sdk-python`, `claude-agent-sdk-typescript`, `claude-plugins-community`, `cwc-long-running-agents`, `claude-code-action`, `cwc-workshops`.
- Skipped (not relevant): `jacobian-lens` (interpretability research), `buffa` (Rust protobuf), `tokio` (Rust async runtime), `financial-services`/`healthcare`/`life-sciences` (vertical industry, no new capabilities), `courses`/`prompt-eng-interactive-tutorial` (educational).

## 2026-07-06


The file /workspace/extra/second-brain/wiki/Wiki Ingest Log.md has been updated successfully. (file state is current in your context — no need to Read it back)

## 2026-07-07 (Anthropic GitHub sweep #23)

- **[[Launch Your Agent]]** (new) — Claude Code skill that takes a founder from raw agent idea to a live Claude Managed Agent in one guided session: interview → scope → deploy → grade → optional schedule. Creates `my-agent/` folder with build docs, resumable script, and eval scaffolding. Deployable in the Anthropic Console.
- **[[Claude Tag Plugins]]** (new) — 19 SaaS integration plugins (Jira, Linear, Asana, Snowflake, BigQuery, Salesforce, HubSpot, Sentry, Datadog, Grafana, PagerDuty, Confluence, Google Drive, Notion, etc.) via Claude Tag CLI. Skills activate contextually, credentials runtime-injected.
- Skipped (already current): `defending-code-reference-harness`, `claude-plugins-official`, `knowledge-work-plugins`, `claude-code-security-review`, `claude-agent-sdk-python`, `claude-agent-sdk-typescript`, `claude-plugins-community`, `cwc-long-running-agents`, `claude-code-action`, `cwc-workshops`.
- Skipped (not relevant): `jacobian-lens` (interpretability research), `buffa` (Rust protobuf), `tokio` (Rust async runtime), `financial-services`/`healthcare`/`life-sciences` (vertical industry, no new capabilities), `courses`/`prompt-eng-interactive-tutorial` (educational).

## 2026-07-06

+## 2026-07-07 (Anthropic GitHub sweep #23)

+- **[[Launch Your Agent]]** (new) — Claude Code skill that takes a founder from raw agent idea to a live Claude Managed Agent in one guided session: interview → scope → deploy → grade → optional schedule. Creates `my-agent/` folder with build docs, resumable script, and eval scaffolding. Deployable in the Anthropic Console.

+- **[[Claude Tag Plugins]]** (new) — 19 SaaS integration plugins (Jira, Linear, Asana, Snowflake, BigQuery, Salesforce, HubSpot, Sentry, Datadog, Grafana, PagerDuty, Confluence, Google Drive, Notion, etc.) via Claude Tag CLI. Skills activate contextually, credentials runtime-injected.

+- Skipped (already current): `defending-code-reference-harness`, `claude-plugins-official`, `knowledge-work-plugins`, `claude-code-security-review`, `claude-agent-sdk-python`, `claude-agent-sdk-typescript`, `claude-plugins-community`, `cwc-long-running-agents`, `claude-code-action`, `cwc-workshops`.

+- Skipped (not relevant): `jacobian-lens` (interpretability research), `buffa` (Rust protobuf), `tokio` (Rust async runtime), `financial-services`/`healthcare`/`life-sciences` (vertical industry, no new capabilities), `courses`/`prompt-eng-interactive-tutorial` (educational).

- **[[Claude Blog - Field Guide to Claude Fable]]** (new source) — July 6. Thariq Shihipar. Practical field guide for working with Claude Fable: the 4-quadrant unknowns model (Known/Unknown × Knowns/Unknowns) and 8 elicitation techniques (blind spot pass, interview mode, reference-based prompting, implementation plan, explainer artifact, quiz mode). Core claim: output quality is now bottlenecked by user clarity, not model capability. Worked example: end-to-end video editing.


<message to="telegram-mg-17796">Anthropic GitHub sweep done. Most repos already had current wiki pages. Two genuinely new ones:

**[[Launch Your Agent]]** — Claude Code skill that takes you from raw agent idea to a live Managed Agent in one session: guided interview → scope → deploy to Console → grade → optional scheduling. Creates a `my-agent/` folder with build docs and eval scaffolding. Worth knowing about given the NanoClaw work.
https://jamess-mac-studio.tail02a1a0.ts.net/second-brain/#Launch%20Your%20Agent

**[[Claude Tag Plugins]]** — 19 SaaS integrations (Jira, Linear, Snowflake, Salesforce, Sentry, Datadog, etc.) via Claude Tag CLI. Skills activate contextually, credentials injected at runtime.
https://jamess-mac-studio.tail02a1a0.ts.net/second-brain/#Claude%20Tag%20Plugins

Everything else in the batch was maintenance updates to repos already in the wiki.</message>


<context timezone="America/Chicago" />
<task from="telegram-mg-17796" time="Jul 6, 2026, 11:56 PM">Instructions:
Prepare James daily portfolio brief. Read /workspace/extra/second-brain/portfolio/PLAN.md for the operating model, then read BOARD.md, all projects/*.md cards, and /workspace/agent/repo-awareness.md. Compare activity and dated Notes with the prior brief when available. Reply directly in this Telegram DM with a phone-readable brief under 20 lines: Moved (new activity since the previous brief), Stalled (items blocked on James for more than about 2 days), and Decisions (at most 3 numbered, concrete short-answer questions). While seeded cards remain unconfirmed, use card confirmation as a decision question. Ask at most one metric-definition question per brief. Never invent project goals. Use only stages research, discovery, spec, build, test, feedback, maintain. Do not modify the board during the brief; when James later answers, update the relevant card Goal, Stage, and Next action, append a dated Notes line, update the BOARD.md row, and remove answered items from its Decision queue. If nothing moved, say so plainly; still surface the highest-value decision question.</task>


Let me read the necessary files for the daily brief.


1	# Portfolio Operating Model — Plan & Decisions
2
3	**Owner:** James · **Created:** 2026-07-06 · **Status:** Tier 1 live
4
5	The goal: James operates as VP of Product across his project portfolio — setting
6	direction and taste, while agents carry research → discovery → spec → build → test →
7	feedback. This doc is the durable record of the plan and the decisions made.
8
9	## Framework decision: stay on NanoClaw
10
11	Evaluated 2026-07-06 against Hermes (Nous Research — model-agnostic, skill-learning
12	loop), OpenClaw (largest ecosystem, weakest isolation story), and NemoClaw (NVIDIA
13	enterprise platform — wrong fit for solo use). Decision: **stay on NanoClaw**.
14	The per-agent container isolation, `cli_scope`, and approval gates are exactly the
15	substrate needed once agents get write access to repos, and the accumulated
16	customization (ingestion modules, OneCLI vault, monitors, repo-awareness) compounds.
17	Adopt Hermes' *idea* (write a reusable skill after every solved problem — already the
18	monorepo Learning Law) without switching platforms. Escape hatch if Anthropic cost or
19	availability becomes a problem: `/add-opencode`, `/add-ollama-provider`.
20
21	## The three tiers
22
23	### Tier 1 — Board + daily brief (LIVE as of 2026-07-06)
24
25	- **Board**: `second-brain/portfolio/` — `BOARD.md` (index + decision queue) and
26	  `projects/*.md` (one card per active project). Mounted read-write into Nano's
27	  container at `/workspace/extra/second-brain/portfolio/`.
28	- **Daily brief**: scheduled task in Nano's Telegram DM session, 07:00 America/Chicago.
29	  Reads the board + repo-awareness (which now carries per-repo `Last activity` lines,
30	  refreshed every 30 min). Sends: what moved, what's stalled, ≤3 decision questions.
31	- **Decision queue**: James replies to the brief from his phone; Nano updates the
32	  board and cards. The queue comes to James — he never has to go look at anything.
33
34	### Tier 2 — Advance-one-stage loop (NEXT)
35
36	A scheduled/nightly run picks the highest-priority project with an unblocked next
37	action and moves it one stage (research → brief, brief → spec, spec → draft PR in a
38	git worktree). Each run ends with a **review packet** to Telegram: what it did, diff
39	summary, screenshot or test output, one question max. Prereqs before turning on:
40	- Per-project repo mounts into an agent container (or Claude Code sessions driven on
41	  the host) — decide per project.
42	- Review packet format agreed.
43	- Budget per run set.
44
45	### Tier 3 — Metric-driven autonomy (GATED)
46
47	Auto-merge below a size threshold when tests pass — allowed **per project, only once
48	that project's objective metric is named**. Five preconditions status:
49
50	| Precondition | Status |
51	|---|---|
52	| 1. Objective metric | ❌ **James-owned task** — name one per project on its card (`Metric:` field). Portfolio-level: user-visible improvements shipped/week at ≤2h of James's review time |
53	| 2. Measurement | Board diffs + git log + per-project checks; counter-metric: rework rate (% agent PRs rejected) |
54	| 3. Action space | Tier 2 actions + auto-merge (small, tested changes only) |
55	| 4. Stopping condition | Weekly token budget per project; pause a project if rework rate > ~30% |
56	| 5. Rollback | Everything is a PR on a branch; `git revert` + service restart |
57
58	## Decisions log (2026-07-06, James)
59
60	- **Board = plain files here, not Linear.** Rationale: agent-native (Nano and Claude
61	  Code both read/write files with zero API surface), no new habit required — Telegram
62	  is the phone interface, the board is just state. Linear can be layered later via
63	  nanoclaw's `/add-linear` if the habit ever sticks; the board content ports trivially.
64	- **Daily brief, not weekly**, to start. Dial back if it gets noisy.
65	- **Guard levels are per-project**, not global:
66	  - `review-required` — **TradingBot25** (deep time investment), **qip-qien**
67	    (customer trial in progress). Agent changes land as PRs; James approves merges.
68	  - `autonomous-ok` — everything else. James does not want to be a blocker; agents
69	    may proceed (branch + merge when tests pass) and report after the fact.
70	- **Tier 3 metrics are James's task** — captured as the `Metric:` field on each card;
71	  the daily brief may ask for at most one metric definition at a time.
72	- **index-repos runs every 30 min** (launchd `com.james.nanoclaw-repo-index`,
73	  logs to `nanoclaw/logs/repo-index.log`). It is deterministic (filesystem + GitHub
74	  REST, no LLM calls) so frequency is nearly free. Future upgrade: event-driven
75	  trigger on board edits / Claude Code session end (Stop hook) if 30 min ever feels
76	  stale.
77	- **Reddit ingestion is not a blocker and not waiting on James's testing.** It was
78	  effectively tested 2026-06-13: Reddit's unauthenticated `.json` API is 403-blocked
79	  at the edge, so every fetch fails gracefully (`status:failed`). To make it work:
80	  James registers a Reddit "script" app (his task), then an agent adds the OAuth
81	  client_credentials flow against `oauth.reddit.com`. Until then the module is
82	  harmless dead weight.
83
84	## Loose ends (tracked, not urgent)
85
86	- nanoclaw working tree has uncommitted Slack-channel install files
87	  (`src/channels/slack.ts`, setup scripts) from wiring #ingest-into-wiki — commit them.
88	- `nanoclaw/groups/main/` contains stale v1-era instructions (WhatsApp JIDs, IPC
89	  paths) — dead weight, clear when convenient.
90	- Ramon's Telegram DM (`telegram:8957631641`) is wired to the *same* Nano agent group
91	  as James's. Fine for now; revisit isolation if his usage grows.
92
93	## Conventions
94
95	- Stage vocabulary (fixed): `research → discovery → spec → build → test → feedback → maintain`
96	- Card fields: Repo, Goal, Stage, Guard, Metric, Blocked on James, Next action, Notes
97	  (dated, append-only).
98	- Nano updates cards from brief replies; anyone (James, Claude Code sessions) may edit
99	  the board directly — it's just files in git.
100

# Portfolio Operating Model — Plan & Decisions

**Owner:** James · **Created:** 2026-07-06 · **Status:** Tier 1 live

The goal: James operates as VP of Product across his project portfolio — setting
direction and taste, while agents carry research → discovery → spec → build → test →
feedback. This doc is the durable record of the plan and the decisions made.

## Framework decision: stay on NanoClaw

Evaluated 2026-07-06 against Hermes (Nous Research — model-agnostic, skill-learning
loop), OpenClaw (largest ecosystem, weakest isolation story), and NemoClaw (NVIDIA
enterprise platform — wrong fit for solo use). Decision: **stay on NanoClaw**.
The per-agent container isolation, `cli_scope`, and approval gates are exactly the
substrate needed once agents get write access to repos, and the accumulated
customization (ingestion modules, OneCLI vault, monitors, repo-awareness) compounds.
Adopt Hermes' *idea* (write a reusable skill after every solved problem — already the
monorepo Learning Law) without switching platforms. Escape hatch if Anthropic cost or
availability becomes a problem: `/add-opencode`, `/add-ollama-provider`.

## The three tiers

### Tier 1 — Board + daily brief (LIVE as of 2026-07-06)

- **Board**: `second-brain/portfolio/` — `BOARD.md` (index + decision queue) and
  `projects/*.md` (one card per active project). Mounted read-write into Nano's
  container at `/workspace/extra/second-brain/portfolio/`.
- **Daily brief**: scheduled task in Nano's Telegram DM session, 07:00 America/Chicago.
  Reads the board + repo-awareness (which now carries per-repo `Last activity` lines,
  refreshed every 30 min). Sends: what moved, what's stalled, ≤3 decision questions.
- **Decision queue**: James replies to the brief from his phone; Nano updates the
  board and cards. The queue comes to James — he never has to go look at anything.

### Tier 2 — Advance-one-stage loop (NEXT)

A scheduled/nightly run picks the highest-priority project with an unblocked next
action and moves it one stage (research → brief, brief → spec, spec → draft PR in a
git worktree). Each run ends with a **review packet** to Telegram: what it did, diff
summary, screenshot or test output, one question max. Prereqs before turning on:
- Per-project repo mounts into an agent container (or Claude Code sessions driven on
  the host) — decide per project.
- Review packet format agreed.
- Budget per run set.

### Tier 3 — Metric-driven autonomy (GATED)

Auto-merge below a size threshold when tests pass — allowed **per project, only once
that project's objective metric is named**. Five preconditions status:

| Precondition | Status |
|---|---|
| 1. Objective metric | ❌ **James-owned task** — name one per project on its card (`Metric:` field). Portfolio-level: user-visible improvements shipped/week at ≤2h of James's review time |
| 2. Measurement | Board diffs + git log + per-project checks; counter-metric: rework rate (% agent PRs rejected) |
| 3. Action space | Tier 2 actions + auto-merge (small, tested changes only) |
| 4. Stopping condition | Weekly token budget per project; pause a project if rework rate > ~30% |
| 5. Rollback | Everything is a PR on a branch; `git revert` + service restart |

## Decisions log (2026-07-06, James)

- **Board = plain files here, not Linear.** Rationale: agent-native (Nano and Claude
  Code both read/write files with zero API surface), no new habit required — Telegram
  is the phone interface, the board is just state. Linear can be layered later via
  nanoclaw's `/add-linear` if the habit ever sticks; the board content ports trivially.
- **Daily brief, not weekly**, to start. Dial back if it gets noisy.
- **Guard levels are per-project**, not global:
  - `review-required` — **TradingBot25** (deep time investment), **qip-qien**
    (customer trial in progress). Agent changes land as PRs; James approves merges.
  - `autonomous-ok` — everything else. James does not want to be a blocker; agents
    may proceed (branch + merge when tests pass) and report after the fact.
- **Tier 3 metrics are James's task** — captured as the `Metric:` field on each card;
  the daily brief may ask for at most one metric definition at a time.
- **index-repos runs every 30 min** (launchd `com.james.nanoclaw-repo-index`,
  logs to `nanoclaw/logs/repo-index.log`). It is deterministic (filesystem + GitHub
  REST, no LLM calls) so frequency is nearly free. Future upgrade: event-driven
  trigger on board edits / Claude Code session end (Stop hook) if 30 min ever feels
  stale.
- **Reddit ingestion is not a blocker and not waiting on James's testing.** It was
  effectively tested 2026-06-13: Reddit's unauthenticated `.json` API is 403-blocked
  at the edge, so every fetch fails gracefully (`status:failed`). To make it work:
  James registers a Reddit "script" app (his task), then an agent adds the OAuth
  client_credentials flow against `oauth.reddit.com`. Until then the module is
  harmless dead weight.

## Loose ends (tracked, not urgent)

- nanoclaw working tree has uncommitted Slack-channel install files
  (`src/channels/slack.ts`, setup scripts) from wiring #ingest-into-wiki — commit them.
- `nanoclaw/groups/main/` contains stale v1-era instructions (WhatsApp JIDs, IPC
  paths) — dead weight, clear when convenient.
- Ramon's Telegram DM (`telegram:8957631641`) is wired to the *same* Nano agent group
  as James's. Fine for now; revisit isolation if his usage grows.

## Conventions

- Stage vocabulary (fixed): `research → discovery → spec → build → test → feedback → maintain`
- Card fields: Repo, Goal, Stage, Guard, Metric, Blocked on James, Next action, Notes
  (dated, append-only).
- Nano updates cards from brief replies; anyone (James, Claude Code sessions) may edit
  the board directly — it's just files in git.


1	# Portfolio Board
2
3	One row per active project. Cards with full detail live in `projects/`.
4	Operating model + decisions: [PLAN.md](PLAN.md).
5	Stages: `research → discovery → spec → build → test → feedback → maintain`.
6	Guard: `review-required` (James approves merges) or `autonomous-ok` (agents proceed, report after).
7
8	**Seeded 2026-07-06 from git activity — stages and next actions are drafts until James confirms.**
9
10	| Project | Stage | Guard | Next action | Blocked on James | Last activity |
11	|---|---|---|---|---|---|
12	| [qip-qien](projects/qip-qien.md) | feedback | review-required | Confirm goal + trial status in brief | confirm card | 2026-07-06 |
13	| [congressional-trading](projects/congressional-trading.md) | test | autonomous-ok | Define precision target; run backtest | exit criteria for shadow mode | 2026-07-06 |
14	| [FindRefurbishedAppleProduct](projects/FindRefurbishedAppleProduct.md) | discovery | autonomous-ok | Confirm goal — brand new repo | confirm card | 2026-07-06 |
15	| [TradingBot25](projects/TradingBot25.md) | build | review-required | Confirm goal + current strategy state | confirm card | 2026-06-26 |
16	| [AgenticLever](projects/AgenticLever.md) | build | autonomous-ok | Confirm goal | confirm card | 2026-06-29 |
17	| [pool-monitor](projects/pool-monitor.md) | maintain | autonomous-ok | None — steady state? confirm | confirm card | 2026-06-17 |
18	| [StageHand](projects/StageHand.md) | discovery | autonomous-ok | Competitive analysis (James sharing links) | share Instagram competitor links | 2026-07-06 |
19	| [MentorCore](projects/MentorCore.md) | research | autonomous-ok | Parked — no bandwidth | none | 2026-06-11 |
20	| [RoadSense](projects/RoadSense.md) | spec | autonomous-ok | Scope public-launch work + GTM; fix display bug | none | 2026-06-06 |
21	| [nanoclaw](projects/nanoclaw.md) | build | autonomous-ok | Commit Slack files; Reddit OAuth app (James) | reddit app registration | 2026-06-13 |
22
23	## Decision queue
24
25	Questions for James, appended by Nano; answered items move to the card's Notes and are removed here.
26
27	- (empty — first daily brief will ask to confirm the seeded cards above)
28
29	## Recently shipped
30
31	- (empty)
32

# Portfolio Board

One row per active project. Cards with full detail live in `projects/`.
Operating model + decisions: [PLAN.md](PLAN.md).
Stages: `research → discovery → spec → build → test → feedback → maintain`.
Guard: `review-required` (James approves merges) or `autonomous-ok` (agents proceed, report after).

**Seeded 2026-07-06 from git activity — stages and next actions are drafts until James confirms.**

| Project | Stage | Guard | Next action | Blocked on James | Last activity |
|---|---|---|---|---|---|
| [qip-qien](projects/qip-qien.md) | feedback | review-required | Confirm goal + trial status in brief | confirm card | 2026-07-06 |
| [congressional-trading](projects/congressional-trading.md) | test | autonomous-ok | Define precision target; run backtest | exit criteria for shadow mode | 2026-07-06 |
| [FindRefurbishedAppleProduct](projects/FindRefurbishedAppleProduct.md) | discovery | autonomous-ok | Confirm goal — brand new repo | confirm card | 2026-07-06 |
| [TradingBot25](projects/TradingBot25.md) | build | review-required | Confirm goal + current strategy state | confirm card | 2026-06-26 |
| [AgenticLever](projects/AgenticLever.md) | build | autonomous-ok | Confirm goal | confirm card | 2026-06-29 |
| [pool-monitor](projects/pool-monitor.md) | maintain | autonomous-ok | None — steady state? confirm | confirm card | 2026-06-17 |
| [StageHand](projects/StageHand.md) | discovery | autonomous-ok | Competitive analysis (James sharing links) | share Instagram competitor links | 2026-07-06 |
| [MentorCore](projects/MentorCore.md) | research | autonomous-ok | Parked — no bandwidth | none | 2026-06-11 |
| [RoadSense](projects/RoadSense.md) | spec | autonomous-ok | Scope public-launch work + GTM; fix display bug | none | 2026-06-06 |
| [nanoclaw](projects/nanoclaw.md) | build | autonomous-ok | Commit Slack files; Reddit OAuth app (James) | reddit app registration | 2026-06-13 |

## Decision queue

Questions for James, appended by Nano; answered items move to the card's Notes and are removed here.

- (empty — first daily brief will ask to confirm the seeded cards above)

## Recently shipped

- (empty)


1	# qip-qien
2
3	- Repo: `~/projects/qip-ask-qien` · https://github.com/jamesjlopez/qip-qien
4	- Goal: _to confirm — expert Q&A persona for medical-device quality (Ramon's domain)?_
5	- Stage: feedback (seeded — confirm)
6	- Guard: **review-required** — customer trial in progress
7	- Metric: _undefined — James to name (candidate: trial-user questions answered satisfactorily/week)_
8	- Blocked on James: confirm this card
9	- Next action: confirm goal + trial status in daily brief
10
11	## Notes
12	- 2026-07-06 — Seeded from git activity: "chore: log Fable model review findings" (same-day commit).
13

# qip-qien

- Repo: `~/projects/qip-ask-qien` · https://github.com/jamesjlopez/qip-qien
- Goal: _to confirm — expert Q&A persona for medical-device quality (Ramon's domain)?_
- Stage: feedback (seeded — confirm)
- Guard: **review-required** — customer trial in progress
- Metric: _undefined — James to name (candidate: trial-user questions answered satisfactorily/week)_
- Blocked on James: confirm this card
- Next action: confirm goal + trial status in daily brief

## Notes
- 2026-07-06 — Seeded from git activity: "chore: log Fable model review findings" (same-day commit).


1	# TradingBot25
2
3	- Repo: `~/projects/TradingBot25` · private GitHub
4	- Goal: _to confirm — multi-asset Claude trading bot (Claude Code writes logic, daily briefings)?_
5	- Stage: build (seeded — confirm)
6	- Guard: **review-required** — deep time investment
7	- Metric: _undefined — James to name (candidates: backtest PnL, live PnL vs benchmark)_
8	- Blocked on James: confirm this card
9	- Next action: confirm goal + current strategy state
10
11	## Notes
12	- 2026-07-06 — Seeded from git activity: "Weights update" (2026-06-26).
13

# TradingBot25

- Repo: `~/projects/TradingBot25` · private GitHub
- Goal: _to confirm — multi-asset Claude trading bot (Claude Code writes logic, daily briefings)?_
- Stage: build (seeded — confirm)
- Guard: **review-required** — deep time investment
- Metric: _undefined — James to name (candidates: backtest PnL, live PnL vs benchmark)_
- Blocked on James: confirm this card
- Next action: confirm goal + current strategy state

## Notes
- 2026-07-06 — Seeded from git activity: "Weights update" (2026-06-26).


1	# AgenticLever
2
3	- Repo: `~/projects/AgenticLever` · https://github.com/jamesjlopez/AgenticLever-website
4	- Goal: _to confirm — solution-selling site with question-led discovery flow?_
5	- Stage: build (seeded — confirm)
6	- Guard: autonomous-ok
7	- Metric: _undefined — James to name (candidates: interest sign-ups/week, discovery-flow completion rate)_
8	- Blocked on James: confirm this card
9	- Next action: confirm goal
10
11	## Notes
12	- 2026-07-06 — Seeded from git activity: "feat: add NTFY_CLICK_URL support" (2026-06-29). Working tree has uncommitted changes.
13

# AgenticLever

- Repo: `~/projects/AgenticLever` · https://github.com/jamesjlopez/AgenticLever-website
- Goal: _to confirm — solution-selling site with question-led discovery flow?_
- Stage: build (seeded — confirm)
- Guard: autonomous-ok
- Metric: _undefined — James to name (candidates: interest sign-ups/week, discovery-flow completion rate)_
- Blocked on James: confirm this card
- Next action: confirm goal

## Notes
- 2026-07-06 — Seeded from git activity: "feat: add NTFY_CLICK_URL support" (2026-06-29). Working tree has uncommitted changes.


1	# FindRefurbishedAppleProduct
2
3	- Repo: `~/projects/FindRefurbishedAppleProduct`
4	- Goal: _to confirm — brand new (initial commit today)_
5	- Stage: discovery (seeded — confirm)
6	- Guard: autonomous-ok
7	- Metric: _undefined_
8	- Blocked on James: confirm this card
9	- Next action: confirm goal and whether this is a monitor (alert on refurb stock?) or a site
10
11	## Notes
12	- 2026-07-06 — Seeded from git activity: "Initial commit: refurbished Apple ..." (same-day).
13

# FindRefurbishedAppleProduct

- Repo: `~/projects/FindRefurbishedAppleProduct`
- Goal: _to confirm — brand new (initial commit today)_
- Stage: discovery (seeded — confirm)
- Guard: autonomous-ok
- Metric: _undefined_
- Blocked on James: confirm this card
- Next action: confirm goal and whether this is a monitor (alert on refurb stock?) or a site

## Notes
- 2026-07-06 — Seeded from git activity: "Initial commit: refurbished Apple ..." (same-day).


Now I have everything I need for the brief. Let me assess:

**Moved (new activity since last brief):**
- This is the first brief, so there's no prior brief to compare against. All notes are from 2026-07-06 (yesterday). Since there's no prior brief, I'll note what happened yesterday.
- RoadSense — confirmed goal, decided to go public, scoping doc written, cw-coder did 2 phases of congressional-trading work
- congressional-trading — cw-coder completed Phase 1 (win-rate fix) and Phase 2 (backtest sweep script). Two commits landed.
- StageHand — new card created from James's context
- MentorCore — confirmed as parked

**Stalled (blocked on James for more than ~2 days):**
The board was just seeded yesterday, so nothing is technically stalled beyond two days yet. However, nanoclaw has been blocked on reddit app registration since mid-June, and there are several items waiting on James to confirm cards like TradingBot25, AgenticLever, and q.

**Decisions (max 3):**
I'm narrowing down the most critical decision questions: whether qip-qien is focused on expert Q&A for medical-device quality and if the trial is still active (highest priority since it's review-required), confirming TradingBot25's goal as a multi-asset Claude trading bot and its current strategy state, and getting clarity on StageHand's competitor research.

Actually, I should focus on questions James can answer quickly over the phone — so: is qip-qien the expert Q&A for Ramon's medical-device domain with an active trial, and is TradingBot25 still actively being built as a multi-asset trading bot?

For congressional-trading, the real blocker is whether the backtest sweep script has been run locally to get calibration data. And I'm noting that RoadSense is moving forward with a public launch and 6-9 week timeline, congressional-trading has the win-rate fix ready to test, and StageHand is a new addition to track.

For the decisions section, I need to frame these as yes/no or multiple-choice questions that James can answer quickly: qip-qien's goal confirmation (expert Q&A for medical devices with active trial), TradingBot25's status (still building or paused), and whether the congressional-trading backtest has been run yet to determine the go-live threshold.

I'm structuring this as a brief that stays under 20 lines and phone-readable, using the format of Moved/Stalled/Decisions. Since this is the first brief, "moved" captures what happened recently rather than incremental changes since a previous update.


<message to="telegram-mg-17796">**Portfolio Brief — Jul 7**

**Moved**
- *RoadSense* → spec: go-public decision made, scoping doc written (6–9 weeks, multi-region pipeline is the main chunk)
- *congressional-trading*: cw-coder delivered win-rate fix + backtest sweep script (commits `14b4cc9`, `b434e5b`) — ready to run locally
- *StageHand*: new card added (real estate video suite, discovery stage)
- *MentorCore*: confirmed parked

**Stalled**
- *nanoclaw*: Reddit app registration waiting 3+ weeks — still needed before OAuth can be wired
- *StageHand*: waiting on Instagram competitor links from you

**Decisions**
1. *qip-qien* — Is the goal an expert Q&A tool for Ramon's medical-device quality domain, and is the trial still live? (yes / different goal)
2. *TradingBot25* — Actively building, or paused for now? (active / paused)
3. *FindRefurbishedAppleProduct* — Is this a personal alert (notify when refurb stock appears) or a public site? (alert / site)</message>


<context timezone="America/Chicago" />
<message id="1036" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:02 AM">
  <quoted_message from="NanoClawM1_bot">Found the answer. Two things needed on your end:

1. Update the mount allowlist at ~/.config/nanoclaw/mount-allowlist.json — add your projects folder as an allowed root. If the file doesn't exist yet, create it:

{
  "allowedRoots": [
    {
      "path": "/Users/jameslopez/projects/second-brain",
      "allowReadWrite": true
    },
    {
      "path": "/Users/jameslopez/projects",
      "allowReadWrite": true
    }
  ]
}

2. Update the DB directly — there's no CLI command for mounts. Run this against the NanoClaw SQLite DB (find its path in ~/projects/nanoclaw/):

UPDATE container_configs
SET additional_mounts = '[
  {"hostPath":"/Users/jameslopez/projects/second-brain","containerPath":"second-brain","readonly":false},
  {"hostPath":"/Users/jameslopez/projects","containerPath":"projects","readonly":false}
]',
updated_at = datetime('now')
WHERE agent_group_id = 'ag-1779666729747-9n7kga';

Then ncl groups restart and all your projects will be at /workspace/extra/projects/ in my container.</quoted_message>
how and where do i run this sql ?</message>


James is asking how and where to run the SQL to update the NanoClaw database. I need to help him find the NanoClaw SQLite DB and run the update against it.

The NanoClaw app is at `~/projects/nanoclaw/`. The SQLite DB is probably in a data directory there. Common locations would be:
- `~/projects/nanoclaw/data/nanoclaw.db` or similar
- `~/projects/nanoclaw/nanoclaw.db`
- Inside a docker volume or local storage path

Since James is on a Mac, he can use the built-in `sqlite3` CLI tool (usually pre-installed on macOS) or any SQLite browser app.
I'll give him a straightforward Terminal approach—first finding the database file, then running the SQL update against it with a simple command.


<message to="telegram-mg-17796">Open **Terminal** on your Mac and run these two commands:

**Step 1 — find the DB:**
```
find ~/projects/nanoclaw -name "*.db" 2>/dev/null
```
That'll show you the path. It's probably something like `~/projects/nanoclaw/data/nanoclaw.db`.

**Step 2 — run the SQL** (replace the path with what you found):
```
sqlite3 ~/projects/nanoclaw/data/nanoclaw.db "UPDATE container_configs SET additional_mounts = '[{\"hostPath\":\"/Users/jameslopez/projects/second-brain\",\"containerPath\":\"second-brain\",\"readonly\":false},{\"hostPath\":\"/Users/jameslopez/projects\",\"containerPath\":\"projects\",\"readonly\":false}]', updated_at = datetime(''now'') WHERE agent_group_id = ''ag-1779666729747-9n7kga'';"
```

If you get "no such file" on sqlite3, it should already be on macOS — just run `which sqlite3` to confirm. After it runs with no error, do `ncl groups restart` and I'll be able to see your projects folder.</message>


<context timezone="America/Chicago" />
<message id="1038" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:02 AM">sqlite3 ~/projects/nanoclaw/data/nanoclaw.db "UPDATE container_configs SET additional_mounts = '[{\"hostPath\":\"/Users/jameslopez/projects/second-brain\",\"containerPath\":\"second-brain\",\"readonly\":false},{\"hostPath\":\"/Users/jameslopez/projects\",\"containerPath\":\"projects\",\"readonly\":false}]', updated_at = datetime(''now'') WHERE agent_group_id = ''ag-1779666729747-9n7kga'';"
Parse error in 2nd command line argument: near "now": syntax error
  cts","readonly":false}]', updated_at = datetime(''now'') WHERE agent_group_id
                                      error here ---^</message>


The issue is with the single quotes inside the sqlite3 double-quoted string. In SQLite, when you pass a query as a shell argument wrapped in double quotes, single quotes work fine - but `''now''` should be `'now'` not `''now''`. The double single-quotes are SQLite's way of escaping single quotes, but here it's causing a parse error because the shell isn't interpreting them correctly.

The fix is to use `datetime('now')` with single quotes, but since the whole command is in double quotes for the shell, I need to handle the quoting differently.

The simplest fix is to use a heredoc or write the SQL to a file and execute it, OR use single quotes for the outer shell argument and escape the inner single quotes differently.
Using a heredoc with the SQL query is much cleaner - I can pass the entire statement without worrying about quote escaping issues since the heredoc preserves the literal SQL syntax.


<message to="telegram-mg-17796">Quoting issue — use this version instead (paste the whole block into Terminal):

```
sqlite3 ~/projects/nanoclaw/data/nanoclaw.db << 'EOF'
UPDATE container_configs
SET additional_mounts = '[{"hostPath":"/Users/jameslopez/projects/second-brain","containerPath":"second-brain","readonly":false},{"hostPath":"/Users/jameslopez/projects","containerPath":"projects","readonly":false}]',
updated_at = datetime('now')
WHERE agent_group_id = 'ag-1779666729747-9n7kga';
EOF
```

If it runs with no output, it worked. Then run `ncl groups restart`.</message>


<context timezone="America/Chicago" />
<message id="1040" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:03 AM">but there was an error here message that pointed to the ''now'' statement</message>


James seems confused - he's quoting my previous message's error, but I just gave him a new version using a heredoc which should avoid the quoting issue entirely. He's referring to the error in the previous command, not the new one I just sent.

Let me clarify that the new heredoc version (the one with `<< 'EOF'`) doesn't have that quoting problem - he should try the new command.


<message to="telegram-mg-17796">That error was from the previous command — the new one I just sent (with `<< 'EOF'` at the end) doesn't have that issue. Try the new block — paste the whole thing including the `EOF` line at the end.</message>


<context timezone="America/Chicago" />
<message id="1042" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:05 AM">Parse error near line 1: no such table: container_configs</message>


The table doesn't exist in that DB file. This means either:
1. The DB file found isn't the right one (there might be multiple .db files)
2. The DB schema hasn't been applied yet
3. The data is in a different DB

Let me help James find the right DB. He should look for all .db files in the nanoclaw project folder and check which one has the container_configs table.

Let me give him a command to find the right DB.


<message to="telegram-mg-17796">Wrong DB file. Run this to find the right one:

```
find ~/projects/nanoclaw -name "*.db" -exec sh -c 'sqlite3 "$1" ".tables" 2>/dev/null | grep -q container_configs && echo "$1"' _ {} \;
```

That'll print the path of whichever DB has the `container_configs` table. Then re-run the update with that path.</message>


<context timezone="America/Chicago" />
<message id="1044" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:06 AM">/Users/jameslopez/projects/nanoclaw/data/v2.db</message>


<message to="telegram-mg-17796">

```
sqlite3 ~/projects/nanoclaw/data/v2.db << 'EOF'
UPDATE container_configs
SET additional_mounts = '[{"hostPath":"/Users/jameslopez/projects/second-brain","containerPath":"second-brain","readonly":false},{"hostPath":"/Users/jameslopez/projects","containerPath":"projects","readonly":false}]',
updated_at = datetime('now')
WHERE agent_group_id = 'ag-1779666729747-9n7kga';
EOF
```

No output = success. Then `ncl groups restart`.</message>


<context timezone="America/Chicago" />
<message id="1046" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:07 AM">ncl groups restart
(node:89167) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
error (handler-error): --id is required</message>


<message to="telegram-mg-17796">

```
ncl groups restart --id ag-1779666729747-9n7kga
```</message>


<context timezone="America/Chicago" />
<message id="1048" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:07 AM">ncl groups restart --id ag-1779666729747-9n7kga
(node:89315) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
{
  "restarted": 1,
  "rebuilt": false
}</message>


The restart succeeded. Now I should be able to verify that the projects mount is accessible.


Bash

ls /workspace/extra/projects/ 2>/dev/null | head -20

Check if projects mount is now accessible


(Bash completed with no output)


Check workspace/extra contents


second-brain


The projects mount isn't showing up yet. This could be because:
1. The mount allowlist at `~/.config/nanoclaw/mount-allowlist.json` hasn't been created yet - that's a prerequisite
2. The container restart might not have taken effect yet in this session

Let me check if the allowlist was created. But I can't access the host filesystem directly.

The allowlist step was listed as step 1 but James jumped straight to the DB update. He may not have created the allowlist file yet.

Let me ask James to confirm the allowlist exists and check the container config to see if the mount is now in the DB.


<message to="telegram-mg-17796">Almost — the restart worked but the projects folder isn't visible yet. You still need to create the mount allowlist. Run this in Terminal:

```
mkdir -p ~/.config/nanoclaw && cat > ~/.config/nanoclaw/mount-allowlist.json << 'EOF'
{
  "allowedRoots": [
    {
      "path": "/Users/jameslopez/projects/second-brain",
      "allowReadWrite": true
    },
    {
      "path": "/Users/jameslopez/projects",
      "allowReadWrite": true
    }
  ]
}
EOF
```

Then restart again:
```
ncl groups restart --id ag-1779666729747-9n7kga
```</message>


<context timezone="America/Chicago" />
<message id="1050" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:08 AM">jameslopez@MacStudio nanoclaw % ncl groups restart --id ag-1779666729747-9n7kga
(node:89597) [DEP0205] DeprecationWarning: `module.register()` is deprecated. Use `module.registerHooks()` instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
{
  "restarted": 1,
  "rebuilt": false
}</message>


ls /workspace/extra/projects/ 2>/dev/null | head -20

Check if projects mount is now accessible after restart


Check workspace/extra contents


Still not showing up. The mount might not be working. Let me check the NanoClaw config to see if additional_mounts is set correctly, and also verify the allowlist is read.

Actually wait - the container was restarted, but I'm still in the same session. The restart may have spun up a new container but this current session might still be running in the old one. Or the mount validation is failing silently.

Let me check the ncl groups config to see if additional_mounts is properly set now.


ncl groups config get --id ag-1779666729747-9n7kga 2>/dev/null | python3 -c "import sys,json; d=json.load(sys.stdin); print(json.dumps(d.get('additional_mounts','not found'), indent=2))"

Check if additional_mounts is set in config


The config is correct in the DB. The mount is defined. But it's not showing up in `/workspace/extra/`.

A few possible reasons:
1. The allowlist check might be blocking it - the allowlist needs to exist AND have the path
2. The container restart spun up a new container but I'm still in a session talking to the old one
3. The mount might need a `--rebuild` to take effect (not just a restart)

Wait - "restarted: 1, rebuilt: false" - maybe the mount changes require a rebuild? Let me suggest `ncl groups restart --id ag-1779666729747-9n7kga --rebuild`.
Actually, looking at the module-cli docs, rebuilding is likely necessary for mount configuration changes since it affects the container setup. Let me request a rebuild with that flag.


<message to="telegram-mg-17796">Config is set correctly but the mount isn't appearing. Mounts need a full rebuild to take effect — try:

```
ncl groups restart --id ag-1779666729747-9n7kga --rebuild --message "Add projects mount"
```

This will take a bit longer than a regular restart.</message>


<context timezone="America/Chicago" />
<message id="1054" from="unknown:agent:ag-1779666729747-9n7kga" sender="system" time="Jul 7, 2026, 8:08 AM">Add projects mount</message>


Check if projects mount appeared after rebuild


ls /workspace/extra/projects/ 2>/dev/null && echo "MOUNTED" || echo "NOT MOUNTED"

Check projects mount specifically


NOT MOUNTED


<context timezone="America/Chicago" />
<message id="1058" from="unknown:agent:ag-1779666729747-9n7kga" sender="Unknown" time="Jul 7, 2026, 8:09 AM">Gemini is unavailable right now, so I am switching to OpenAI for this reply.</message>


<context timezone="America/Chicago" />
<message id="1060" from="unknown:agent:ag-1779666729747-9n7kga" sender="Unknown" time="Jul 7, 2026, 8:09 AM">OpenAI is unavailable too, so I am switching to Anthropic for this reply.</message>


Still not mounted after a rebuild. Let me investigate more carefully.

The Explore agent found that mounts are validated against the allowlist at `~/.config/nanoclaw/mount-allowlist.json`. Did James create that file? He ran the mkdir/cat command I gave him before the second restart. Let me check if there's any way to verify.

Actually - the allowlist file needs to exist on the HOST at `~/.config/nanoclaw/mount-allowlist.json`. The Explore agent said:
- "The allowlist file must contain..."
- "stored OUTSIDE the project root and never mounted into containers"
- "Validation happens at spawn time — invalid mounts are silently dropped with warnings, container still starts"

So if the allowlist doesn't allow the path, the mount just gets silently dropped and the container starts anyway. That would explain why everything seems fine but the mount isn't there. I'm not even sure James actually ran the allowlist creation command before the restart, and I can't see the nanoclaw logs from inside the container to check if there were validation warnings. I should ask him to verify the allowlist file exists and check for any nanoclaw logs about mount validation.


<message to="telegram-mg-17796">Still not appearing — the mount is being silently dropped, which usually means the allowlist check isn't passing. Can you verify the allowlist file was created? Run:

```
cat ~/.config/nanoclaw/mount-allowlist.json
```

Should show the JSON with both paths. If it's missing or empty, the mount command didn't run before the restart.</message>


<context timezone="America/Chicago" />
<message id="1058" from="unknown:agent:ag-1779666729747-9n7kga" sender="Unknown" time="Jul 7, 2026, 8:09 AM">Gemini is unavailable right now, so I am switching to OpenAI for this reply.</message>
<context timezone="America/Chicago" />
<message id="1060" from="unknown:agent:ag-1779666729747-9n7kga" sender="Unknown" time="Jul 7, 2026, 8:09 AM">OpenAI is unavailable too, so I am switching to Anthropic for this reply.</message>


These messages are from my own container (system messages about model switching), not from James. These are internal system notifications. I should just wait for James to reply about the allowlist.


<internal>
Those are internal system messages from my container switching models. Nothing to act on — just waiting for James to check the allowlist file.
</internal>


<context timezone="America/Chicago" />
<message id="1062" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:16 AM">I was thinking that we have 3 current frontier model LLM subscriptions ($20/mo plan for Claude, ChatGPT (codex), and Gemini (Antigravity) and we also have LM studio installed locally so we could also send work there. We also have in the CodeBar-ESP32 project a way to see how much of the 5h and 7d quota is left. Maybe we should integrate that so into our portfolio board in some way so that the planning tasks and escalation goes to the more capable models and the grunt or easy work goes to other models. We already have an escalate skill that might be the right primitive for this. Please come up with a plan or tell me if that's for the backlog. One test case for this could be the thorny UI issue in RoadSense?</message>


This is an interesting idea from James. He's suggesting integrating model/quota awareness into the portfolio board and agent routing. Let me think through this:

**The idea:**
- James has 4 LLM subscriptions/access points:
  1. Claude (Anthropic) - $20/mo, 5h/7d quota visible via CodexBar-ESP32
  2. ChatGPT/Codex (OpenAI) - $20/mo
  3. Gemini (via "Antigravity") - $20/mo
  4. LM Studio (local, free)
- Plus the CodexBar-ESP32 which shows quota usage
- He wants to route work based on task complexity and quota availability—pushing complex planning to capable models while offloading routine work to cheaper or local options when quotas run low.

There's an existing "escalate" skill that might already handle some of this routing. The real question is whether this is worth building now or if it's better as a future enhancement—quota management at these price points does matter, and preventing important work from getting blocked by exhausted quotas has genuine value, though the implementation complexity depends on how tightly we'd need to integrate quota tracking with the routing logic. The RoadSense display bug would be a solid test case, but it depends on getting the mount working first. I'm thinking the right approach is to tackle this in phases: finish the mount setup now, then implement the model routing through a lightweight wrapper around the CodexBar quota API rather than building something complex. Before diving into implementation though, I need to clarify a few things—how to access the quota data, what the escalate skill actually does, and whether the LM Studio API is reachable from the container—so I can recommend whether this should be planned as a near-term task or spec'd out more fully.

I notice James has moved on to a new question, so I should address that while flagging that the mount issue is still unresolved if he wants to circle back to it.

For the model routing concept, I'm sketching out a tiered system where Claude handles the complex reasoning and planning, mid-tier models like Gemini or GPT-4 take on bulk extraction and research tasks, and lighter models handle simple formatting and classification. The escalate skill already covers routing up to Claude, but what's missing is the ability to route down to cheaper models and switch based on quota constraints.

Honestly though, this feels like a nice-to-have optimization rather than something urgent. The real payoff only materializes if quota is consistently tight and there are enough routine tasks to justify the complexity. For James's immediate situation, the bigger priorities are getting the projects mount working, running that congressional-trading backtest, and resolving the portfolio card confirmations. I should suggest putting the model routing idea on the backlog for now.

Before designing any routing system, I need to understand the CodexBar data access situation first—that's the blocking question that'll inform whether this optimization even makes sense.


<message to="telegram-mg-17796">Good idea, and the instinct is right — but I'd put the *integration* in the backlog for now and here's why: the routing logic is straightforward, but the missing piece is a reliable way to read live quota data from inside my container. CodexBar-ESP32 displays it on your desk, but I'd need to query it programmatically (either the Anthropic usage API, or a small local endpoint CodexBar-ESP32 could expose). Once that data is readable, the routing layer is simple: planning/hard thinking → Claude, bulk extraction/research → Gemini or GPT-4, simple formatting/classification → LM Studio.

The escalate skill is the right primitive for upward escalation. What's missing is the inverse — a "delegate down" path — plus a quota-awareness hook that triggers it automatically.

**The RoadSense UI bug is actually a great first test case, but it's blocked on the mount working first.** Once I can see the repo, I can look at the display bug and we'd have a concrete task to route: Claude handles diagnosis and fix design, maybe LM Studio handles the summary/write-up.

I'll add this to the backlog. The one thing worth answering when you have a moment: does CodexBar-ESP32 expose the quota numbers via any local endpoint or file, or does it only display them on the hardware?</message>


<context timezone="America/Chicago" />
<message id="1064" from="telegram-mg-17796" sender="James Lopez" time="Jul 7, 2026, 8:42 AM">The CodexBar-esp32 project has an endpoint that’s already running, its local python that is executed on this machine. The esp32 then is then rendering UI to chart that. My point is that we could listen or poll that same endpoint to decide which model and effort level to use for escalation and also to know when the usage quota is reset and to know when the usage is below average for a smooth burn down and “excess” quota could be used to make progress on our various projects</message>