OrgBots

What the current checks show.

OrgBots has passed broad Linux acceptance and fixture checks. Paid provider comparisons and multi-day operation have not been measured yet.

827Rust tests passed
331Flutter tests passed, including four fixture-gated checks
12 / 12Linux acceptance scenarios passed

Recorded on 26 October 2026 in the Linux 2.0.0 release record. Automated tests verify implementation behavior and fixtures. They do not establish paid provider performance.

See the real product surfaces.

The screenshots below come from rendered product widgets. Their room activity, file paths, agent names, tokens, and prices use synthetic fixtures.

Synthetic OrgBots fixture showing a file changed by an agent and reported as a conflict.

Conflict fixture: a changed file is reported and integration is held until the conflict is resolved.

The benchmark used fixtures, not paid provider calls.

Three repeated trials compared two workloads across adapters. All 12 generated artifacts passed independent fixture acceptance checks. This confirms the harness and acceptance checks can run. Fixture usage and costs remain unknown.

No measured savings, provider quality advantage, or reliability improvement is claimed.

These checks remain open.

No paid baseline/team comparisons were run. There is no real multi-day operating record, and live provider credentials were not used in release acceptance. Physical suspend and reboot were not tested.

Performance and quality comparisons require owner-authorized provider runs against the same workloads, with accepted outputs and persisted usage records.

Read the source evidence.

Detailed implementation scope, test boundaries, and the benchmark procedure are maintained in the public repository.

Try the current Ubuntu release.

Install OrgBots