Programs in boxes, and you in charge
Every .deb, Flatpak, AppImage and plugin runs in a box that starts with nothing. A window like a phone's asks before anything is shared, and every switch starts off.
The boxes
A box is a fence around a program, built with bubblewrap, the same tool Flatpak uses.
What a box keeps away from a program
What runs in a box
What a permission window shows
The window takes the keyboard as it opens, so it works without a mouse, and Escape leaves the choices as they were. The desktop passes no made-up key press or click to the window, so a program can't answer for you.
Permissions
When an app is installed, Trindle lists everything it wants in plain words, with a switch for each one. All the switches start off.
A box can ask for the internet, sound, the microphone, your folders, the camera and plugged-in devices, Bluetooth, notifications, to start by itself at login, the screen, older windows, or to work outside its box (meant for terminals). A plugin can also ask to share your mouse and keyboard with another computer, read the files you copy, or reach only your home network.
A dot shows in the top right corner while any app uses the camera or the microphone, or records the screen. It is orange for the microphone, teal for the camera and blue for the screen. It sits on the app's window tab too. One button in the ring cuts the microphone for every program, and only you can turn it back on.
AI coding agents in a box
Programs such as Claude Code, Codex, Cursor's agent, Gemini, Aider, OpenCode, Goose and Amp (you can edit the list) run in a fence of their own. They can read the system, the logs and the installed programs, and run commands, but they can't see your files.
They see an empty private home folder of their own, kept between runs, not yours. Other people's home folders, your mail, your keyring, ssh-agent and the session are hidden. Other programs are invisible to them, and anything that looks like a key or token is removed from their environment. They get no screen, sound or keyboard, so they can't see the screen or press keys.
You choose what the fence shares
An agent can ask for a folder, and a window outside the fence asks you: Share for this session only, Share always or No. Hidden folders such as .ssh and .gnupg, and mail and password folders, can never be shared.
Inside the fence, ssh and sudo are stand-ins that ask Trindle, outside the fence, to do the job. ssh works only with computers you list, using a key made for the fence. sudo works only after you approve the exact command in a window. We haven't tried those two on a real screen yet.
What it can read without asking
What it can do only after you say yes
An on-screen window asks first. The cross, Escape, closing the window, or two minutes of silence all count as no. After you say yes, it can start an app, bring a window to the front, close a window, change one Trindle setting from a fixed list, set light or dark and the accent colour, install or remove a Flathub app, change a Flathub app's permissions, join a known or open Wi-Fi network, pair a Bluetooth device, or undo a previous change.
An assistant, inside a fence
Trindle has a small MCP server, the standard way an AI assistant such as Claude talks to programs on your computer. It runs on your computer only and is not a network service.
trindle-mcp. Trindle's Settings has no switch for it.Nothing needs an assistant. You can still do everything by hand, offline, with the mouse and keyboard.
Trindle takes a snapshot before and after every package change, and the start-up menu lists the last twelve, so you can start from one even if the computer won't start. This needs the Btrfs disk the Trindle Installer makes.
The installer switches on a daily snapshot of your home folder. Each day's copy is kept for a week by default, or for three days, two weeks or a month if you choose. One switch turns it off. A computer upgraded from an older version may have it off to begin with.
At the start, the installer asks whether to encrypt the disk. You can choose not at all (the starting choice), a password that you type at every start, or this computer's TPM chip, which needs a TPM 2 chip. Encryption needs a computer that starts with UEFI. There is no separate recovery key, so the password is the way back in.
Updates, plugins, the network and the sockets
Still being built
These are planned and are not in Trindle yet.
- Locking the system files by default. You can already lock them with a switch in Settings, Snapshots, but the Trindle Installer doesn't turn it on yet.
- The Permissions page listing the boxes round AppImages and programs started from Folders.
- An assistant that can restart a misbehaving program, change that program's own settings or clear its cache, and never change Trindle itself.
- A signed whole-system image, and a signed start-up for Trindle itself.