A mind for your machine

Ask in
English,
answer in kind.

Sysmind runs your Linux box — updates, disk, security, services — and talks to you in whatever language you think in. It answers in that language. But the commands stay shell, always, untranslated. Shell is the only language the machine reads.

Dig down
the same answer, twice a few of many · language: auto
for youen · auto
for the machinenever translated
$ apt update && apt upgrade
identical in every tongue — a translated flag is a broken command
01 — The profile

Trust is a depth,
not a switch.

Sysmind has four modes and four rings of context, and they are the same axis: how deep you let it dig. Shallow, it reads the surface and explains. Deep, it knows your kernel, your failed units and your Parrot toolchain — and it may act on them. You set the depth. You can pull it back up any time. It starts at Assistant, two down, because the default should be the one that asks.

02 — The graft

Every permission
is earned separately.

A command is filed at three tiers: the tool (apt), the subcommand (apt:update), and the exact line you ran. The tiers are independent. Approving the bare tool does not grant the subcommand, and no approval anywhere grants apt remove. There is no scope creep, because there is no scope inheritance.

What does spread is use. Run the same subcommand three times and sysmind offers to graft the approval wider — once, out loud, as a question you answer. Nothing widens quietly.

~/.config/sysmind/config.json · approvals
Base · tool
apt
not approved
Only ever consulted for a bare command with no subcommand at all.
Sub · subcommand
apt:update
not approved
Granted only by promotion, and only after you say yes to it.
Tertiary · exact line
apt update
not approved
The natural tier. What you approve the first time you're asked.
Nothing is approved yet. Run it and sysmind asks — the way it will the first time, on your machine, with the blocklist up.
03 — The fence

Some things
are fenced off.

Sysmind is not a script that YOLOs sudo. Ten tools are refused outright before the model is ever consulted — it cannot suggest them, and it cannot run them. A short list of genuinely safe maintenance is allowed to run itself once you're deep enough. Everything between those two lists is a conversation.

The fence is a config line, not a personality. blocklist_enabled: false takes it down — it's your machine. But it's up by default, and turning it off is a thing you do on purpose, in a file, in daylight.

Refused · blocklist
Never suggested, never run
rmddmkfsfdiskmkfs.ext4 mkfs.ext3mkfs.ntfsmkfs.vfatpartedgparted
Safe · auto-runnable
May run itself at depth
apt updateapt upgradeapt autoremove systemctl restartlogrotatejournalctl --vacuum-time
04 — What it runs on

Your laptop.
That's the whole list.

Sysmind is a handful of Python files with no dependencies outside the standard library, talking to a model you pulled yourself through Ollama. No cloud, no account, no telemetry, no API key. Built for Parrot OS — it knows about anonsurf and firejail — and it runs fine CPU-only.

The model
qwen3:8b
The sweet spot at 8 GB: strong on shell and configs and near-complete Urdu, Apache-2.0. ~5–10 tokens/sec CPU-only on a modern laptop.
Smaller / larger
1.7b → 32b
The installer reads your RAM and picks: qwen3:1.7b at 4 GB, qwen3:14b at 16, qwen3:32b above. Bigger qwen3 speaks better Urdu.
Setup
./setup.sh
A health check, then four questions: how hands-off, how much RAM, which language, how paranoid. Then just type sysmind.

It's your machine.
Talk to it.

Sysmind is free and runs entirely on hardware you own. It's in early access — we're looking for people running Linux who want to argue with it in their own language and tell us where it's wrong.

Parrot OS / Debian · Python, stdlib only · local models via Ollama
No cloud · no account · no telemetry · nothing leaves the machine