TacidOSpre-releaseApache-2.0NO TELEMETRYSTATIC
TacidOS
DevelopersGitHub
In development Built on NixOS

Your machine.
With agency.

A Linux system that can act on your intent.
See the plan. Set the rules. Keep control.

Tacid brings an AI agent into the operating system, with the boundaries a machine you depend on needs. You set the rules. The system enforces them.

Explore how it works Get started

Early development. No supported public release yet.

tacidDevelopment recording
tacid ask --diff install ripgrep
I will install ripgrep.

  + install ripgrep (cli)

  Reversible: system configuration to generation 1.

--- a/mind/agent.nix
+++ b/mind/agent.nix
@@ -5,4 +5,7 @@
 # transaction. Your own configuration belongs in owner.nix, which Tacid never writes.
 { ... }:
 {
+  tacid.packages.cli = [
+    "ripgrep"
+  ];
 }
A visible diff. A recorded decision.43da513
Excerpt from the original CLI demo. The Nix builder and privileged operations are simulated in this recording. View the full session
Built on a solid foundation

Agency, with boundaries

Let it do the work.
Keep the decisions that matter.

Useful autonomy starts with a system you can inspect, constrain, and recover.

01

See the change before it happens.

A request becomes a typed transaction and a readable configuration diff. Policy decides what can run. The model cannot approve its own work.

Follow a transaction
02

Keep a way back.

System generations make configuration changes reversible. Data and external effects have their own limits, made explicit before you approve.

Understand rollback
03

Choose the intelligence. Keep control.

Use local models or connect your own provider. A separate network gate handles credentials and policy. The agent never gets a root shell.

Read the security model

One path for change

The agent proposes.
The system decides.

A package install, a service change, or a repair goes through the same controlled process.

Inside the architecture
  1. 01

    Understand the request

    The agent inspects the machine and proposes a typed change.

    Agent
  2. 02

    Check the boundaries

    The keeper checks policy and reversibility, and requests approval where needed.

    Keeper
  3. 03

    Apply and verify

    The privileged core activates the change. Health checks and the journal record the outcome.

    Stem

Where we are

Working code.
Clear next steps.

Tacid is an engineering project in active development. Here is the evidence behind the ambition.

Source snapshot
dcb3832 · Development status

21
Rust crates in the source
898
Tests reported by the project
46
Architecture decisions, documented

Implemented

A system you can investigate.

The transaction engine, policy, audit journal, CLI, terminal interface, and installer are in the source. Installation and rollback have run in emulated machines.

Explore the implementation

In development

A release we can stand behind.

Real hardware validation, release promotion, and end-to-end channel testing remain. The graphical shell and advanced device workflows are still ahead.

See what comes next

For people who build

Know your tools.
Help shape what comes next.

For developers, embedded engineers, and curious people who want to understand the system they run.

The implementationExplore the developer portalThe thinking behind TacidRead the manifestoBuild with usFind your way to contribute