@townco/agent 0.1.51 → 0.1.52

package/dist/acp-server/cli.d.ts

@@ -1,5 +1,3 @@
 import type { AgentDefinition } from "../definition";
 import { type AgentRunner } from "../runner";
-export declare function makeStdioTransport(
-	agent: AgentRunner | AgentDefinition,
-): void;
+export declare function makeStdioTransport(agent: AgentRunner | AgentDefinition): void;

package/dist/acp-server/index.js

@@ -1,2 +1,7 @@
+import { initializeOpenTelemetryFromEnv } from "../telemetry/setup.js";
+// Initialize OpenTelemetry when this module is imported (if enabled)
+if (process.env.ENABLE_TELEMETRY === "true") {
+    initializeOpenTelemetryFromEnv();
+}
 export { makeStdioTransport } from "./cli";
 export { makeHttpTransport } from "./http";

package/dist/check-jaeger.d.ts

@@ -0,0 +1,5 @@
+/**
+ * Quick script to verify Jaeger connectivity
+ * Run with: bun check-jaeger.ts
+ */
+export {};

package/dist/check-jaeger.js

@@ -0,0 +1,82 @@
+/**
+ * Quick script to verify Jaeger connectivity
+ * Run with: bun check-jaeger.ts
+ */
+export {}; // Make this a module for top-level await
+console.log("🔍 Checking Jaeger connectivity...\n");
+// Check if Jaeger collector is accepting OTLP on gRPC port
+const checkPort = async (port, protocol) => {
+    try {
+        const net = await import("node:net");
+        const socket = new net.Socket();
+        return new Promise((resolve) => {
+            socket.setTimeout(2000);
+            socket.on("connect", () => {
+                console.log(`✅ ${protocol} port ${port} is accepting connections`);
+                socket.destroy();
+                resolve(true);
+            });
+            socket.on("timeout", () => {
+                console.log(`❌ ${protocol} port ${port} timed out`);
+                socket.destroy();
+                resolve(false);
+            });
+            socket.on("error", (error) => {
+                console.log(`❌ ${protocol} port ${port} not reachable: ${error.message}`);
+                resolve(false);
+            });
+            socket.connect(port, "localhost");
+        });
+    }
+    catch (error) {
+        console.log(`❌ Error checking ${protocol} port ${port}:`, error);
+        return false;
+    }
+};
+// Check Jaeger ports
+console.log("Checking Jaeger ports:");
+console.log("─────────────────────────────");
+await checkPort(4317, "OTLP gRPC"); // Collector OTLP gRPC
+await checkPort(4318, "OTLP HTTP"); // Collector OTLP HTTP
+await checkPort(16686, "UI       "); // Query UI
+console.log("\n🔍 Checking Docker container...\n");
+// Check if Jaeger container is running
+try {
+    const { execSync } = await import("node:child_process");
+    const output = execSync("docker ps --filter name=jaeger --format '{{.Status}}'", {
+        encoding: "utf-8",
+    }).trim();
+    if (output) {
+        console.log(`✅ Jaeger container is running: ${output}`);
+        // Check container logs for OTLP
+        try {
+            const logs = execSync("docker logs jaeger 2>&1 | tail -20", {
+                encoding: "utf-8",
+            });
+            console.log("\n📋 Recent container logs:");
+            console.log("─────────────────────────────");
+            console.log(logs);
+        }
+        catch (e) {
+            console.log("⚠️  Could not fetch container logs");
+        }
+    }
+    else {
+        console.log("❌ No Jaeger container running with name 'jaeger'");
+        console.log("\n💡 Start Jaeger with:");
+        console.log("docker run -d --name jaeger \\");
+        console.log("  -e COLLECTOR_OTLP_ENABLED=true \\");
+        console.log("  -p 16686:16686 \\");
+        console.log("  -p 4317:4317 \\");
+        console.log("  -p 4318:4318 \\");
+        console.log("  jaegertracing/all-in-one:latest");
+    }
+}
+catch (error) {
+    console.log("⚠️  Could not check Docker container:", error);
+}
+console.log("\n🎯 Next steps:");
+console.log("─────────────────────────────");
+console.log("1. Make sure ports above show ✅");
+console.log("2. Run the test: ENABLE_TELEMETRY=true bun test-telemetry.ts");
+console.log("3. Check UI: http://localhost:16686");

