aegiscode 6.1.0 → 6.2.0

package/README.md

@@ -9,6 +9,7 @@ an editor — built on the same two shared pieces and no others:
 | `client/aegis.js` | The thin transport. Holds the API key, speaks HTTP/SSE. No brain logic. |
 | `mcp/tools.js` | The tool registry — names, JSON schemas, result formatting. |
 | `desktop/renderer/usage.js` | The token-usage → number mapping, shared with the GUI so the two can never disagree. |
+| `desktop/lib/local/` | The agent-loop engine — persistent-shell exec, read/write/edit/glob/grep, Task subagents. The CLI runs the same loop the GUI does, scoped to the AEGIS class. |
 
 Routing, model tiers, memory and billing all stay behind aegiscloud.org.
 
@@ -53,64 +54,46 @@ echo "q" | aegiscode -p -        # prompt on stdin
 aegiscode -m deepseek/deepseek-v4-flash -p "..."   # pin a model
 ```
 
-In a session, plain text is a prompt. `/help` lists commands:
+In a session, plain text is a prompt. `/help` lists commands, grouped by
+category, the way `aegiscodex-dev` does. The registry is that client's, ported
+command for command — 75 entries across nine categories:
 
-| Command | What it does |
+| Category | Commands |
 |---|---|
-| `/ask <prompt>` | Pooled inference (identical to typing the prompt) |
-| `/status` | Key, plan, account, memory state |
-| `/models` | The model ids you can pin |
-| `/balance` | Token-bank balance and recent spend — tokens beside € |
-| `/recall <query>` | Search cloud memory |
-| `/remember <text>` | Save a durable note |
-| `/memory` `/import` | Review or import memory from other tools |
-| `/byok` `/byok-set` `/byok-rm` | Bring-your-own-key status and management (the key is prompted, never echoed) |
-| `/model` `/stream` `/theme` `/cost` `/clear` `/help` `/quit` | Session controls |
-| `/tool <name> [json]` | Call any registry tool directly |
-
-Every command above that talks to AEGIS names a tool from `mcp/tools.js`, and
-the test suite asserts both directions: no command points at a tool that does
-not exist, and no tool is unreachable from the prompt.
-
-Command names, aliases and categories follow `aegiscodex-dev`'s registry, so the
-vocabulary matches the other terminal host: the AEGIS family is spelled
-`/aegis-ask`, `/aegis-status`, `/aegis-recall`, `/aegis-remember`, `/aegis-import`
-(with `/ask`, `/status`, `/recall`, `/remember` kept as aliases), and the session
-and model controls are its `help`/`?`/`h`, `exit`/`quit`, `clear`/`cls`,
-`theme`/`t`, `version`/`v` and `model`/`m`. Commands that need a local agent loop
-this client deliberately does not have — `/login`, `/doctor`, `/permissions`,
-`/mcp`, `/skills`, `/hooks`, `/agents`, `/resume` and a few more — are listed but
-answer honestly with the reason and the nearest working alternative rather than
-pretending to work.
-
-## What it looks like
+| Session & context | `/clear` `/compact` `/cost` `/exit` `/new` `/recap` `/resume` `/rewind` `/agents` `/status` `/teleport` `/version` `/clone` `/schedule` |
+| Workspace | `/run` `/build` `/cd` `/copy` `/init` `/review` `/prs` |
+| Model & behavior | `/model` `/effort` `/thinking` `/theme` `/vim` `/router` `/confirm` `/yolo` `/permissions` `/hooks` `/skills` `/mcp` |
+| Data | `/context` `/export` `/tokens` |
+| Auth | `/credentials` `/byok` `/byok-set` `/byok-rm` |
+| Support | `/help` `/doctor` `/troubleshooting` `/feedback` `/bug` `/issue` `/onboarding` `/benchmark` `/release-notes` `/billing` `/cloud` |
+| Aegis plugin | `/aegis-ask` `/aegis-status` `/aegis-recall` `/aegis-remember` `/memory` `/aegis-council` `/aegis-multi` `/aegis-print` `/aegis-import` `/tool` |
+| Fun | `/radio` `/waifu` |
+
+`/help` shows the live list with hints; aliases are searchable in the `/`
+palette exactly as they are there (`/ask` → `/aegis-ask`, `?` → `/help`,
+`quit` → `/exit`, `tok` → `/tokens`, …).
+
+Every command that talks to AEGIS names a tool from `mcp/tools.js`, and the test
+suite asserts both directions: no command points at a tool that does not exist,
+and no tool is unreachable from the prompt. Everything else is a real local
+handler — `/run` detects and drives this project's dev command, `/init` sniffs
+the project and writes `AEGIS.md`, `/export` writes the transcript out,
+`/resume` and `/rewind` read the session store, `/cd` moves the working
+directory, `/doctor` runs diagnostics.
+
+The only two commands that answer "not available" are `/login` and `/logout`:
+their whole premise is Claude Code's own auth loop, which this client does not
+participate in — it authenticates with an AEGIS key (or your own provider key
+via `/byok-set`). They say so, and point at the working alternative.
+
+## The chatflow
+
+The session is `aegiscodex-dev`'s loop, ported rather than approximated: an
+alternate-screen frame of header rule, transcript viewport, spinner/effort line,
+input line and status line, driven by a raw key stream.
 
 ```
