From 0cad3bf2ca061a67adaa24dc8bf9e29041f6734b Mon Sep 17 00:00:00 2001 From: ismeth Date: Fri, 20 Feb 2026 14:35:52 +0100 Subject: [PATCH] chore(athena): remove dead exports and unused barrel file --- src/agents/athena/agent.ts | 10 +++++----- src/agents/athena/index.ts | 3 --- src/agents/builtin-agents/council-member-agents.ts | 2 +- 3 files changed, 6 insertions(+), 9 deletions(-) delete mode 100644 src/agents/athena/index.ts diff --git a/src/agents/athena/agent.ts b/src/agents/athena/agent.ts index d850e003..59f97f6d 100644 --- a/src/agents/athena/agent.ts +++ b/src/agents/athena/agent.ts @@ -34,7 +34,7 @@ const ATHENA_SYSTEM_PROMPT = `You are Athena, a multi-model council orchestrator ## CRITICAL: Council Member Selection (Your First Action) -Before launching council members, you MUST present a multi-select prompt using the Question tool so the user can choose which council members to consult. The "Registered Council Members" section at the end of this prompt lists all available members. +Before launching council members, you MUST present a multi-select prompt using the Question tool so the user can choose which council members to consult. Your available council members are listed below. Use the Question tool like this: @@ -44,7 +44,7 @@ Question({ header: "Council Members", options: [ { label: "All Members", description: "Consult all configured council members" }, - ...one option per member from the "Registered Council Members" section below + ...one option per member from your available council members listed below ], multiple: true }] @@ -70,19 +70,19 @@ You are an ORCHESTRATOR, not an analyst. Your council members do the analysis. Y Step 1: Present the Question tool multi-select for council member selection (see above). Step 2: Resolve the selected member list: -- If user selected "All Members", resolve to every member from the "Registered Council Members" section. +- If user selected "All Members", resolve to every member from your available council members listed below. - Otherwise resolve to the explicitly selected member labels. Step 3: Launch each selected member via the task tool with run_in_background=true: - For each selected member, call the task tool with: - - subagent_type: the exact member name from "Registered Council Members" (e.g., "Council: Claude Opus 4.6") + - subagent_type: the exact member name from your available council members listed below (e.g., "Council: Claude Opus 4.6") - run_in_background: true - prompt: the user's original question - load_skills: [] - description: the member name (e.g., "Council: Claude Opus 4.6") - Launch ALL selected members FIRST (one task call per member, all in parallel) before collecting any results. - Track every returned task_id and member mapping. -- IMPORTANT: Use EXACTLY the subagent_type names listed in "Registered Council Members" — they must match precisely. +- IMPORTANT: Use EXACTLY the subagent_type names listed in your available council members below — they must match precisely. Step 4: Collect results with progress using background_wait: - After launching all members, call background_wait(task_ids=[...all task IDs...]) with ONLY the task_ids parameter. diff --git a/src/agents/athena/index.ts b/src/agents/athena/index.ts deleted file mode 100644 index f5087ade..00000000 --- a/src/agents/athena/index.ts +++ /dev/null @@ -1,3 +0,0 @@ -export * from "./agent" -export * from "./council-member-agent" - diff --git a/src/agents/builtin-agents/council-member-agents.ts b/src/agents/builtin-agents/council-member-agents.ts index 5ec6e6f9..df69715a 100644 --- a/src/agents/builtin-agents/council-member-agents.ts +++ b/src/agents/builtin-agents/council-member-agents.ts @@ -10,7 +10,7 @@ export const COUNCIL_MEMBER_KEY_PREFIX = "Council: " /** * Generates a stable agent registration key from a council member's name. */ -export function getCouncilMemberAgentKey(member: CouncilMemberConfig): string { +function getCouncilMemberAgentKey(member: CouncilMemberConfig): string { return `${COUNCIL_MEMBER_KEY_PREFIX}${member.name}` }