package/dist/run-subagents.d.ts

@@ -0,0 +1,9 @@
+#!/usr/bin/env bun
+/**
+ * Helper script to test makeSubagentsTool
+ *
+ * Usage:
+ *   bun packages/agent/run-subagents.ts
+ *   bun packages/agent/run-subagents.ts "your custom query here"
+ */
+export {};

package/dist/run-subagents.js

@@ -0,0 +1,110 @@
+#!/usr/bin/env bun
+/**
+ * Helper script to test makeSubagentsTool
+ *
+ * Usage:
+ *   bun packages/agent/run-subagents.ts
+ *   bun packages/agent/run-subagents.ts "your custom query here"
+ */
+import { makeSubagentsTool } from "./utils";
+import { makeRunnerFromDefinition } from "./runner";
+// Default query if none provided
+const defaultQuery = "Can you search for news about artificial intelligence?";
+const userQuery = process.argv[2] || defaultQuery;
+console.log("🧪 Testing makeSubagentsTool\n");
+console.log("Query:", userQuery);
+console.log("─".repeat(60));
+// Create a simple subagent definition
+const simpleSubagent = {
+    model: "claude-sonnet-4-5-20250929",
+    systemPrompt: "You are a helpful research assistant. Provide concise, informative responses.",
+    tools: [
+        "web_search",
+        "todo_write",
+    ],
+    mcps: [],
+};
+// Create the coordinator agent with subagent tool
+const coordinatorAgent = {
+    model: "claude-sonnet-4-5-20250929",
+    systemPrompt: `You are a coordinator agent that delegates tasks to specialized subagents.
+When you receive a query, evaluate if it needs to be delegated to a subagent.
+If so, use the Task tool with the appropriate subagent.`,
+    tools: [
+        makeSubagentsTool([
+            {
+                agentName: "researcher",
+                description: "Use this agent to research topics, search the web, and gather information",
+                path: import.meta.filename, // Points to itself as a simple test
+            },
+            {
+                agentName: "simple",
+                description: "Use this for general tasks that don't require specialized tools",
+                path: import.meta.filename,
+            },
+        ]),
+    ],
+    mcps: [],
+};
+// Run the test
+async function runTest() {
+    console.log("\n📝 Creating runner...");
+    const runner = makeRunnerFromDefinition(coordinatorAgent);
+    console.log("🚀 Running query...\n");
+    try {
+        const stream = runner.invoke({
+            prompt: [
+                {
+                    type: "text",
+                    text: userQuery,
+                },
+            ],
+            sessionId: "test-session",
+            messageId: "msg-1",
+        });
+        console.log("📊 Stream output:");
+        console.log("─".repeat(60));
+        let messageCount = 0;
+        let toolCallCount = 0;
+        let lastTextContent = "";
+        for await (const chunk of stream) {
+            messageCount++;
+            // Pretty print different types of chunks
+            if (chunk.type === "agent_message_chunk") {
+                const content = chunk.content;
+                if (content.type === "text" && content.text) {
+                    process.stdout.write(content.text);
+                    lastTextContent += content.text;
+                }
+                else if (content.type === "tool_use") {
+                    toolCallCount++;
+                    console.log(`\n\n🔧 Tool Call #${toolCallCount}: ${content.name}`);
+                    console.log("   Input:", JSON.stringify(content.input, null, 2).split('\n').join('\n   '));
+                }
+            }
+            else if (chunk.type === "tool_result") {
+                console.log("\n\n✅ Tool Result:");
+                console.log("   ", JSON.stringify(chunk, null, 2).split('\n').join('\n   '));
+            }
+            else {
+                // Print other chunk types for debugging
+                console.log("\n\n📦 Chunk:", JSON.stringify(chunk, null, 2));
+            }
+        }
+        console.log("\n\n" + "─".repeat(60));
+        console.log("✨ Test completed!");
+        console.log(`   Total chunks: ${messageCount}`);
+        console.log(`   Tool calls: ${toolCallCount}`);
+        console.log("─".repeat(60));
+    }
+    catch (error) {
+        console.error("\n❌ Error during test:");
+        console.error(error);
+        process.exit(1);
+    }
+}
+// Run the test
+runTest().catch((error) => {
+    console.error("Fatal error:", error);
+    process.exit(1);
+});