-━────────────────────────────────────────────────────────────────────────────━
-
-            ✦               █████▓▓░      ▓▓▓▓▓▓▓▓▓ ✦       ▒▒▒▒▒▒▒▒▒▒▒▒ 
-                 ✦        ███▓░     ░░    ▓▓▓▓▓▓▓░░░       ▒▒▒▒▒▒▒▒▒▒▒▒▒ 
-             ░░░░         ███▓░           ▓▓▓▓░░░░░░     ██▒▒▒▒▒▒▒▒▒▒▒▒▓▓
-           ░░░░░░░░       ███▓░             ░░░░░░       ██▒▒▒▒▒▒▒▒▒▒▒▒▓ 
-         ░░░░░░░░░░░░     ███▓░           ✦   ·   ·       ▒▒▒▒▒▒▒▒▒▒▒▒▒▒ 
-                  ██▓░░      ▓                             ░░░░░░░░░░░░  
-                  ░▓▓███▓▓░                                              
-     ▐▛███▜▌                                                             
-    ▝▜█████▛▘                                                            
-      ▘▘ ▝▝                                                              
-
-                            Welcome to AEGIS Code
-                     v6.1.0 · Cloud brain in your shell.
-
-───────────────────────────────── aegiscode ──────────────────────────────────
-  version v6.1.0
-  model   nexus-brain
-  base    https://aegiscloud.org
-  key     aegis_••••4f2a
-  render  streaming
-
- type /help for commands · /quit to exit
-
+╭───────────────────────────── AEGIS Code v6.2.0 ─────────────────────────────╮
 ❯ summarise what changed in the token accounting
 ● Three things changed, and one of them was costing you money:
 
@@ -118,16 +101,51 @@ pretending to work.
   - cache reads and writes are billed, not ignored
   - a zero-token call no longer refunds its reservation
 
