mooting 0.1.0__tar.gz

mooting-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 jyunming
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

mooting-0.1.0/PKG-INFO

@@ -0,0 +1,185 @@
+Metadata-Version: 2.4
+Name: mooting
+Version: 0.1.0
+Summary: A council where agent CLIs from different vendors deliberate, and a human decides.
+Author: jyunming
+License: MIT
+Project-URL: Homepage, https://jyunming.github.io/mooting/
+Project-URL: Documentation, https://jyunming.github.io/mooting/docs/
+Project-URL: Source, https://github.com/jyunming/mooting
+Project-URL: Issues, https://github.com/jyunming/mooting/issues
+Keywords: ai,agents,cli,mcp,multi-agent,claude-code,codex
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: mcp>=1.2
+Requires-Dist: prompt_toolkit>=3.0
+Requires-Dist: textual>=1.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Dynamic: license-file
+
+<h1 align="center">Mooting</h1>
+
+<p align="center">
+  <em>Your coding agents, arguing on the record — and you decide.</em>
+</p>
+
+<p align="center">
+  <a href="https://github.com/jyunming/mooting/actions/workflows/tests.yml"><img alt="tests" src="https://github.com/jyunming/mooting/actions/workflows/tests.yml/badge.svg"></a>
+  <a href="LICENSE"><img alt="MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
+  <img alt="python" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+</p>
+
+<p align="center">
+  <a href="https://jyunming.github.io/mooting/"><strong>mooting &rarr;</strong></a>
+</p>
+
+<p align="center">
+  <img alt="A Mooting session" src="docs/assets/session.svg" width="820">
+</p>
+
+<p align="center">
+  <a href="#install">Install</a> ·
+  <a href="docs/COMMANDS.md">Commands</a> ·
+  <a href="docs/ARCHITECTURE.md">Architecture</a> ·
+  <a href="docs/DRIVERS.md">Driver notes</a>
+</p>
+
+---
+
+Claude Code, Codex, Copilot CLI and Antigravity each keep their own
+subscription, their own context and their own strengths. Mooting gives them one
+shared board and a turn-taking loop, so *"get a second opinion from the model that
+read the sources"* stops being four terminal windows and a lot of copy-paste.
+
+It never calls a model, holds an API key, or sees a token. It drives the
+first-party CLIs you already pay for.
+
+```bash
+mooting tui
+```
+
+```
+> /new the workflow optimization in agentic AI development
+> we run four CLIs by hand across separate windows and merge by hand
+> /run
+```
+
+Three seats argue. You interject, ask one of them directly with `@codex …`, and
+rule on what they propose. Then:
+
+```
+> /conclude examples before invariants; humans review oracles, not diffs
+wrote what-is-the-best-optimized-workflow-minutes.md — 2 decisions
+```
+
+## What it is for
+
+**A decision you do not want to make alone.** Independent seats, real
+disagreement, and a record of who objected and why — then a ruling that only you
+can give.
+
+**Work that follows from it.** The same topic becomes a team: a manager drafts
+tasks, the plan comes to you as one proposal, and approved work runs in isolated
+git worktrees. Your branch is never touched; merging stays your git action.
+
+**A record that outlives the terminal.** `mooting minutes` writes what was asked,
+what was decided and by whom, who objected, what was left unanswered, and — on a
+work topic — a log of every task and what came of it.
+
+## Why not one model with a long prompt
+
+Because they disagree, and the disagreement is the product. In the session that
+produced this project's own design notes, one seat proposed a criterion for
+agentic workflows and a second seat rejected the premise the first had built on —
+a distinction the first had not considered. That exchange is in the minutes,
+attributable, with the human ruling recorded against it.
+
+And because the seats are the CLIs you already pay for. Routing a cheap question
+to a cheap seat and a hard one to an expensive seat is the point; that only works
+if each runs under its own subscription.
+
+## Install
+
+```bash
+pip install mooting            # once published
+# or, from a clone:
+pip install -e .
+
+mooting setup                  # finds your CLIs, seats them, wires them up, proves it works
+mooting tui
+```
+
+`mooting doctor` asserts on **what landed on the board**, not on exit codes. A CLI
+can start, load the server, decline to call it and exit 0 — a return-code check
+goes green while the seat is mute.
+
+Windows: use Windows Terminal, PowerShell or cmd for the full-screen session;
+`mooting console` is the line-based fallback for mintty and SSH.
+
+## A tour
+
+```
+> /new should webhook retries use exponential backoff?
+> the gateway retries every 30s and stampedes on recovery
+> /run
+```
+
+Seats argue. Type to interject — it also answers anything asked of you. `@codex
+what does the gateway do today?` puts the question to one of them and the others
+wait for the answer. When a seat proposes something concrete, only you can close
+it:
+
+```
+> /proposals 3          # the whole thing: body, every vote, every objection
+> /approve 3 agreed — cap at 6 attempts
+> /conclude backoff with jitter, capped
+wrote retries-minutes.md — 1 decision
+```
+
+Then the same topic can become a team: `/mode work <seat>` and a manager drafts
+tasks, the plan comes to you as one proposal, and approved work runs in isolated
+git worktrees.
+
+**[Using it →](https://github.com/jyunming/mooting/blob/main/docs/USING.md)**  ·  **[Every command →](https://github.com/jyunming/mooting/blob/main/docs/COMMANDS.md)**
+
+## Status
+
+Verified end to end on this machine (2026-08-29):
+
+| Seat | Result |
+|---|---|
+| **Claude Code** 2.1.250 | **working** — posts to the board, resumes by our own UUID |
+| **Codex** 0.149.0 | **working** — needs `--approve-for-me` and its prompt on stdin; stateless |
+| **Antigravity** (`agy`) 1.1.20 | **working** — `--mode plan` is genuinely read-only; stateless |
+| **Copilot** 1.0.81 | driver verified against the CLI |
+
+Per-CLI flags and the four traps behind them are in
+[`docs/DRIVERS.md`](https://github.com/jyunming/mooting/blob/main/docs/DRIVERS.md). The one worth knowing before you write any
+adapter: **Windows `.CMD` shims cannot carry a multi-line argument**, so a
+multi-line prompt silently drops every flag after it — and the symptom is a CLI
+insisting your MCP server needs approval, not a quoting error.
+
+**Not built yet:** a web UI. ACP (`--acp` on Copilot and Antigravity) is
+worth adding for **permission routing** — it hands a seat's approval requests back
+to the supervisor, which is the natural home for "the human decides". It is *not*
+a latency fix: process spawn is ~2% of a turn.
+
+## More
+
+- **[Using it](https://github.com/jyunming/mooting/blob/main/docs/USING.md)** — the session, mentions, minutes, work mode
+- **[Commands](https://github.com/jyunming/mooting/blob/main/docs/COMMANDS.md)** — every command, in both surfaces
+- **[Why it works this way](https://github.com/jyunming/mooting/blob/main/docs/WHY.md)** — invariants, latency measurements, prior art
+- **[Architecture](https://github.com/jyunming/mooting/blob/main/docs/ARCHITECTURE.md)** — the board, the fences, the driver contract
+- **[Driver notes](https://github.com/jyunming/mooting/blob/main/docs/DRIVERS.md)** — what each CLI actually does, and four traps
+- **[Contributing](https://github.com/jyunming/mooting/blob/main/CONTRIBUTING.md)**
+
+MIT.

mooting-0.1.0/README.md

@@ -0,0 +1,157 @@
+<h1 align="center">Mooting</h1>
+
+<p align="center">
+  <em>Your coding agents, arguing on the record — and you decide.</em>
+</p>
+
+<p align="center">
+  <a href="https://github.com/jyunming/mooting/actions/workflows/tests.yml"><img alt="tests" src="https://github.com/jyunming/mooting/actions/workflows/tests.yml/badge.svg"></a>
+  <a href="LICENSE"><img alt="MIT" src="https://img.shields.io/badge/license-MIT-blue.svg"></a>
+  <img alt="python" src="https://img.shields.io/badge/python-3.10%2B-blue.svg">
+</p>
+
+<p align="center">
+  <a href="https://jyunming.github.io/mooting/"><strong>mooting &rarr;</strong></a>
+</p>
+
+<p align="center">
+  <img alt="A Mooting session" src="docs/assets/session.svg" width="820">
+</p>
+
+<p align="center">
+  <a href="#install">Install</a> ·
+  <a href="docs/COMMANDS.md">Commands</a> ·
+  <a href="docs/ARCHITECTURE.md">Architecture</a> ·
+  <a href="docs/DRIVERS.md">Driver notes</a>
+</p>
+
+---
+
+Claude Code, Codex, Copilot CLI and Antigravity each keep their own
+subscription, their own context and their own strengths. Mooting gives them one
+shared board and a turn-taking loop, so *"get a second opinion from the model that
+read the sources"* stops being four terminal windows and a lot of copy-paste.
+
+It never calls a model, holds an API key, or sees a token. It drives the
+first-party CLIs you already pay for.
+
+```bash
+mooting tui
+```
+
+```
+> /new the workflow optimization in agentic AI development
+> we run four CLIs by hand across separate windows and merge by hand
+> /run
+```
+
+Three seats argue. You interject, ask one of them directly with `@codex …`, and
+rule on what they propose. Then:
+
+```
+> /conclude examples before invariants; humans review oracles, not diffs
+wrote what-is-the-best-optimized-workflow-minutes.md — 2 decisions
+```
+
+## What it is for
+
+**A decision you do not want to make alone.** Independent seats, real
+disagreement, and a record of who objected and why — then a ruling that only you
+can give.
+
+**Work that follows from it.** The same topic becomes a team: a manager drafts
+tasks, the plan comes to you as one proposal, and approved work runs in isolated
+git worktrees. Your branch is never touched; merging stays your git action.
+
+**A record that outlives the terminal.** `mooting minutes` writes what was asked,
+what was decided and by whom, who objected, what was left unanswered, and — on a
+work topic — a log of every task and what came of it.
+
+## Why not one model with a long prompt
+
+Because they disagree, and the disagreement is the product. In the session that
+produced this project's own design notes, one seat proposed a criterion for
+agentic workflows and a second seat rejected the premise the first had built on —
+a distinction the first had not considered. That exchange is in the minutes,
+attributable, with the human ruling recorded against it.
+
+And because the seats are the CLIs you already pay for. Routing a cheap question
+to a cheap seat and a hard one to an expensive seat is the point; that only works
+if each runs under its own subscription.
+
+## Install
+
+```bash
+pip install mooting            # once published
+# or, from a clone:
+pip install -e .
+
+mooting setup                  # finds your CLIs, seats them, wires them up, proves it works
+mooting tui
+```
+
+`mooting doctor` asserts on **what landed on the board**, not on exit codes. A CLI
+can start, load the server, decline to call it and exit 0 — a return-code check
+goes green while the seat is mute.
+
+Windows: use Windows Terminal, PowerShell or cmd for the full-screen session;
+`mooting console` is the line-based fallback for mintty and SSH.
+
+## A tour
+
+```
+> /new should webhook retries use exponential backoff?
+> the gateway retries every 30s and stampedes on recovery
+> /run
+```
+
+Seats argue. Type to interject — it also answers anything asked of you. `@codex
+what does the gateway do today?` puts the question to one of them and the others
+wait for the answer. When a seat proposes something concrete, only you can close
+it:
+
+```
+> /proposals 3          # the whole thing: body, every vote, every objection
+> /approve 3 agreed — cap at 6 attempts
+> /conclude backoff with jitter, capped
+wrote retries-minutes.md — 1 decision
+```
+
+Then the same topic can become a team: `/mode work <seat>` and a manager drafts
+tasks, the plan comes to you as one proposal, and approved work runs in isolated
+git worktrees.
+
+**[Using it →](https://github.com/jyunming/mooting/blob/main/docs/USING.md)**  ·  **[Every command →](https://github.com/jyunming/mooting/blob/main/docs/COMMANDS.md)**
+
+## Status
+
+Verified end to end on this machine (2026-08-29):
+
+| Seat | Result |
+|---|---|
+| **Claude Code** 2.1.250 | **working** — posts to the board, resumes by our own UUID |
+| **Codex** 0.149.0 | **working** — needs `--approve-for-me` and its prompt on stdin; stateless |
+| **Antigravity** (`agy`) 1.1.20 | **working** — `--mode plan` is genuinely read-only; stateless |
+| **Copilot** 1.0.81 | driver verified against the CLI |
+
+Per-CLI flags and the four traps behind them are in
+[`docs/DRIVERS.md`](https://github.com/jyunming/mooting/blob/main/docs/DRIVERS.md). The one worth knowing before you write any
+adapter: **Windows `.CMD` shims cannot carry a multi-line argument**, so a
+multi-line prompt silently drops every flag after it — and the symptom is a CLI
+insisting your MCP server needs approval, not a quoting error.
+
+**Not built yet:** a web UI. ACP (`--acp` on Copilot and Antigravity) is
+worth adding for **permission routing** — it hands a seat's approval requests back
+to the supervisor, which is the natural home for "the human decides". It is *not*
+a latency fix: process spawn is ~2% of a turn.
+
+## More
+
+- **[Using it](https://github.com/jyunming/mooting/blob/main/docs/USING.md)** — the session, mentions, minutes, work mode
+- **[Commands](https://github.com/jyunming/mooting/blob/main/docs/COMMANDS.md)** — every command, in both surfaces
+- **[Why it works this way](https://github.com/jyunming/mooting/blob/main/docs/WHY.md)** — invariants, latency measurements, prior art
+- **[Architecture](https://github.com/jyunming/mooting/blob/main/docs/ARCHITECTURE.md)** — the board, the fences, the driver contract
+- **[Driver notes](https://github.com/jyunming/mooting/blob/main/docs/DRIVERS.md)** — what each CLI actually does, and four traps
+- **[Contributing](https://github.com/jyunming/mooting/blob/main/CONTRIBUTING.md)**
+
+MIT.

mooting-0.1.0/mooting/__init__.py

@@ -0,0 +1,3 @@
+"""Mooting: a council where agent CLIs from different vendors deliberate, and a human decides."""
+
+__version__ = "0.0.1"