honcho-config

Honcho Configuration

Interactive configuration for the Honcho memory plugin. Uses AskUserQuestion for all menus and selections — never dump numbered text lists.

Step 1: Status Header

Call get_config to load the current state. The response includes a card field — a pre-rendered box-drawing card with perfect alignment.

Output the card value exactly as-is inside a code fence. Do not modify it, re-render it, or add any formatting. Just wrap it in triple backticks:

```
{card value here, verbatim}
```

• Do NOT show cache info, config paths, or raw JSON.
• Do NOT show warnings unless they indicate something is broken (skip env var shadowing warnings where the values match what's configured).
• If configExists is false, tell the user no config exists and offer to create one.

Step 2: Menu

Use AskUserQuestion with two questions to present the menu. First question selects the category, second selects the specific setting.

Present ONE question with these options:

AskUserQuestion:
  question: "What would you like to configure?"
  header: "Config"
  options:
    - label: "Peers"
      description: "Your name and AI name (currently: {resolved.peerName} / {resolved.aiPeer})"
    - label: "Session mapping"
      description: "How sessions are named — per directory, git branch, or per chat (currently: {resolved.sessionStrategy})"
    - label: "Workspace"
      description: "Data space, linking, and cross-tool context (currently: {resolved.workspace})"

If the user selects "Other", present advanced options:

AskUserQuestion:
  question: "Advanced settings:"
  header: "Advanced"
  options:
    - label: "Host"
      description: "Platform / local / custom URL (currently: {current.host})"
    - label: "Context refresh"
      description: "TTL, message threshold, dialectic settings"
    - label: "Message upload"
      description: "Token limits, summarization settings"

Always include current values in the description so the user can see what's set.