MUTATION_TESTING
AgentThe agent package's pure, deterministic core (the chat permission gate, the control-tool plumbing, JSON extraction, and the…
**Navigation**: [Agents package rules](../AGENTS.md) → **Observing LLM Steps and Planning**
Claude Code
$ npx -y skills add nodetool-ai/nodetool --agent claude-code
Cursor
Cursor also loads subagents from .claude/agents, so copy this file there to use it in Cursor.
**Navigation**: [Agents package rules](../AGENTS.md) → **Observing LLM Steps and Planning**
Paths are relative to `packages/agents/` unless they name another package.
The CLI renders a real-time tree view during agent execution:
✓ initialization Starting parallel task planning... ✓ generation Generating parallel plan... ✗ validation Plan validation failed: duplicate step IDs ✓ generation Retry attempt 2/3... ✓ complete Plan created: 5 tasks, 5 steps, 5 parallelizable ◆ Plan (3/5 tasks) ├─ ✓ Task 1: Search sources 3.2s (1/1 steps) ├─ ◐ Task 2: Analyze findings │ ├─ ✓ web_search(query: "AI trends") │ └─ ◐ llm_call └─ ○ Task 3: Write report waiting
All execution events are yielded as `ProcessingMessage`:
| Type | Description | |------|-------------| | `planning_update` | Planning phase progress (initialization, generation, validation, complete) | | `task_update` | Task lifecycle (task_created, step_started, step_completed, step_failed, task_completed) | | `tool_call_update` | Tool invocation with name and args | | `step_result` | Step completion with result or error | | `chunk` | Streaming text output | | `log_update` | Informational log messages | | `llm_call` | Full LLM call details (provider, model, messages, response, tokens, cost, duration) |
# Verbose logging to stderr export NODETOOL_LOG_LEVEL=debug # Log to file export NODETOOL_LOG_FILE=/tmp/agents.log
Span hierarchy (an analyzer agent can read this tree to optimize prompts):
workflow.run
node.process
agent.execute
agent.plan (TaskPlanner.planMultiTask / authorGraph)
llm.chat (BaseProvider.generateMessageTraced)
llm.stream (BaseProvider.generateMessagesTraced)
agent.step (CodeActExecutor.execute)
llm.chat
llm.streamSpan attributes:
Sinks (simultaneous, each on its own SpanProcessor):
# JSONL trace file — one span per line, analyzer-friendly export NODETOOL_TRACE_FILE=/tmp/nodetool-trace.jsonl # Stdout — pretty (human) or json (JSONL) export NODETOOL_TRACE_STDOUT=pretty # or "json" # OpenTelemetry — console (legacy) export OTEL_TRACES_EXPORTER=console export TRACELOOP_DISABLE_BATCH=true # OpenTelemetry — Traceloop cloud export TRACELOOP_API_KEY=your-key # OpenTelemetry — custom OTLP backend (Jaeger, Grafana, etc.) export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
CLI flags pass these through:
nodetool-chat --trace-file trace.jsonl nodetool-chat --trace-stdout pretty nodetool --trace-file trace.jsonl run workflow.ts
Telemetry must be initialized before use:
import { initTelemetry } from "@nodetool-ai/runtime";
await initTelemetry({
traceFile: "trace.jsonl", // optional
stdout: "pretty", // optional: "pretty" | "json" | false
});The CLI calls `initTelemetry()` at startup automatically. The WebSocket server requires env vars to be set before starting.
The web UI renders the same tree view in the chat panel (`ExecutionTree` component). The `TracePanel` provides a detailed event inspector with token counts, costs, and full request/response payloads.
Open-source AI film studio · agent + node workflows Direct AI films, shot by shot. Start with one sentence. The agent writes the story, draws a still for every shot, and cuts the clips on a timeline.
The agent package's pure, deterministic core (the chat permission gate, the control-tool plumbing, JSON extraction, and the…
**Navigation**: [Agents package rules](../AGENTS.md) → **Capabilities and tool sources**
**Navigation**: [Agents package rules](../AGENTS.md) → **Running Agents from CLI**
**Navigation**: [Agents package rules](../AGENTS.md) → **CodeAct Execution**
**Navigation**: [Agents package rules](../AGENTS.md) → **Eval suites**
**Navigation**: [Agents package rules](../AGENTS.md) → **Graph authoring**
Agent for managing AI prompts on prompts.chat - search, save, improve, and organize your prompt library.
정밀(strict) 모드 1단계 진단 에이전트. 글 전체를 한 번에 보고 "가장 지배적인 AI 티 패턴 3~6개"를 taxonomy ID와 함께 진단한다. 불안정한 span 열거(0↔18개로 요동) 대신 "무엇이 이 글을…
Topic Clusters curator for the Claude Blog Brain. Maintains and answers from the Topic Clusters theme of the brain, grounded in…
Optional gallery research helper. Use when a caller wants to find references, explore styles, build a mood board, or needs…