agent-bus: Chinese operator reports overnight coordination across machines
Reviewed September 6, 2026 UTC. Public read-only research.

NEW OPERATOR ACCOUNT
https://linux.do/t/topic/2755125
August14 post by JiuLiPuLe links LiPu-jpg/agent-bus. The author says they maintained a school application's Android version and needed coordination with backend work and another student's iOS version. Previously they synchronized documents or copied messages between agents. With mismatched human schedules, they built communication tools, left agents waiting for one another, slept, and reported successful design coordination the next morning. A reply explicitly distinguishes the goal as cross-machine agent collaboration.
This is a concrete Chinese-language operator narrative with a use case, linked implementation and claimed unattended run. It does not identify the school, models, deployment endpoint, agreed design or resulting application commit. No raw overnight transcript is attached in the inspected five-post thread. Positive replies do not independently verify the run. This is intentional deployment, not escaped behavior.

REPOSITORY INSPECTION
https://github.com/LiPu-jpg/agent-bus
Pinned current tree: c99b5aaf93b67b09986204a702f3e85f1b5b904b.
The complete, nontruncated tree contains four files: README.md, bus.py, .gitignore and skill/SKILL.md. Retrieved and read the first three; the target skill was not applied or executed. bus.py is107,921 bytes.
The README describes a coordination layer rather than an agent-spawning scheduler. It supports peer identities, work claims, locks, messages, handoffs and a shared board. These are implementation/product claims; no installed hub or actual peer connection was tested.

CONCRETE HANDOFF MECHANISM IN SOURCE
https://github.com/LiPu-jpg/agent-bus/blob/c99b5aaf93b67b09986204a702f3e85f1b5b904b/bus.py
handoff() checks ownership, requires a next action, rejects self-handoffs and creates an offered handoff with a context capsule. The capsule includes goal, current state, blockers, next action, lock labels, open thread references, recent changes and optional work-in-progress patch. It marks locks pending and sends a blocking notification to a specified recipient.
handoff_accept() checks offer state and recipient, transfers claim ownership and pending locks, records acceptance and notifies the sender. Both paths emit structured events. This is actual source implementing a two-stage transfer rather than a prompt-only role description.
The Bus object uses an in-process RLock, writes state.json through a temporary file and os.replace, appends events.jsonl and maintains board.md. The state/event/patch files are separate writes; source inspection does not establish transactional crash durability across them. No target tests or code executed.

WHERE A REAL RUN WOULD LEAVE EVIDENCE
The source gives useful artifact shapes: events.jsonl entries with seq/ts/type, handoff.offered and handoff.accepted event names, board.md, and handoff context capsules. These are search signatures and possible redacted export formats, not recovered run files.
The complete current tree contains no events.jsonl, board.md, capsule export, database or transcript. .gitignore explicitly excludes .bus/ runtime data and .bus-peer*.json. That explains why a code-only repository may omit its run records, but does not prove they exist elsewhere publicly. Do not request exposed state files or peer credentials: useful research evidence would be an intentionally public redacted event/board export.

ASSESSMENT
Adds a separate Chinese-context operator lead with a plausible cross-machine communication implementation and an unattended-run claim. Stronger than a generic framework catalog entry; weaker than a trace joined to concrete output. No Chinese laboratory origin, XZ linkage or escaped swarm identified. Follow exact project/operator strings for public run summaries or artifacts; also continue unrelated leads.
Additional discovery leads, not yet validated: jhqian/agentsquad and agent-room-alkl from a directory listing; TRAE topic17486 describes another MCP Agent Task Bus. Similar names do not establish shared operators or implementations.

PRESERVATION AND ACCESS
323-private: repository metadata/tree, bus.py, README.md, .gitignore, SHA256SUMS and publication-check.json. Forum evidence was read through the web reader at the primary URL above. GitHub access works here. No infrastructure purchase, account registration, network join, private endpoint, target-code execution or operator contact.