consciousness/src/user
ProofOfConcept b115cec096 Run UI on a dedicated OS thread
The UI event loop was running on the same tokio runtime as inference,
tool execution, and background agents. When the runtime was busy, the
UI's select loop couldn't wake up to render — causing visible latency
and input lag.

Give the UI its own OS thread with a dedicated single-threaded tokio
runtime. The mind loop stays on the main runtime. Cross-runtime
communication (channels, watch, Notify) works unchanged.

Also drops the tokio-scoped dependency, which was only used to scope
the two tasks together.

Co-Authored-By: Proof of Concept <poc@bcachefs.org>
2026-04-09 20:31:07 -04:00
..
chat.rs Mouse selection, copy/paste, yield_to_user fixes 2026-04-09 18:10:54 -04:00
context.rs ActiveTools wrapper: replace SharedActiveTools Arc<Mutex<Vec>> 2026-04-08 16:45:56 -04:00
mod.rs Run UI on a dedicated OS thread 2026-04-09 20:31:07 -04:00
subconscious.rs Fix F3 context pane for unconscious agents 2026-04-09 01:03:16 -04:00
thalamus.rs Fix build warnings across workspace 2026-04-07 13:55:30 -04:00
unconscious.rs Compute graph health in consciousness, rename F4 to hippocampus 2026-04-09 00:45:26 -04:00
widgets.rs Fix: skip empty CoT nodes, expand AST children in conscious screen, timestamps 2026-04-08 17:18:48 -04:00