televibe
Run headless coding agents (Claude Code, Codex) one turn at a time, as resumable sessions with a typed event stream.
televibe starts the agent, turns its output into common events
(Started, Message, ToolUse, Warning, then exactly one Done or
Failed), and kills what it started on timeout, cancel, or when the caller
walks away. Claude Code also reports the account's subscription usage as
Limits (five-hour and seven-day windows), and a call refused at the limit
fails with FailReason.USAGE_LIMIT. Done.text is the final answer; when
the agent answers, calls a bookkeeping tool and closes with a short line,
engine.turn(..., quiet_tools={"<tool name>"}) keeps the answer whole, and
Done.last_message still has the agent's own last text. What to do with the output is the caller's
business: televibe never sends a message anywhere.
A one-shot call answers in a JSON schema with no session, no tools and no
place in the engine's queue: await claude.ask(prompt, schema={...}, system="...") returns Answer(data, usage, limits) or raises AskFailed
with the same reasons a turn fails for. It is for the model-only chores a bot
has around its turns — cleaning a transcript, classifying a message. See
SPEC.md section 12.
The optional Telegram layer does: pip install 'televibe[telegram]' adds
televibe.telegram, which shows a turn in a chat (reactions, typing or a live
draft, the answer) and keeps one session per reply chain. It is a set of parts
for an aiogram bot, not a framework. Every reaction can be replaced, and
Reactions(done=None, failed_when_sent=False) leaves a reaction only when
nothing could be sent at all. A live
draft shows the usage ("5h 35% · 7d 13%"); Texts relabels it and words the
limit message, and Presenter(tz=...) sets the zone of its reset time. See SPEC.md
section 13.
Install: pip install televibe, or pip install 'televibe[telegram]' with the
Telegram layer. Python 3.12+, Linux and macOS.
Status: 0.4, alpha. Tests: uv run pytest; live tests against real agents:
see tests/test_live.py. MIT licensed.
- SPEC.md is the specification. It is the law: numbered requirements, each claimed by a test.
Metadata
Release files for televibe 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| televibe-0.4.0.tar.gz | 79.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| televibe-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 116.3 kB
Release files / televibe-0.4.0.tar.gz
| Download URL | televibe-0.4.0.tar.gz |
|---|---|
| Size | 79.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c84ac71e1ae4769bac209a2463119c37b4ac22d27db13cd9f4b9c5067a5a6a2e
|
|
BLAKE2b-256 checksum How to use checksums |
f4fc8717ad78f30af494d3f23a8fffb86d47bc538533ee4975839fa2f081368b
|
| 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 16, 2026.
Transparency logRelease files / televibe-0.4.0-py3-none-any.whl
| Download URL | televibe-0.4.0-py3-none-any.whl |
|---|---|
| Size | 36.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
254165fbc568642c5fce6a944e9cb8c0c04cad919bf68d5945a11a5550ed2080
|
|
BLAKE2b-256 checksum How to use checksums |
36a480814a49a0fb9999bd40cb094e4c9db9953219918259c8704dd7d64ec390
|
| 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 16, 2026.
Transparency log