package/dist/runner/index.d.ts

@@ -1,6 +1,4 @@
 import type { AgentDefinition } from "../definition";
 import { type AgentRunner } from "./agent-runner";
 export type { AgentRunner };
-export declare const makeRunnerFromDefinition: (
-	definition: AgentDefinition,
-) => AgentRunner;
+export declare const makeRunnerFromDefinition: (definition: AgentDefinition) => AgentRunner;

package/dist/runner/langchain/custom-stream-types.d.ts

@@ -0,0 +1,36 @@
+import { z } from "zod";
+/**
+ * Custom stream events emitted by subagent tools via config.writer
+ */
+export declare const SubagentToolCallEventSchema: z.ZodObject<{
+    type: z.ZodLiteral<"tool_call">;
+    toolName: z.ZodString;
+}, z.core.$strip>;
+export declare const SubagentMessageEventSchema: z.ZodObject<{
+    type: z.ZodLiteral<"message">;
+    text: z.ZodString;
+}, z.core.$strip>;
+export declare const SubagentEventSchema: z.ZodDiscriminatedUnion<[z.ZodObject<{
+    type: z.ZodLiteral<"tool_call">;
+    toolName: z.ZodString;
+}, z.core.$strip>, z.ZodObject<{
+    type: z.ZodLiteral<"message">;
+    text: z.ZodString;
+}, z.core.$strip>], "type">;
+export type SubagentToolCallEvent = z.infer<typeof SubagentToolCallEventSchema>;
+export type SubagentMessageEvent = z.infer<typeof SubagentMessageEventSchema>;
+export type SubagentEvent = z.infer<typeof SubagentEventSchema>;
+/**
+ * Wrapper for subagent events that includes the parent tool call ID
+ */
+export declare const CustomStreamChunkSchema: z.ZodObject<{
+    parentToolCallId: z.ZodString;
+    event: z.ZodDiscriminatedUnion<[z.ZodObject<{
+        type: z.ZodLiteral<"tool_call">;
+        toolName: z.ZodString;
+    }, z.core.$strip>, z.ZodObject<{
+        type: z.ZodLiteral<"message">;
+        text: z.ZodString;
+    }, z.core.$strip>], "type">;
+}, z.core.$strip>;
+export type CustomStreamChunk = z.infer<typeof CustomStreamChunkSchema>;

package/dist/runner/langchain/custom-stream-types.js

@@ -0,0 +1,23 @@
+import { z } from "zod";
+/**
+ * Custom stream events emitted by subagent tools via config.writer
+ */
+export const SubagentToolCallEventSchema = z.object({
+    type: z.literal("tool_call"),
+    toolName: z.string(),
+});
+export const SubagentMessageEventSchema = z.object({
+    type: z.literal("message"),
+    text: z.string(),
+});
+export const SubagentEventSchema = z.discriminatedUnion("type", [
+    SubagentToolCallEventSchema,
+    SubagentMessageEventSchema,
+]);
+/**
+ * Wrapper for subagent events that includes the parent tool call ID
+ */
+export const CustomStreamChunkSchema = z.object({
+    parentToolCallId: z.string(),
+    event: SubagentEventSchema,
+});

package/dist/runner/langchain/index.js

@@ -364,9 +364,12 @@ export class LangchainAgent {
                             }
                             // Create tool span within the invocation context
                             // This makes the tool span a child of the invocation span
