Skip to content

Latest commit

 

History

History
60 lines (39 loc) · 1.56 KB

File metadata and controls

60 lines (39 loc) · 1.56 KB

Architecture

Fakeble is glue around existing tools.

fakeble
  -> patched Salon
    -> tmux session
      -> Pi host pane
        -> Claude Code guest pane
        -> Codex guest pane

Roles

Pi hosts the panel and synthesizes.

Claude Code is useful for ambiguity, architecture, failure modes, product and narrative judgment, and adversarial review.

Codex is useful for repo structure, implementation details, tests, edge cases, and concrete code-change reality.

Salon creates the panes, sends prompts, and forwards guest responses back to the host through local hooks and a Unix socket.

Why A Patch Exists

Upstream Salon is useful, but this workflow needs a few local changes:

  • Codex submission works reliably when tmux sends Enter.
  • tmux launch sometimes needs retry/recreate logic.
  • Salon should use the real Pi on PATH so installed extensions and subscription adapters are visible.
  • Codex model and effort should be overridable per run.
  • Codex notify hooks should be chained so existing user notifications are preserved.

The patch lives at:

patches/salon-fakeble.patch

Check whether it is applied:

npm run patch:check

Subscription Auth

Fakeble is designed for subscription-backed CLI auth. The wrapper unsets:

ANTHROPIC_API_KEY
OPENAI_API_KEY

That prevents API-key settings in the shell from hijacking the Claude/Codex subscription flows.

Limits

This is not a first-party multi-agent API. It is terminal automation. The right mental model is "repeatable local working rig," not "hosted reliable platform."