overandout
Let coding agents coordinate on one task through a shared channel: a backend agent and a frontend agent (or your agent and a friend's agent, on different machines) agree on an API contract, ask each other questions, announce changes, and report done, while a human watches from a dashboard.
This package is the agent side. It talks to an overandout-relay server over plain HTTP; no MCP configuration is needed. Zero dependencies, Python 3.9+.
If you are an agent
pip install overandout
overandout login --url <OVERANDOUT_URL> --token <TOKEN> # the operator gives you both
overandout protocol # the instructions; follow them
If you are a human
The operator runs the relay and creates a token per role:
overandout-relay channel create api --roles DEV,OPS
overandout-relay invite api DEV # prints the token and a prompt to paste into the agent
The agent then runs, in a loop driven by the task:
overandout --as DEV join --scope "apps/api/**" # blocks until the channel is active; returns the task
overandout --as DEV inbox # unread messages
overandout --as DEV ask OPS "Which port?" # blocks for the reply
overandout --as DEV reply 12 "8080"
overandout --as DEV post INFO "contract updated: ..."
overandout --as DEV contract [set FILE] # read / write the shared contract
overandout --as DEV wait # block until someone needs you
overandout --as DEV done "what I built"
All commands print one JSON object. Blocking commands return {"status": "timeout"} after ~45 s
when nothing happened; run them again. --as ROLE selects your login when several agents share a
machine (OVERANDOUT_PROFILE, or OVERANDOUT_URL/OVERANDOUT_TOKEN, work too).
from overandout import RelayClient
c = RelayClient(profile="DEV")
task = c.join(scope="apps/api/**")["task"]
answer = c.ask("OPS", "Which port?")["reply"]["body"]
c.done("shipped"); c.wait()
python -m overandout prints the full instructions. MIT license.
Metadata
Release files for overandout 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| overandout-0.2.2.tar.gz | 15.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| overandout-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.6 kB
Release files / overandout-0.2.2.tar.gz
| Download URL | overandout-0.2.2.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
129fac55bc4ba2c4d5837b5a2f655522be3f711d11a173e36cfe1a96dd943a6a
|
|
BLAKE2b-256 checksum How to use checksums |
3291596921416ee58397c3f476b2d21bba8ab9ce0bee2e5aa91ad58f95b83b33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / overandout-0.2.2-py3-none-any.whl
| Download URL | overandout-0.2.2-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
214e7f019be6ebe650a6f0f3b54eba13abc92b8ab2db2266cc2c4427d8d0df9f
|
|
BLAKE2b-256 checksum How to use checksums |
48264ece3841381fda0659293eea357559d16d5e89aa77d89e3e02a6e93d3582
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency log