Summary

• Fix exec allowlist not matching entries in agents.main when triggered via chat/Discord
• When createExecTool was called without explicit agentId (e.g., from bash-command.ts), the allowlist lookup used "default" instead of deriving the agent from sessionKey
• User's allowlist entries in agents.main were never matched, causing repeated approval prompts

Root Cause

In bash-command.ts:333, createExecTool was called with sessionKey but NOT agentId:

const execTool = createExecTool({
  scopeKey: CHAT_BASH_SCOPE_KEY,
  sessionKey: params.sessionKey,  // ← sessionKey passed
  // agentId NOT passed!
});

In bash-tools.exec.ts, the allowlist lookup used defaults?.agentId:

const approvals = resolveExecApprovals(defaults?.agentId, ...);

With agentId undefined, resolveExecApprovalsFromFile fell back to:

const agentKey = params.agentId ?? "default";

This looked up agents.default instead of agents.main, missing all user allowlist entries.

Fix

Derive agentId from sessionKey if not explicitly provided:

const agentId = defaults?.agentId ?? resolveAgentIdFromSessionKey(defaults?.sessionKey);

Then use the derived agentId in all allowlist operations.

Test plan

• pnpm test src/agents/bash-tools.test.ts passes (16 tests)
• pnpm test src/infra/exec-approvals.test.ts passes (15 tests)
• Manual test: trigger exec from Discord with allowlist entries in agents.main

🤖 Generated with Claude Code