Direct naar hoofdinhoud
SAITS Logo
Product Update

SAITS Editor as a colorful operating workspace

A local AI workspace for prompts, tickets, preview, evidence, and route-aware execution. The page now stays fully editorial: no screenshots, no clutter, just a cleaner product story with stronger SAITS color and structure.

Core thesis

The product is not the chatbot. The product is the chain from prompt to route to execution to proof.

Local-first behavior, route visibility, ticket ownership, and evidence-driven completion are what make the editor operational.

LOCAL

Default operating route

PREVIEW

Built into the work loop

TICKETS

Traceable from intake to done

EVIDENCE

Checks and proof stay visible

Local-first editor

Project files, preview, shell context, and writing flow stay anchored to the Mac instead of disappearing behind a remote interface.

Route-aware execution

LOCAL, LOCAL + Internet, provider-key routes, and remote brain paths stay explicit so the operator always knows what handled the task.

Ticket-first delivery

Intake, slice selection, execution, validation, and done-gates are part of the same operating model instead of side processes.

Controlled proof

Preview, smoke checks, status, and evidence keep the result verifiable. The product is designed to finish work, not just generate output.

Operating model

One workspace, several routes, one accountable chain.

SAITS Editor does not behave like a single floating chatbot. A prompt enters the workspace, gets attached to a ticket or slice, moves through a route decision, passes a filter layer, executes into the active project, and only counts as done when the proof holds.

01

A prompt enters the workspace and is linked to a real ticket or an active slice.

02

The route layer decides whether the work stays local, uses internet capability, or moves through a remote/provider path.

03

The filter layer checks whether the action is valid, which ticket owns it, and whether it may execute.

04

Execution writes to the active project, keeps preview aligned, and records what changed.

05

Checks, evidence, and final gates determine whether the work is actually done.

Route

LOCAL

The primary route on the Mac. Chat, project writes, and working context stay on-device.

Route

LOCAL + Internet

Still local, but web context can be added for recent information or live lookup without changing the core operating route.

Route

MONSTER PC

Remote compute for heavier work, broker-backed flows, and extended brain capacity. Useful, but not allowed to break the local route.

Design direction

Cleaner composition, brighter gradients, stronger separation between sections, and no screenshot clutter competing with the product story.

Front-end

The visible control surface

  • Monaco editor
  • Preview states
  • Sidebar and ticket box
  • Command and search flows
  • Terminal and shell views
Back-end

The route and execution engine

  • Node.js server
  • Route logic
  • Auth and token context
  • Project write flow
  • Evidence and smoke support
Local AI

The on-device chain

  • Ollama runtime
  • Active soul selection
  • Model-aware chat
  • Project-relative writes
  • Offline-first working mode
Brains and keys

Explicit external routes

  • API-key profiles
  • Claude route
  • Remote broker path
  • Monster brain compute
  • RCP relay back to workspace
Visible controls

The interface keeps state legible

The point is not just power. The point is visible power: route badges, token state, preview control, ticket state, and runtime status remain readable inside the same operating surface.

Route badgesInternet togglePreview stateAuth stateToken stateRuntime stateIoT stateSettings menuTerminalShell panelsSoul switchTicket stateGates open / closedEvidence status
Why this page changed

The product reads better without a screenshot wall.

The previous version tried to prove the product with too many images. This version uses color, spacing, route language, and execution logic to explain the editor more clearly and with more confidence.

Less visual noise
More deliberate color
Stronger section hierarchy
Cleaner product brief tone
What already works
  • Local chat is active with the current soul and runtime model.
  • Ticket-first flow runs from intake to validation to done.
  • Preview is part of the main workspace, not a separate tool.
  • Local internet remains a capability inside the local route.
  • Remote routes stay visible without replacing the on-device workspace.
What still needs improvement

Smarter real-time lookup

Internet mode should fetch live data directly when the prompt clearly depends on current information.

Sharper ticket evidence

Probe results, chats, and execution outcomes should read even more clearly inside each ticket.

Tighter UI rhythm

The sidebar, ticket surfaces, and preview hierarchy can be calmer and more deliberate.

Harness alignment

Local routes should depend less on irrelevant remote state during startup and smoke validation.

Release brief

SAITS Editor is a local AI workspace with route control, preview, tickets, and proof built in.

This pass removes the screenshots, sharpens the product story, and gives the page a brighter SAITS gradient system so it feels more like a deliberate product launch page and less like a stitched gallery.

Back to products