Skip to content
OpenCohost Kira

Evidence that keeps its source and boundary attached.

Five artifacts cover visible exports, log telemetry and a reported migration; they are distinct evidence, not interchangeable samples.

4h 27m 35s
Measured agenda duration
Log-derived
104 pages
Visible 1 Aug UI export
Visible UI artifact
285
Generations: 120 cloud / 165 local
Log-derived
70 min
Raw visible chat case
Qualitative n=1

A supervised co-host loop, not an autonomy promise.

Kira can carry a prepared agenda, take direct input and recover across local and cloud providers. The streamer remains the editor and factual authority.

Product
  1. Verified

    Agenda continuity, Direct/PTT, chat input, BYOK and Ollama paths.

  2. Experimental

    Stream connection and reactions were functional but uneven in the abandoned CTK prototype; Tauri carries them forward.

  3. Legacy Unstable

    The CustomTkinter (CTK) prototype was fully abandoned in mid-July 2026; it lacks the interruption improvements.

Download the public alpha for Windows.

OpenCohost is a local-first open-source application and local AI co-host. The alpha installer is generated by CI and published on GitHub Releases. There is no hosted service and no bundled model: you bring Ollama, choose and download the models, and provide the hardware.

v0.3.0-alpha.4 · 588 MB · Windows 10/11 x64 · published Sep 9, 2026 · Verify the SHA256 checksums

Alpha build, generated by CI. If something misbehaves, report it — that feedback is what the alpha is for.

Product demo

Watch the current Kira walkthrough

See the current agenda, chat-context, co-host reaction, and interface flow before reviewing the dated build progress.

Audio: Spanish · Captions: auto-generated Spanish; YouTube may offer automatic English translation

Spanish audioYouTube

Current OpenCohost Kira walkthrough

The walkthrough shows the product direction in motion. Kira remains in active development and this demo is not a release promise.

Open on YouTube
Read the English demo summary

English summary of the walkthrough

This English summary covers agenda control, co-host reactions, chat context, voice coordination, and the current interface direction. The player provides auto-generated Spanish captions; availability and quality of YouTube automatic English translation can vary.

Original source artifacts with readable context first

Each summary precedes its PDF: visible UI, raw chat, log values and reported work records remain distinct.

Visible

Visible UI artifact

1 Aug raw long-session export

The 104-page UI export shows a 4h27m window at minute resolution; it is not a complete transcript or analytical telemetry.

Visible
188 visible KIRA agenda-output markers; 6 operator messages and 6 visible direct-response headers with queue labels of 10s, 12s, 45s, 55s, 1s and 21s.
Visible
4 cloud-down/restored cycles, 29 scheduled retries plus 4 forced retries, 23 visible guardrail rejections and 10 visible memory saves.
Caveat
Markers and headers are what the UI made visible; they do not establish full transcript coverage, causal performance or aggregate telemetry.
Open raw long-session UI export(PDF: Spanish: 104 pages: 1.66 MB)

Measured

Log-derived

1 Aug telemetry analysis

Separate log-derived analysis; it does not derive from the visible UI export.

Measured
4h 27m 35s, 285 generations, 120 cloud and 165 local; local fallback totals 2.62 h (58.6% of the session).
Measured
4 cloud restorations and 194 prefetches are reported from traced runtime events.
Caveat
Its exact metrics are bounded to that instrumented run and are not a production guarantee.
Open telemetry analysis(PDF: Spanish: 9 pages: 368 KB)

Measured

Log-derived

30 Jul traced stress audit

Independent 30 Jul sample; the newer 1 Aug export does not supersede it.

Measured
2h50m25s active agenda/audio, 169 completions, 139 TTS pipelines, and 1,625 fragments across 2h27m32s of audio. First fragment: median .37s, p95 .54s.
Measured
86/87 accepted prefetch gaps were at most 100ms (median 46ms); context mean was 68.6%, with 1,126 pairs evicted across 15 topics.
Visible difference
Four direct questions were answered 14 to 29 minutes late in the 30 Jul audit; six 1 Aug visible queue labels were 1 to 55s. This is an observed difference suggesting improvement, not a guarantee.
Caveat
GLM5.2 and audible Unicode are operator observations, not log-proven. This audit does not test factual reliability, personality or production readiness.
Open traced runtime stress audit(PDF: Spanish: 10 pages: 855 KB)

Reported

Reported engineering record

2 Aug core-domain migration record

Work-record synthesis, not an independent live-repository audit.

Reported
27 modules moved; 150 obsolete references in 45 files; 21 identical-blob renames plus 6 audited import/docstring changes.
Reported
It records 6 entrypoints, compileall, 5,142 collected tests, three introduced defects repaired, and a final reported 5,129 passed / 14 skipped plus one regression.
Not demonstrated
It does not show that main contains the migration, that the 7,009-line llm_engine.py God Object is solved, full DDD adoption or a production regression-free state.
Open reported core-domain migration record(PDF: Spanish: 10 pages: 370 KB)

Visible

Raw visible chat export

70-minute agenda chat export

One qualitative n=1 agenda chat, not telemetry or an evaluation study.

Visible
70 minutes from 14:12 to 15:22; 10 topics; 59 Kira interventions and 2 operator interventions.
Caveat
This is a raw visible chat export; subjective usefulness is self-report, not productivity or learning proof.
Open raw 70-minute chat export(PDF: 32 pages: 540 KB)

Not demonstrated

  • Production-ready streaming, validation with external streamers, or viewer retention.
  • Reliable live-chat understanding in real communities or factual reliability in sensitive domains.
  • Safe autonomous hosting without human supervision.
  • Productivity or learning gains from the single self-report chat case.
  • A complete transcript, universal performance guarantee or independent audit of the reported migration.

From abandoned prototype to source of truth

Since mid-July 2026 the Tauri app is the source of truth: the improved, stable version of the product. CustomTkinter (CTK) was a functional prototype, fully abandoned (Legacy Unstable) without the interruption improvements.

Agenda continuity
CTK · ABANDONED PROTOTYPE
Prototype evidence without interruption improvements
TAURI · SOURCE OF TRUTH
Source of truth: improved and stable
Stream reactions
CTK · ABANDONED PROTOTYPE
Functional but irregular prototype behavior
TAURI · SOURCE OF TRUTH
Source of truth: current development
Memory and chat
CTK · ABANDONED PROTOTYPE
Functional prototype behavior
TAURI · SOURCE OF TRUTH
Source of truth: improved and stable
User experience
CTK · ABANDONED PROTOTYPE
Abandoned prototype
TAURI · SOURCE OF TRUTH
The current product interface

Project direction, without artificial dates

The horizon labels describe intent, not delivery promises. Circularity and factual discipline remain open research questions until they have suitable evidence.

  1. Now

    Refine the Tauri source of truth and preserve observable failure states.

  2. Next

    Prove stream reactions in Tauri and collect structured external feedback.

  3. Later

    Broaden reproducible model and hardware matrices without universal claims.

  4. Open research

    Circularity, factual discipline, conversational novelty and safer live behavior.

Share feedback