Omniscio documentation
Browse all documentation
  1. Getting Started19
  2. Sessions & Agents135
  3. Inbox & Notifications68
  4. Projects & Tasks99
  5. Automation & Scheduling77
  6. Knowledge & Memory28
  7. AI Features71
  8. Integrations112
  9. Plugins & Marketplace42
  10. Cloud & Teams52
  11. Settings & Customization79
  12. Account & Billing28
  13. Troubleshooting80
  14. CLI & API Reference28
  15. Legal & Policies5
  16. Uncategorised17

Session states and project looks

You can give each session state its own colour, icon and words, and give a project its own colour that the workspace wears while one of its sessions is open. Nothing changes until you pick something, and both travel in your look file.

What it is

Two more ways to make the app read the way you think: the words and colours your sessions use, and the colour a project brings with it.

Session states. A session shows one of five states — running, waiting (parked on a usage limit), needs you, done (archived) and error (which also covers Stalled? and Interrupted, because they already share one red). Settings → Appearance → Theme & Visual → Session states gives each one a colour, a Lucide icon and the words it shows. Change them once and every surface agrees: sidebar rows, session cards and the inbox all read from the same record, so the sidebar can never call a session "Busy" while the inbox still says "Running".

Project looks. Give a project a colour (its own Appearance pane, or the Project looks card) and open one of its sessions: the workspace wears that colour, and the project's session rows carry a small marker so you can see at a glance which project you are looking at. A project can also borrow one of the six ready-made looks' colour sets — Midnight's deep navy, Paper's warm paper, Neon's magenta — without taking its stylesheet.

Where to find it

  • Session states: Settings → Appearance → Theme & Visual → Session states.
  • Project looks: the Project looks card in Settings → Appearance, or a project's own Appearance pane.

How it behaves

  • Nothing changes until you pick something. With every box untouched the app looks exactly as it does today, and waiting stays the orange it has always been.

  • Custom CSS can read them. Each state publishes --session-state-running, --session-state-needs-you and so on (plus an -rgb twin), so your own stylesheet or a mod can match the colour you picked instead of guessing a hex.

  • The switch turns the whole language off without erasing what you chose, so it is safe to try.

  • Mods Safe Mode and boot Safe Mode show the stock states — a rescue start is never wearing a look you have to un-pick first.

  • Your theme record is never touched. A project colour changes what you see while that session is open; it never changes the theme you chose, and it goes away when no session of that project is open.

  • The marker sits beside the status dot, never over it. Status still wins on a row, and a session with its own colour keeps it.

  • One switch in the Project looks card turns the whole thing on, and off again in a click. It starts off, because the accent repaints the whole workspace and most projects already carry a colour from their rail — nothing is restyled until you ask for it.

Both ride your look file. Session states and the per-project colour-set choices are optional parts of an exported look: they apply with everything else, all or nothing, and Undo puts them back. A part the file does not carry is left exactly as you have it, and a project this computer does not have is simply skipped.

Try it. Tell your agent: "make my needs-you state blue and call it On you", or "give the Docs project the Midnight colours".

Related

Last verified 2026-10-18