-  merge_usage({input_tokens: 1250}, {output_tokens: 312})
-  => 1562 total
-
-Use /balance to see tokens beside € on every row.
-⎿  nexus-brain · 1,562 tok · 1,250/312 · €0.0007 · 4.2s · 4 calls
-
-* Consulting… (2.1s)  esc to interrupt
- aegis · nexus-brain · 1,562 tok · €0.0007 · stream               ctrl+c quit 
+● Running 1 shell command…
+  ⎿  $ git log --oneline -3
+Ran 1 shell command
+✻ Worked for 6s
+⎿  nexus-brain · 1,562 tok · 1,250/312 · €0.0007 · 4.2s
+                                                            ● high · /effort
+────────────────────────────────────────────────────────────────────────────────
+❯  Try "edit <filepath> to..."
+────────────────────────────────────────────────────────────────────────────────
+⏸ manual mode on · ? for shortcuts · ← for agents
 ```
 
+What the loop does, in the order a turn happens:
+
+- **You type.** The input line has history (`↑`/`↓`), tab completion for `/…`,
+  word motions, a rotating suggestion when empty, horizontal scrolling for a
+  long line, and a collapsed one-line preview for a multi-line paste (the full
+  text is still what gets submitted).
+- **The turn starts.** A random verb from the reference set shimmers in coral
+  beside the spinner, with elapsed time and a live token estimate.
+- **The answer streams into a row**, markdown-rendered, opening with `●` and
+  trailing a live cursor while it grows.
+- **Tool calls become rows.** `● Running 1 shell command… · 3s` resolves to
+  `Ran 1 shell command` when the call returns — paired by tool-call id, so
+  parallel same-name calls and nested subagent rows stay separate, and the
+  plural is right.
+- **The turn ends** with `✻ Churned for Ns` (no tools) or `✻ Worked for Ns`
+  (tools), then an accounting row: `⎿ nexus-brain · 1,562 tok · 1,250/312 ·
+  €0.0007 · 4.2s`.
+- **Esc interrupts.** The abort reaches the transport through an
+  `AbortSignal`, so the in-flight provider call is genuinely cancelled — it
+  does not keep running and billing behind a "stopped" label — and whatever had
+  already streamed is kept, marked `(stopped)`.
+- **Keys work mid-turn.** Esc/Ctrl-C abort; PgUp/PgDn and the wheel scroll the
+  transcript live (and scrolling up is anchored to an absolute line index, so an
+  arriving delta does not drag the reader back to the bottom); everything else
+  you type is replayed into the input line afterwards.
+- **Overlays**: `/` the palette, `alt+p` the model picker, `/effort` the effort
+  picker, `/resume` the session list, `?` the shortcut grid, and a centred
+  Yes/No dialog when a mutating tool needs approval.
+
+Anything that is not a real terminal — a pipe, `-p`, a CI run — stays a linear
+transcript written once to scrollback, so output remains pipeable and
+scriptable.
+
 Render it yourself, with no key and no network:
 
 ```bash
@@ -147,31 +165,56 @@ and art row to that source so the two hosts cannot drift apart. (An earlier
 revision of this CLI was a deliberate divergence — a violet/cyan "Signal" theme
 with a test asserting it. That direction is gone.)
 
-**A linear transcript, not a full-screen TUI.** Finished turns are written once
-to the scrollback; only the one live line (spinner, elapsed time) is redrawn.
-Output stays selectable, searchable and pipeable, which matters for a tool you
-script.
+**A full-screen chatflow on a terminal, a linear transcript everywhere else.**
+On a TTY the session is the reference's loop: alternate screen, header rule,
+transcript viewport, spinner, effort line, input line, status line, overlays.
+Anywhere else — a pipe, `-p`, CI — turns are written once to the scrollback
+instead, so output stays selectable, searchable and pipeable. A tool you script
+should not become un-scriptable because the interactive mode got nicer.
+
+**The command registry is `aegiscodex-dev`'s, ported.** Names, aliases,
+categories, the palette grouping and the handlers themselves come from it, with
+`test/cli-commands.test.mjs` asserting the full name list so a silent drop
+fails the build. Local capability that the reference has — a dev-server runner,
+project sniffing, an export path, a session store, checkpoints, permission
+rules, subagent presets — was ported with it rather than stubbed.
 
 **Tokens beside money, always.** A turn prints what it consumed and what it
 settled at, in the same line: `1,562 tok ∙ 1,250/312 ∙ €0.0007`. Sub-cent
 amounts keep four decimals, because a €0.0007 call rendered at 2dp reads as
 free usage next to a token count.
 
+**Esc really stops the call.** The interrupt travels as an `AbortSignal` into
+the transport, and the engine does not re-dispatch after an abort — a cancelled
+turn used to fire a second billed provider request ("the model said nothing"
+recovery, triggered by the empty result an abort produces) and stream the
+partial answer twice. `test/local-engine.test.mjs` pins the dispatch count.
+
 ## Tests
 
 ```bash
-node ../../test/cli-conformance.test.mjs # the design guard: palette, glyphs, art, verbs
-node ../../test/cli-render.test.mjs      # width safety, accounting, live region
-node ../../test/cli-overlays.test.mjs    # the / palette, model + effort pickers, resume list
-node ../../test/cli-fuzzy.test.mjs       # palette ranking and match positions
-node ../../test/cli-markdown.test.mjs    # span-line markdown, cell widths
-node ../../test/cli-tools.test.mjs       # registry parity with the MCP host + dispatch
-node ../../test/cli-run.test.mjs         # the real binary against a real backend
-node ../../test/cli-package.test.mjs     # the published layout, isolated from the repo
+node ../test/cli-chatflow.test.mjs    # the session loop, driven with a synthetic key stream
+node ../test/cli-commands.test.mjs    # the full command table, aliases, dispatch contract
+node ../test/cli-panels.test.mjs      # every panel builder, defensive against missing data
+node ../test/cli-support.test.mjs     # config/history/tokens/agents/export/checkpoints
+node ../test/cli-conformance.test.mjs # the design guard: palette, glyphs, art, verbs
+node ../test/cli-render.test.mjs      # width safety, accounting, live region
+node ../test/cli-overlays.test.mjs    # the / palette, model + effort pickers, resume list
+node ../test/cli-fuzzy.test.mjs       # palette ranking and match positions
+node ../test/cli-markdown.test.mjs    # span-line markdown, cell widths
+node ../test/cli-tools.test.mjs       # registry parity with the MCP host + dispatch
+node ../test/cli-run.test.mjs         # the real binary against a real backend
+node ../test/cli-package.test.mjs     # the published layout, isolated from the repo
 npm test                                 # all of the above
 ```
 
