Security suite: Gitleaks · Bandit · Semgrep · pip-audit · Trivy
byte-bot
See what your coding agents are doing — and know when they need you.
Byte is a small, local dashboard for coding agents. It watches supported agents without controlling them, gives you one terminal view, and can optionally send the same status to a private Telegram chat.
The dashboard above uses synthetic demo data.
Install
curl -fsSL https://raw.githubusercontent.com/erajtob/byte-bot/main/install.sh | sh
Run
byte-bot
On first launch, choose the demo or follow the guided setup for your machine.
Already installed?
byte-bot update
Beta status: Linux-first. macOS has a foreground path but is not Beta-verified yet; Windows is not Beta-supported yet.
What you can see
- active supported agent sessions, grouped by project when Byte can prove the workspace;
- a short current-activity line such as reading files, editing, running a command, or thinking;
- model and usage information when the source provides it;
- permission or input blockers that need you;
- whether status is fresh or stale, and when a source could not be read.
Byte does not store or display private chain-of-thought, prompt bodies, command output, or raw tool arguments as status.
Telegram (optional)
Pair Byte with one private Telegram chat to check status away from the terminal and receive quiet notifications when an agent needs attention.
Telegram does not become a shell. It cannot change configured commands, start agents, control Docker or sudo, browse the filesystem, or turn chat text into command input.
Supported today
| Source | What Byte currently supports |
|---|---|
| OpenCode | Active sessions, projects, model/usage, current activity, and permission/input waits |
| Codex CLI 0.155.1 | Passive observation of an existing exec --json capture |
| Structured project sources | Status and events provided by a project adapter |
| Local status commands | Exact read-only commands you configure, with timeouts |
OpenCode is not pinned to one release number. Byte checks the small set of data it relies on; if that data becomes incompatible, Byte marks the source degraded instead of guessing.
Read-only by design
byte-bot v0.1 only observes:
- Telegram cannot run arbitrary commands or control your agents;
- Byte only runs the exact local status commands you configure, with timeouts;
- there is no hosted Byte account; optional Telegram uses outbound connections only.
For the technical details, read Security, How it works, and Compatibility.
More
- Install, update, and remove
- Setup and configuration
- Support and troubleshooting
- How it works
- Contributing
byte-bot stays project-agnostic and does not require any particular workload.
License
MIT.
1 maintainer
Release files for byte-bot 0.1.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 | |
|---|---|---|---|
| byte_bot-0.1.2.tar.gz | 148.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| byte_bot-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 313.9 kB
Release files / byte_bot-0.1.2.tar.gz
| Download URL | byte_bot-0.1.2.tar.gz |
|---|---|
| Size | 148.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5e99789fbf236277dfc40a4acaec332e89bc337e6f951835dc8e6c5df6747e3
|
|
BLAKE2b-256 checksum How to use checksums |
d2c94ac348c1278df4aa941f3deaf7c400dfc322183c10dcdc80218faa1ea977
|
| 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 Sep 23, 2026.
Transparency logRelease files / byte_bot-0.1.2-py3-none-any.whl
| Download URL | byte_bot-0.1.2-py3-none-any.whl |
|---|---|
| Size | 165.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b8fc134ff833bcd3e63285bcf39b77b13353417cec1e5660f3af87edb25a7d6
|
|
BLAKE2b-256 checksum How to use checksums |
169bcbe0e5fba1d0ef1b6a53734bfffa4bb90ac91e04b5c99aa7ec16c3e405d7
|
| 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 Sep 23, 2026.
Transparency log
