@townco/agent 0.1.52 → 0.1.53

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

@@ -1,135 +0,0 @@
-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/test-telemetry.d.ts

@@ -1,5 +0,0 @@
-/**
- * Simple test script to verify OpenTelemetry is working
- * Run with: ENABLE_TELEMETRY=true DEBUG_TELEMETRY=true bun test-telemetry.ts
- */
-export {};

package/dist/test-telemetry.js

@@ -1,88 +0,0 @@
-/**
- * Simple test script to verify OpenTelemetry is working
- * Run with: ENABLE_TELEMETRY=true DEBUG_TELEMETRY=true bun test-telemetry.ts
- */
-import { makeRunnerFromDefinition } from "./runner/index.js";
-import { configureTelemetry } from "./telemetry/index.js";
-// Initialize OpenTelemetry
-console.log("🔧 Initializing OpenTelemetry...");
-const { NodeTracerProvider } = await import("@opentelemetry/sdk-trace-node");
-const { BatchSpanProcessor } = await import("@opentelemetry/sdk-trace-base");
-const { OTLPTraceExporter } = await import("@opentelemetry/exporter-trace-otlp-grpc");
-const { Resource } = await import("@opentelemetry/resources");
-const { ATTR_SERVICE_NAME } = await import("@opentelemetry/semantic-conventions");
-const serviceName = "test-agent";
-const otlpEndpoint = process.env.OTEL_EXPORTER_OTLP_ENDPOINT ?? "http://localhost:4317";
-console.log(`📡 Service: ${serviceName}`);
-console.log(`📡 Endpoint: ${otlpEndpoint}`);
-const provider = new NodeTracerProvider({
-    resource: new Resource({
-        [ATTR_SERVICE_NAME]: serviceName,
-    }),
-});
-const exporter = new OTLPTraceExporter({
-    url: otlpEndpoint,
-});
-provider.addSpanProcessor(new BatchSpanProcessor(exporter));
-provider.register();
-configureTelemetry({
-    enabled: true,
-    serviceName,
-    attributes: {
-        "test.run": "true",
-    },
-});
-console.log("✅ OpenTelemetry initialized\n");
-// Create a simple test agent
-console.log("🤖 Creating test agent...");
-const runner = makeRunnerFromDefinition({
-    model: "claude-sonnet-4-5-20250929",
-    systemPrompt: "You are a helpful assistant. Keep responses brief.",
-    tools: ["get_weather"],
-});
-console.log("✅ Agent created\n");
-// Run a simple test invocation
-console.log("🚀 Running test invocation...");
-const result = runner.invoke({
-    prompt: [
-        {
-            type: "text",
-            text: "What's the weather like in San Francisco?",
-        },
-    ],
-    sessionId: "test-session-123",
-    messageId: "test-msg-1",
-});
-console.log("📨 Processing response...\n");
-let tokenCount = 0;
-let toolCalls = 0;
-for await (const chunk of result) {
-    if (chunk.sessionUpdate === "tool_call") {
-        console.log(`🔧 Tool called: ${chunk.title}`);
-        toolCalls++;
-    }
-    else if (chunk.sessionUpdate === "agent_message_chunk") {
-        if (chunk.content.type === "text") {
-            process.stdout.write(chunk.content.text);
-        }
-        if (chunk._meta &&
-            "tokenUsage" in chunk._meta &&
-            chunk._meta.tokenUsage &&
-            typeof chunk._meta.tokenUsage === "object" &&
-            "outputTokens" in chunk._meta.tokenUsage) {
-            tokenCount += chunk._meta.tokenUsage.outputTokens ?? 0;
-        }
-    }
-}
-console.log("\n\n✅ Test completed!");
-console.log(`📊 Stats: ${toolCalls} tool calls, ~${tokenCount} output tokens`);
-// Force flush before exit
-console.log("\n⏳ Flushing telemetry data...");
-await provider.forceFlush();
-console.log("✅ Telemetry flushed!");
-console.log("\n🎯 Check Jaeger UI at: http://localhost:16686");
-console.log(`   Service: ${serviceName}`);
-console.log(`   Look for "agent.invoke" spans`);
-// Give a moment for final flush
-await new Promise((resolve) => setTimeout(resolve, 1000));
-process.exit(0);