-`npm run predist` stages `client/`, `mcp/tools.js` and the desktop's `usage.js`
-into `cli/vendor/` (gitignored) so the published package resolves its own
-modules. `test/cli-package.test.mjs` copies that tree somewhere with no repo
-around it and runs the binary there.
+The chatflow test drives `runSession` for real: a synthetic key stream, stdout
+captured, and the app entered exactly as `bin/aegiscode.js` enters it. It covers
+the turn lifecycle, tool-row pairing, the interrupt reaching the transport, the
+viewport anchor, the input line's cell maths and an abort that must not
+re-dispatch.
+
+`npm run predist` stages `client/`, `mcp/tools.js` and the desktop's `usage.js`,
+`local/engine.js` and `local/agents.js` into `cli/vendor/` (gitignored) so the
+published package resolves its own modules. `test/cli-package.test.mjs` copies
+that tree somewhere with no repo around it and runs the binary there.

package/bin/aegiscode.js

@@ -33,11 +33,14 @@ Options:
       --max-tokens <n>    output ceiling hint
       --light             light theme
       --width <cols>      force a render width (useful for piping/logs)
+      --yolo              skip tool-approval prompts (exec/writeFile/editFile
+                           run without asking) — same as the in-session /yolo
   -h, --help              this text
   -v, --version           print the version
 
 In-session: type /help for commands, /quit to exit, esc/ctrl+c to interrupt a
