---
title: "Discussion on \"Botference: A TUI for Multi-Model Project Planning with Claude Code and Codex\" | Hashnode"
description: "Discussion on \"Botference: A TUI for Multi-Model Project Planning with Claude Code and Codex\". A new terminal app lets you run a planning 'council' with Claude Code and Codex simultaneously, producing an implementation-plan.md to kickstart your workflow.\n\nWhat It Does — Multi-LLM Planning in Your Terminal\nBotference is a vibe-coded terminal ap..."
url: "https://hashnode.com/posts/botference-a-tui-for-multi-model-project-planning-with-claude-code-and-codex/69cbd4e032c57515f2610602"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Botference: A TUI for Multi-Model Project Planning with Claude Code and Codex](https://gentic-news.hashnode.dev/botference-a-tui-for-multi-model-project-planning-with-claude-code-and-codex?utm_source=hashnode&utm_medium=feed)

A new terminal app lets you run a planning 'council' with Claude Code and Codex simultaneously, producing an implementation-plan.md to kickstart your workflow. What It Does — Multi-LLM Planning in Your Terminal Botference is a vibe-coded terminal ap...

Mar 31 · 3 min read · gentic-news.hashnode.dev  
Read the article

-   [#artificial-intelligence](https://hashnode.com/tag/artificial-intelligence)
-   [#open-source](https://hashnode.com/tag/open-source)

## Written by

[gentic news](https://hashnode.com/@gentic)

@gentic

  
[View profile](https://hashnode.com/@gentic)

## Responses 1

Markdown supported · ⌘↵ to post

[Aamer Mehaisi](https://hashnode.com/@mehaisi)

[Mar 31](https://hashnode.com/posts/botference-a-tui-for-multi-model-project-planning-with-claude-code-and-codex/69cbd4e032c57515f2610602/comment/69cbd76d32c57515f2610608)

The council/caucus distinction here maps directly onto something we are seeing in production agent systems - the difference between collaborative deliberation (council) and structured convergence (caucus).

What is clever about Botference is that it treats planning as a separate capability from execution. Most agent frameworks conflate these phases, but forcing a plan mode output (implementation-plan.md) before execution creates a natural checkpoint for human review.

The /caucus pattern is particularly interesting. Having models debate privately before presenting a recommendation mirrors how human teams converge on decisions - you get the benefit of divergent exploration without the noise of watching the disagreement unfold.

One question: in the caucus mode, do Claude and Codex converge independently, or does one model take a lead position? The convergence mechanism matters - if they are just averaging recommendations, you lose the value of structured disagreement. If one model synthesizes the others critiques, you get a stronger output.

Also curious how the plan checkpoint handles the handoff back to Claude Code. Does it use structured context injection, or is it more free-form?