← Products

Release candidate

An assistant that asks permission.

smolit runs on your infrastructure, uses tools within the permissions you give it, and makes its steps possible to follow.

Join the waitlist

The problem

AI helps — but control tends to disappear into the background.

Plenty of assistants are quick to get hold of.

But which model is working, where your input goes, which tools get access and which actions are actually carried out is often hard for the person using it to follow.

The solution

smolit makes control part of the interface.

Your input doesn’t have to leave your device.

smolit brings together local models, clearly approved tools and actions you can follow afterwards.

You decide what the AI may see, which tools it may use, and when an action needs your approval.

The interface

What you see when you open it.

smolit interface: the conversation on the left, the logged sequence of every action on the right.
Conversation and trail. The exchange on the left, every step written down on the right. Real interface, development state.
Agent view with approval cards and one rule per agent.
Approvals. Each agent has its own rules about what may leave. Real interface, development state.
Tools and connections with risk ratings.
Tools. Approved one by one, each with a risk rating. Real interface, development state.
Sequence view: five chained steps run locally, one external step waiting for approval.
Every step visible. Five actions done locally, the one external step waiting for your approval. Real interface, development state.
“Privacy and egress” page with redaction profiles and a before/after preview.
Cleaned up before anything leaves. You can see which fields are replaced before a request leaves the device. Real interface, development state.
Routing view: task classes by risk, sensitive ones pinned to local models.
Routing by risk. Sensitive tasks are pinned to local models. Real interface, development state.
Task board with three columns and links to the agent runs behind each card.
A workplace, not a chat window. Tasks trigger agent runs; every card shows what worked on it. Real interface, development state.
Calendar showing your own appointments alongside scheduled smolit actions.
Calendar. Your appointments and scheduled actions side by side. Real interface, development state.

The principle

You decide what is allowed to happen.

smolit asks before it acts. Every action that changes something or goes outwards needs your click, and is written down. Models run on your hardware by preference; a stronger cloud model is only brought in if you explicitly allow it — and requests going there are anonymised first.

What you do with it

A workplace, not a chat window.

The cockpit comes with it — the working environment for knowledge, documents and tasks. smolit also brings research tooling: a fixed path from idea through experiment to analysis, with limits it cannot cross. Controlling the lab itself sits next door in laborium.

For those who want the detail

What runs underneath.

  • Rust core without a UI; interfaces in React via Tauri 2, for desktop and Android
  • Coupled solely over loopback WebSocket IPC — not reachable from outside
  • Models local by preference; cloud models only after explicit approval, with requests anonymised first
  • smolit picks tools and processing paths within your permissions, with local fallbacks
  • Speech handled locally (whisper.cpp, Piper) · ground rule: when in doubt, nothing happens
  • AGPL-3.0 · version 1.0.0-rc.2, reproducible build

Where it stands

Where smolit is.

Today

  • Release candidate 1.0.0-rc.2 with a reproducible build.
  • Approvals, tool rules and the activity log are working.
  • Models run locally; the cloud only after explicit approval.

Next

  • The audit view. Actions are already logged; making that searchable is next.
  • Ready-made installers — today the way in is the source code.
  • Calling tools independently, currently in active development.

After that

  • Publishing the repositories under AGPL-3.0.

Works with laborium and publishes through mesorium. smolit gets a permanent home on the smolit node — optional, not a requirement.

Waitlist

Try smolit early.

When we open new test places, the people on the waitlist hear first.

Join the waitlist

Non-binding, and not a guarantee of access.