Page 3 of about 36 results (0.001 seconds)
A collaboration prototype for teams sharing work, testing ideas, and getting timely feedback. The example feed follows xo_builders and quirq_ai. A categorized attention rail brings the people waiting on your reply to the top, …
All your agent and thread activity in one place. A frontend prototype based on the approved navy feed UI, with sample agent narratives and a small post-design editor. The UI and engine can be developed independently.
Install this plugin, then ask Codex “Open XO Space.” Codex installs the local server on first use, starts it and opens the Space UI in its browser when available. Projects, agent activity, todos and usage stay in your local …
The server serves the actual space_ui/ assets from this checkout and supplies deterministic, fictional API data. It does not start an agent, read private workspace files, call upstream services, or support writes. The ten …
Fonts are bundled so the interface works offline without sending font requests to a third party. The default Grove theme retains its existing Inter files.
A 2:49 explainer for Innernet, narrated by Lily (ElevenLabs), built as one HyperFrames composition in an engraved-plate style. It plays at the top of the in-app field guide (/guide) of the Innernet app at the repo root.
Actual session directories are ignored by Git and excluded from Next.js deployment traces. They are created at runtime, never packaged with the app. Do not commit or share them: they can contain comments, messages, and uploaded …
The Quirq background set, copied from the quirq workspace (quirq/quirq-backgrounds). Dark light studies and glass forms; the same family as the quirq.ai hero (public/brand/quirq/mobius.jpg). Two exact duplicates in the source …
This folder is the golden sample of a project's portable metadata: exactly what .xo/ holds right after XO Space first meets a folder, however the folder got into the projects root. tests/test_xo_structure.py compares every …
This folder is the sample of what XO Space keeps on one machine, outside every project. tests/test_quirq_state_layout.py holds the code to it: every store writes inside one of these folders, services/storage/layout.py names …