+                            const toolInputJson = JSON.stringify(toolCall.args);
                             const toolSpan = context.with(invocationContext, () => telemetry.startSpan("agent.tool_call", {
                                 "tool.name": toolCall.name,
                                 "tool.id": toolCall.id,
+                                "tool.input": toolInputJson,
+                                "agent.session_id": req.sessionId,
                             }));
                             this.toolSpans.set(toolCall.id, toolSpan);
                             telemetry.log("info", `Tool call started: ${toolCall.name}`, {
@@ -553,6 +556,10 @@ export class LangchainAgent {
                             // End telemetry span for this tool call
                             const toolSpan = this.toolSpans.get(aiMessage.tool_call_id);
                             if (toolSpan) {
+                                // Add tool output to span before ending
+                                telemetry.setSpanAttributes(toolSpan, {
+                                    "tool.output": aiMessage.content,
+                                });
                                 telemetry.log("info", "Tool call completed", {
                                     toolCallId: aiMessage.tool_call_id,
                                 });

package/dist/runner/langchain/otel-callbacks.js

@@ -1,4 +1,4 @@
-import { context } from "@opentelemetry/api";
+import { context, trace } from "@opentelemetry/api";
 import { telemetry } from "../../telemetry/index.js";
 /**
  * OpenTelemetry callback handler for LangChain LLM calls.
@@ -45,6 +45,38 @@ function extractSystemPrompt(messages) {
         return undefined;
     }
 }
+/**
+ * Serializes LLM output to a string for logging.
+ * Preserves the raw provider format (content blocks, tool_calls, etc.)
+ */
+function serializeOutput(output) {
+    try {
+        const generations = output.generations.flat();
+        const serialized = generations.map((gen) => {
+            // ChatGeneration has a message property with the full AIMessage
+            const chatGen = gen;
+            if (chatGen.message) {
+                const msg = chatGen.message;
+                const result = {
+                    role: msg._getType?.() ?? "assistant",
+                    content: msg.content, // Keep as-is: string or ContentBlock[]
+                };
+                // Include tool_calls if present (LangChain's normalized format)
+                const aiMsg = msg;
+                if (aiMsg.tool_calls && aiMsg.tool_calls.length > 0) {
+                    result.tool_calls = aiMsg.tool_calls;
+                }
+                return result;
+            }
+            // Fallback for non-chat generations
+            return { text: gen.text };
+        });
+        return JSON.stringify(serialized);
+    }
+    catch (error) {
+        return `[Error serializing output: ${error}]`;
+    }
+}
 /**
  * Creates OpenTelemetry callback handlers for LangChain LLM calls.
  * These handlers instrument model invocations with OTEL spans and record token usage.
@@ -84,6 +116,18 @@ export function makeOtelCallbacks(opts) {
             }));
             if (span) {
                 spansByRunId.set(runId, span);
+                // Emit log for LLM request with trace context
+                const spanContext = span.spanContext();
+                telemetry.log("info", "LLM Request", {
+                    "gen_ai.operation.name": "chat",
+                    "gen_ai.provider.name": opts.provider,
+                    "gen_ai.request.model": opts.model,
+                    "gen_ai.input.messages": serializedMessages,
+                    "langchain.run_id": runId,
+                    // Include trace context for correlation
+                    trace_id: spanContext.traceId,
+                    span_id: spanContext.spanId,
+                });
             }
         },
         /**
@@ -105,6 +149,28 @@ export function makeOtelCallbacks(opts) {
                         : 0);
                 telemetry.recordTokenUsage(inputTokens, outputTokens, span);
             }
+            // Serialize output and attach to span
+            const serializedOutput = serializeOutput(output);
+            telemetry.setSpanAttributes(span, {
+                "gen_ai.output.messages": serializedOutput,
+            });
+            // Emit log for LLM response with trace context
+            const spanContext = span.spanContext();
+            telemetry.log("info", "LLM Response", {
+                "gen_ai.operation.name": "chat",
+                "gen_ai.output.messages": serializedOutput,
+                "langchain.run_id": runId,
+                // Include token usage in log
+                ...(tokenUsage
+                    ? {
+                        "gen_ai.usage.input_tokens": tokenUsage.inputTokens ?? 0,
+                        "gen_ai.usage.output_tokens": tokenUsage.outputTokens ?? 0,
+                    }
+                    : {}),
+                // Include trace context for correlation
+                trace_id: spanContext.traceId,
+                span_id: spanContext.spanId,
+            });
             telemetry.endSpan(span);
             spansByRunId.delete(runId);
         },

package/dist/runner/langchain/tools/bash.d.ts

@@ -0,0 +1,14 @@
+import { z } from "zod";
+export declare function makeBashTool(workingDirectory?: string): import("langchain").DynamicStructuredTool<z.ZodObject<{
+    command: z.ZodString;
+    timeout: z.ZodOptional<z.ZodNumber>;
+    description: z.ZodOptional<z.ZodString>;
+}, z.core.$strip>, {
+    command: string;
+    timeout?: number | undefined;
+    description?: string | undefined;
+}, {
+    command: string;
+    timeout?: number | undefined;
+    description?: string | undefined;
+}, unknown>;

package/dist/runner/langchain/tools/bash.js

@@ -0,0 +1,135 @@
+import { spawn } from "node:child_process";
+import { once } from "node:events";
+import * as path from "node:path";
+import { SandboxManager, } from "@anthropic-ai/sandbox-runtime";
+import { tool } from "langchain";
+import { z } from "zod";
+/**
+ * Lazily initialize Sandbox Runtime with write access limited to workingDirectory.
+ */
+let initialized = false;
+async function ensureSandbox(workingDirectory) {
+    if (initialized)
+        return;
+    const cfg = {
+        network: {
+            // No outbound network needed for basic bash commands; block by default.
+            allowedDomains: [],
+            deniedDomains: [],
+        },
+        filesystem: {
+            // Allow writes only within the configured sandbox directory.
+            allowWrite: [workingDirectory],
+            denyWrite: [],
+            // Optional: harden reads a bit (deny common sensitive dirs)
+            denyRead: ["~/.ssh", "~/.gnupg", "/etc/ssh"],
+        },
+    };
+    await SandboxManager.initialize(cfg);
+    initialized = true;
+}
+/** Run a command string inside the sandbox, returning { stdout, stderr, code, timedOut }. */
+async function runSandboxed(cmd, cwd, timeoutMs) {
+    const wrapped = await SandboxManager.wrapWithSandbox(cmd);
+    const child = spawn(wrapped, { shell: true, cwd });
+    const stdout = [];
+    const stderr = [];
+    child.stdout?.on("data", (d) => stdout.push(Buffer.from(d)));
+    child.stderr?.on("data", (d) => stderr.push(Buffer.from(d)));
+    let timedOut = false;
+    let timeoutHandle;
+    // Set up timeout if specified
+    if (timeoutMs !== undefined && timeoutMs > 0) {
+        timeoutHandle = setTimeout(() => {
+            timedOut = true;
+            child.kill("SIGTERM");
+            // If process doesn't exit after SIGTERM, force kill after 1 second
+            setTimeout(() => {
+                if (!child.killed) {
+                    child.kill("SIGKILL");
+                }
+            }, 1000);
+        }, timeoutMs);
+    }
+    const [code] = (await once(child, "exit"));
+    if (timeoutHandle) {
+        clearTimeout(timeoutHandle);
+    }
+    return {
+        stdout: Buffer.concat(stdout),
+        stderr: Buffer.concat(stderr),
+        code: code ?? 1,
+        timedOut,
+    };
+}
+/** Truncate output if it exceeds the maximum length. */
+function truncateOutput(output, maxLength = 30000) {
+    if (output.length <= maxLength) {
+        return output;
+    }
+    return `${output.slice(0, maxLength)}\n\n... (output truncated, ${output.length - maxLength} characters omitted)`;
+}
+export function makeBashTool(workingDirectory) {
+    const resolvedWd = path.resolve(workingDirectory ?? process.cwd());
+    const bash = tool(async ({ command, timeout, description }) => {
+        await ensureSandbox(resolvedWd);
+        // Validate timeout
+        const DEFAULT_TIMEOUT = 120000; // 2 minutes
+        const MAX_TIMEOUT = 600000; // 10 minutes
+        let timeoutMs = timeout ?? DEFAULT_TIMEOUT;
+        if (timeoutMs > MAX_TIMEOUT) {
+            throw new Error(`Timeout cannot exceed ${MAX_TIMEOUT}ms (10 minutes), got ${timeoutMs}ms`);
+        }
+        if (timeoutMs < 0) {
+            throw new Error(`Timeout must be positive, got ${timeoutMs}ms`);
+        }
+        // Execute the command
+        const startTime = Date.now();
+        const { stdout, stderr, code, timedOut } = await runSandboxed(command, resolvedWd, timeoutMs);
+        const executionTime = Date.now() - startTime;
+        // Convert buffers to strings
+        const stdoutStr = stdout.toString("utf8");
+        const stderrStr = stderr.toString("utf8");
+        // Truncate outputs if necessary
+        const truncatedStdout = truncateOutput(stdoutStr);
+        const truncatedStderr = truncateOutput(stderrStr);
+        // Build result message
+        let result = "";
+        if (timedOut) {
+            result += `Command timed out after ${timeoutMs}ms\n\n`;
+        }
+        if (truncatedStdout) {
+            result += truncatedStdout;
+        }
+        if (truncatedStderr) {
+            if (result)
+                result += "\n\n";
+            result += `STDERR:\n${truncatedStderr}`;
+        }
+        if (!truncatedStdout && !truncatedStderr) {
+            result = "(no output)";
+        }
+        // Add exit code info
+        result += `\n\nExit code: ${code}`;
+        if (description) {
+            result += `\nDescription: ${description}`;
+        }
+        result += `\nExecution time: ${executionTime}ms`;
+        return result;
+    }, {
+        name: "Bash",
+        description: 'Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.\n\nBefore executing the command, please follow these steps:\n\n1. Directory Verification:\n   - If the command will create new directories or files, first use `ls` to verify the parent directory exists and is the correct location\n   - For example, before running "mkdir foo/bar", first use `ls foo` to check that "foo" exists and is the intended parent directory\n\n2. Command Execution:\n   - Always quote file paths that contain spaces with double quotes (e.g., cd "path with spaces/file.txt")\n   - Examples of proper quoting:\n     - cd "/Users/name/My Documents" (correct)\n     - cd /Users/name/My Documents (incorrect - will fail)\n     - python "/path/with spaces/script.py" (correct)\n     - python /path/with spaces/script.py (incorrect - will fail)\n   - After ensuring proper quoting, execute the command.\n   - Capture the output of the command.\n\nUsage notes:\n  - The command argument is required.\n  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).\n  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.\n  - If the output exceeds 30000 characters, output will be truncated before being returned to you.\n  - You can use the `run_in_background` parameter to run the command in the background, which allows you to continue working while the command runs. You can monitor the output using the Bash tool as it becomes available. Never use `run_in_background` to run \'sleep\' as it will return immediately. You do not need to use \'&\' at the end of the command when using this parameter.\n  - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, and `tail`, and use Read to read files.\n - If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` first, which all Claude Code users have pre-installed.\n  - When issuing multiple commands, use the \';\' or \'&&\' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).\n  - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it.\n    <good-example>\n    pytest /foo/bar/tests\n    </good-example>\n    <bad-example>\n    cd /foo/bar && pytest tests\n    </bad-example>\n\n# Committing changes with git\n\nWhen the user asks you to create a new git commit, follow these steps carefully:\n\n1. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following bash commands in parallel, each using the Bash tool:\n  - Run a git status command to see all untracked files.\n  - Run a git diff command to see both staged and unstaged changes that will be committed.\n  - Run a git log command to see recent commit messages, so that you can follow this repository\'s commit message style.\n2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:\n  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).\n  - Check for any sensitive information that shouldn\'t be committed\n  - Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"\n  - Ensure it accurately reflects the changes and their purpose\n3. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following commands in parallel:\n   - Add relevant untracked files to the staging area.\n   - Create the commit with a message ending with:\n   🤖 Generated with [Claude Code](https://claude.ai/code)\n\n   Co-Authored-By: Claude <noreply@anthropic.com>\n   - Run git status to make sure the commit succeeded.\n4. If the commit fails due to pre-commit hook changes, retry the commit ONCE to include these automated changes. If it fails again, it usually means a pre-commit hook is preventing the commit. If the commit succeeds but you notice that files were modified by the pre-commit hook, you MUST amend your commit to include them.\n\nImportant notes:\n- NEVER update the git config\n- NEVER run additional commands to read or explore code, besides git bash commands\n- NEVER use the TodoWrite or Task tools\n- DO NOT push to the remote repository unless the user explicitly asks you to do so\n- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.\n- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit\n- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:\n<example>\ngit commit -m "$(cat <<\'EOF\'\n   Commit message here.\n\n   🤖 Generated with [Claude Code](https://claude.ai/code)\n\n   Co-Authored-By: Claude <noreply@anthropic.com>\n   EOF\n   )"\n</example>\n\n# Creating pull requests\nUse the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.\n\nIMPORTANT: When the user asks you to create a pull request, follow these steps carefully:\n\n1. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:\n   - Run a git status command to see all untracked files\n   - Run a git diff command to see both staged and unstaged changes that will be committed\n   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote\n   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)\n2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request summary\n3. You have the capability to call multiple tools in a single response. When multiple independent pieces of information are requested, batch your tool calls together for optimal performance. ALWAYS run the following commands in parallel:\n   - Create new branch if needed\n   - Push to remote with -u flag if needed\n   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.\n<example>\ngh pr create --title "the pr title" --body "$(cat <<\'EOF\'\n## Summary\n<1-3 bullet points>\n\n## Test plan\n[Checklist of TODOs for testing the pull request...]\n\n🤖 Generated with [Claude Code](https://claude.ai/code)\nEOF\n)"\n</example>\n\nImportant:\n- NEVER update the git config\n- DO NOT use the TodoWrite or Task tools\n- Return the PR URL when you\'re done, so the user can see it\n\n# Other common operations\n- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments',
+        schema: z.object({
+            command: z.string().describe("The command to execute"),
+            timeout: z
+                .number()
+                .optional()
+                .describe("Optional timeout in milliseconds (max 600000)"),
+            description: z
+                .string()
+                .optional()
+                .describe("Clear, concise description of what this command does in 5-10 words, in active voice. Examples:\nInput: ls\nOutput: List files in current directory\n\nInput: git status\nOutput: Show working tree status\n\nInput: npm install\nOutput: Install package dependencies\n\nInput: mkdir foo\nOutput: Create directory 'foo'"),
+        }),
+    });
+    return bash;
+}

package/dist/telemetry/setup.d.ts

@@ -1,7 +1,8 @@
 /**
  * OpenTelemetry provider setup for @townco/agent
- * Initializes the trace provider, exporter, and propagator
+ * Initializes the trace provider, log provider, exporters, and propagator
  */
+import { LoggerProvider } from "@opentelemetry/sdk-logs";
 import { NodeTracerProvider } from "@opentelemetry/sdk-trace-node";
 export interface TelemetrySetupOptions {
     serviceName?: string;
@@ -14,6 +15,7 @@ export interface TelemetrySetupOptions {
  */
 export declare function initializeOpenTelemetry(options?: TelemetrySetupOptions): {
     provider: NodeTracerProvider;
+    loggerProvider: LoggerProvider;
     shutdown: () => Promise<void>;
 };
 /**