-running call. Plain text is a prompt (identical to /ask).
+running call. Plain text is a prompt (identical to /ask) — a question that
+needs a file read, a shell command, or an edit is handled the same turn.
 `;
 
 function parseArgs(argv) {
@@ -50,6 +53,7 @@ function parseArgs(argv) {
     maxTokens: undefined,
     light: false,
     width: null,
+    yolo: false,
     prompt: null,
     help: false,
     version: false,
@@ -102,6 +106,9 @@ function parseArgs(argv) {
       case '--light':
         opts.light = true;
         break;
+      case '--yolo':
+        opts.yolo = true;
+        break;
       case '--width':
         opts.width = Number(next());
         break;
@@ -172,6 +179,7 @@ async function main(argv = process.argv.slice(2)) {
     maxTokens: opts.maxTokens,
     width: opts.width ? () => opts.width : undefined,
     interactive: !prompt && Boolean(process.stdin.isTTY),
+    confirmMode: !opts.yolo,
   });
 
   if (prompt) return app.runOnce(prompt, { json: opts.json });

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "aegiscode",
   "productName": "AEGIS Code",
-  "version": "6.1.0",
+  "version": "6.2.0",
   "description": "aegiscode — the command-line version of AEGIS Desktop. The shared tool surface in your shell, over the same thin transport and tool registry as the MCP plugin and the desktop app. Ships transport + UI only; no brain.",
   "author": {
     "name": "AEGIS Code",
@@ -31,8 +31,8 @@
     "start": "node bin/aegiscode.js",
     "predist": "node scripts/predist.mjs",
     "prepublishOnly": "npm run predist",
-    "check": "node --check bin/aegiscode.js && node --check src/theme.js && node --check src/art.js && node --check src/screen.js && node --check src/format.js && node --check src/fuzzy.js && node --check src/markdown.js && node --check src/render.js && node --check src/overlays.js && node --check src/commands.js && node --check src/deps.js && node --check src/app.js && node --check scripts/predist.mjs",
-    "test": "for f in ../../test/cli-*.test.mjs; do node \"$f\" || exit 1; done"
+    "check": "node --check bin/aegiscode.js && for f in src/*.js; do node --check \"$f\" || exit 1; done && node --check scripts/predist.mjs",
+    "test": "for f in ../test/cli-*.test.mjs; do node \"$f\" || exit 1; done"
   },
   "keywords": [
     "aegis",

package/scripts/predist.mjs

@@ -11,7 +11,8 @@
  *   cli/                        repo/
  *     vendor/mcp/tools.js   ≡     mcp/tools.js
  *     vendor/client/*.js    ≡     client/*.js
- *     vendor/desktop/...    ≡     desktop/renderer/usage.js
+ *     vendor/desktop/...    ≡     desktop/renderer/usage.js,
+ *                                 desktop/lib/local/{engine,tools,shell,agents,prompt}.js
  *
  * The shape matters: `mcp/tools.js` requires `../client/foreign-memory.js`, and
  * because the staged tree mirrors the repo, that path resolves *inside* the
@@ -39,6 +40,15 @@ const FILES = [
   'client/foreign-memory.js',
   'mcp/tools.js',
   'desktop/renderer/usage.js',
+  // The agent-loop engine (persistent shell, editFile/grep/exec, Task
+  // subagents) the desktop app already ships (desktop/lib/local/). The CLI
+  // reuses it as-is, scoped to the 'aegis' class only (see src/engine.js) —
+  // one tool loop implementation, not a second one drifting alongside it.
+  'desktop/lib/local/engine.js',
+  'desktop/lib/local/tools.js',
+  'desktop/lib/local/shell.js',
+  'desktop/lib/local/agents.js',
+  'desktop/lib/local/prompt.js',
 ];
 
 function main() {

package/src/agents.js

@@ -0,0 +1,136 @@
+'use strict';
+
+/**
+ * Sub-agent prompt presets — ported verbatim from aegiscodex-dev/src/agents.js
+ * (which in turn came from the reference's slash-commands builtinCommands.ts
+ * buildMultiAgents() and the research-council member prompts). This build has
+ * no parallel-agent runtime, so the presets are prompt composition:
+ * /agents <role> <task> and /research <question> build the same specialist
+ * prompts the reference hands to real sub-agents and run them through the
+ * normal chat flow (c.runPrompt).
+ */
+
+/** Role → system prompt, verbatim from the reference's buildMultiAgents. */
+const AGENT_PRESETS = {
+  synthesizer: `You are a senior technical lead. Given analysis from multiple specialist agents, synthesize their findings into a clear, actionable summary.
+Structure your response as: key findings, recommended approach, top action items.
+Be direct, concrete, and avoid repeating everything the agents said.
+Focus on delivering a decision-ready synthesis.`,
+
+  architect: `You are a System Architect. Design the new application architecture.
+Define: project structure, tech stack, directory layout, key modules, data flow, API design.
+Consider: scalability, maintainability, testing strategy, deployment.
+Output a concrete file tree and architecture decisions log. Be specific.`,
+
+  scaffolder: `You are a Project Scaffolder. Build the complete application from scratch.
+
+YOUR JOB IS TO CREATE ALL PROJECT FILES - not just describe them.
+
+Use Write to create: package.json, tsconfig.json, source files, configs, tests.
+Generate COMPLETE, WORKING code - not stubs or placeholders.
+Set up build scripts, lint config, and any necessary tooling.
+
+After creating files, use Bash to run: npm/pnpm install, then build/compile.
+Fix any errors until the project builds successfully.
+
+Be thorough - a real, runnable project is the goal.`,
+
+  planner: `You are a Refactoring Planner. Given the analyzer findings, create a step-by-step plan.
+Each step: file path, what to change, why, risk level (LOW/MEDIUM/HIGH).
+Include before/after snippets. Order by impact. Be concrete.`,
+
+  implementer: `You are an Implementation Engineer. Execute the refactoring plan.
+Use Edit and Write to make actual code changes.
+After each change, use Read to verify correctness. Keep existing code style.
+Run build commands to ensure nothing is broken.`,
+
+  reviewer: `You are a Code Reviewer. Review the approach and code.
+Check: logic errors, type safety, error handling, performance, security.
+Be critical but constructive. Report specific issues with file paths.`,
+
+  debugger: `You are a Debugging Specialist. Analyze potential issues and edge cases.
+Identify: failure modes, error handling gaps, testing considerations.
+Think about what could go wrong and how to prevent it.`,
+
+  scanner: `You are a Security Vulnerability Scanner.
+Scan for: hardcoded API keys/secrets, SQL injection, XSS, unsafe eval/exec, path traversal.
+Use Grep with targeted patterns. Report every finding with: file path, severity (CRITICAL/HIGH/MEDIUM/LOW), line number.`,
+
+  analyzer: `You are a Code Analyzer. Find refactoring opportunities.
+Look for: duplicated code, long functions (>20 lines), complex conditionals, unused imports,
+circular dependencies, inconsistent patterns. Report with file paths and line numbers.`,
+};
+
+/** Human-readable role label for a preset id (falls back to the id). */
+function agentRoleLabel(role) {
+  const labels = {
+    synthesizer: 'Technical Lead', architect: 'System Architect',
+    scaffolder: 'Project Scaffolder', planner: 'Refactoring Planner',
+    implementer: 'Implementation Engineer', reviewer: 'Code Reviewer',
+    debugger: 'Debugging Specialist', scanner: 'Vulnerability Scanner',
+    analyzer: 'Code Analyzer',
+  };
+  return labels[role] || role;
+}
+
+/** Compose a sub-agent prompt: the role's system prompt + the task. */
+function composeAgentPrompt(role, task) {
+  return `${AGENT_PRESETS[role]}\n\nTask: ${task}\n\nRespond directly — no preamble.`;
+}
+
+/** Every preset id, in palette order. */
+function agentRoles() {
+  return Object.keys(AGENT_PRESETS);
+}
+
+/**
+ * The research-council prompt (Analyst/Architect/Ethicist/Pragmatist),
+ * ported from the reference's /research command. Includes the workspace
+ * context note so the model can read real files.
+ */
+function composeResearchPrompt(question, workspaceRoot = process.cwd()) {
+  return [
+    `Research the following question from four perspectives, then synthesize:`,
+    ``,
+    `Question: ${question}`,
+    ``,
+    `You are a research council with these members:`,
+    `- Analyst: reasons from data, statistics, and empirical evidence; values measurable outcomes.`,
+    `- Architect: evaluates designs, tradeoffs, and architectural decisions; focuses on scalability, maintainability, and system coherence.`,
+    `- Ethicist: evaluates safety, fairness, privacy, and societal impact; raises concerns others miss.`,
+    `- Pragmatist: evaluates practicality, implementation effort, and real-world constraints; balances idealism with what works in production.`,
+    ``,
+    `Workspace: ${workspaceRoot} — read files with Read, search with Grep, browse with Glob, and check recent git changes with Git to ground your analysis in the real codebase.`,
+    ``,
+    `Format: one reasoned section per perspective, then a Synthesis with a clear recommendation. Always state VOTE: approve, reject, or abstain and REASONING with clear justification.`,
+  ].join('\n');
+}
+
+/**
+ * A structured debate prompt for the current model (the reference runs a
+ * real multi-model DiscussionRoom; this build simulates the debate on the
+ * one configured backend, which the note makes explicit).
+ */
+function composeDebatePrompt(topic, modelId = '') {
+  return [
+    `Hold a structured debate on: ${topic}`,
+    ``,
+    `Present two opposing positions fairly (with the strongest argument FOR and AGAINST), then act as moderator:`,
+    `1. Opening statements for each side.`,
+    `2. Rebuttals — each side attacks the other's weakest claim.`,
+    `3. Cross-examination questions and answers.`,
+    `4. Closing statements.`,
+    `5. A moderator verdict summarizing where each side won and a final recommendation.`,
+    ``,
+    `Be rigorous and balanced — steelman both sides before judging.${modelId ? ` (Simulated on ${modelId} — the reference runs a multi-model discussion.)` : ''}`,
+  ].join('\n');
+}
+
+module.exports = {
+  AGENT_PRESETS,
+  agentRoleLabel,
+  composeAgentPrompt,
+  agentRoles,
+  composeResearchPrompt,
+  composeDebatePrompt,
+};