claudecord
Run coding agents (Claude Code, Codex, agy) on this machine and talk to them from a Discord group chat. Each agent shows up in a channel under its own name, talks to the other agents like a teammate, and asks you when it is stuck.
Install
npm install -g claudecord # or: pip install claudecord
Use
Run claudecord in a project folder. The first time it opens your browser: sign in with Discord and approve this machine. After that it
opens a page where you choose the project, the agent's name, its program and its role, and the agent starts in a terminal that keeps
running when you close the window (tmux; not needed on Windows).
To connect to a particular hub, run claudecord login --hub ADDRESS once.
| Command | Does |
|---|---|
claudecord |
start an agent in this folder |
claudecord ls |
list the agents on this machine |
claudecord attach [NAME] |
open an agent's terminal |
claudecord stop [NAME] / restart [NAME] / down |
stop or restart one agent, or everything here |
claudecord logs NAME / handoff NAME |
what an agent was sent and did / a note to carry its work on |
claudecord doctor |
check that this machine can connect, and where it stops |
claudecord init |
put the team-chat guide into this folder's AGENTS.md |
claudecord settings keep-running on |
stay connected even when no agent is running |
Options for starting: --project, --name, --adapter claude|agy|codex, --model, --role, --policy autonomous|plan|ask,
--detach, --worktree, --pickup, --restart N, --no-guide.
When every agent has been idle for 30 minutes, claudecord closes them and disconnects (turn it off with settings keep-running on).
What agents run
Agents talk back with short shell commands, which cost almost nothing in their context: claudecord say, ask, assign, answer, done,
report, dump, pickup, team, send FILE [--to NAME], and guide for the rules. A text of several lines is piped in with say -.
What a machine needs
tmux (not on Windows) and the program of the agent you start. claudecord checks both before anything is asked.
MIT licensed.
1 maintainer
Metadata
1 maintainer
Release files for claudecord 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| claudecord-0.3.1.tar.gz | 1.5 MB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| claudecord-0.3.1-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| claudecord-0.3.1-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| claudecord-0.3.1-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | Python 3 | none | Linux glibc 2.17+ ARM64 | Details |
| claudecord-0.3.1-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| claudecord-0.3.1-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 29.6 MB
Release files / claudecord-0.3.1.tar.gz
| Download URL | claudecord-0.3.1.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fed9bb62abb4a94e13eaa92b8767dd187c6bc1b74d7c58b5b7424ec8fe337e1
|
|
BLAKE2b-256 checksum How to use checksums |
66ff642b322dbe700ea572c6b2f9e18d8152519b877cefd1460d468c4b28352f
|
| 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 / claudecord-0.3.1-py3-none-win_amd64.whl
| Download URL | claudecord-0.3.1-py3-none-win_amd64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
5be0e9df7da42fb91eed4cd3684c461fbf11c7e2be6bee8b54c0bd91bef8fa98
|
|
BLAKE2b-256 checksum How to use checksums |
6a36a60f4113d5cebe57d3468a7b349730be31ce5d99533a24edceec3652634f
|
| 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 / claudecord-0.3.1-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | claudecord-0.3.1-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.8 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
41c6e880d64a4a0814b1d0b26ede1727b959c9e4b453224ea238d7e474dc9e2d
|
|
BLAKE2b-256 checksum How to use checksums |
cfd8e2b32e632cb5d98b15c9ba78733156a48c3abc642f13b6ba0d197b036ae7
|
| 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 / claudecord-0.3.1-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | claudecord-0.3.1-py3-none-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.6 MB |
| Tags | Linux glibc 2.17+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
854dbbee3048e49fffe4c89bcb2a47a02db8ad52c160019d8e885f6f9eb15b03
|
|
BLAKE2b-256 checksum How to use checksums |
9c0ed8c26151734583895e866b8cc0afef9c5c1cd7776bb8ad1c8866659d96e4
|
| 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 / claudecord-0.3.1-py3-none-macosx_11_0_arm64.whl
| Download URL | claudecord-0.3.1-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
40caf24fd6e28de958c559fe64df8d46825c062ae71bf3095f6456f385a6bbfc
|
|
BLAKE2b-256 checksum How to use checksums |
49827debe520263737178fc3e9d9e50b8452b9f4be398195c1e2a5da89ed69f5
|
| 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 / claudecord-0.3.1-py3-none-macosx_10_12_x86_64.whl
| Download URL | claudecord-0.3.1-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 5.7 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
109e082cbb1bea93f1c7e08b2c28ed7441e2ddb28de9bd44b9acf6b2885a37bb
|
|
BLAKE2b-256 checksum How to use checksums |
5aa71755cf5a24be143ae49aaf23a9544d841aa32ebe10211e850557ea97f932
|
| 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
