My Workspace
| # | Task | Repo | Route | Status | PR |
|---|
New Task — opens its chat with Oracle
Ask Iris about this task
She can see this task's status, transcript, diff and files. Asking her changes nothing and queues nothing.
My Profile
My Knowledge
Facts, decisions and preferences Oracle should carry into every conversation. Company records apply to everyone and win if they conflict with yours.
My email addresses
Any of these signs you in to this account, and a report sent to any of them appears in your Reports. One report is listed once, however many of your addresses it went to.
My usage
My fallback chain (SBL-011)
| Order | Credential | Kind | Env ref | Health |
|---|
Personal accounts power only your tasks. Values are never shown — only the env-var name that holds them.
Link a personal account
Terminal
A shell in the runner container — node, npm, git, python3, pandoc, LibreOffice, Chromium. Work inside it is free. Anything that leaves it — a push, a deploy, publishing — is held for approval, exactly as it is for Oracle.
How to use this
2. Type a command and press Enter — ls, npm test, git status, python3 script.py. cd is remembered between commands, so you stay where you moved to.
3. Three kinds of command. Most run immediately. A few ask first — anything that rewrites history or deletes in bulk. A few are refused outright and become an approval request instead: pushing, deploying, or sending anything outside the container.
4. The container is temporary. It is yours until the session ends. Commit and push (which asks for approval) if the work needs to outlive it — files left in the container are gone when it stops.
Long output is trimmed from the MIDDLE, so the command you ran and its final result are both always visible.
Spaces
A Space holds files and the conversations about them. Anything you ask Iris inside a Space already has its files — you never attach them twice. Your uploads stay yours: they are not read by the fleet or by any report.
Bug reports
Things handed to Oracle to investigate. Oracle decides whether each one is a fault it can fix, or a change that needs approval first — you are never asked to make that call.
Report a bug
Sessions
Work done in Claude Code or Cowork on your own machine, brought here so it is visible alongside everything else. These did not run on Sable's runner.
Where do these come from?
One session, by hand: press Import a session above and pick the .jsonl file. Importing the same file again UPDATES that session rather than making a second copy, so it is safe to re-import as work continues.
All of them, from the machine: run the courier, which reads the folder directly:
Only the conversation is carried over — the messages, and counts of the tool calls. Sable does not receive your files, your keys, or the repository itself.
Reports
Upload a report
Fleet — AS Agents
Purpose and department come from the fleet roster; status comes from the
fleet's own /status. An agent in the roster that is not reporting is shown as
such rather than hidden.
Admin
Team — who is using Sable, and how much
| Member | Role | Tasks | Done | Failed |
|---|
Settings
Iris waits this long after you stop speaking, then sends. At 0 it fires.
Default OFF. With it off, Iris drafts an email and you press Send — so a misheard voice command can never mail a colleague or customer. Turning it on removes that gate for every outbound action. Change is audit-logged.
Credentials — org keys & per-user keys
| Label | Assigned to | Kind | Env var (IT sets value) | Status |
|---|
Per-user keys serve only that user's tasks. Sable stores the variable NAME only — IT pastes the value into Railway under that exact name.
Routing rules (SBL-012) — edit, no deploy
| Ord | Task class | Match keywords | Model | Runner |
|---|
Users
| Coding | Reports | Admin | Active |
|---|
A person who does both registers for both services under one login. Report-only users never see coding; coding-only users never see reports. Admin and services are independent — an admin may legitimately lack a service.