Building in the open, before it's ready

Tixim has been in development long enough to have 68 crates, 33 packaged services and 67 feature specs, and short enough that none of it has a version number worth quoting. This page exists to close that gap: to say what the thing is while it is still being built, rather than announcing it fully formed and hoping the description survives contact with the code.

What it is

Tixim is a multi-agent development environment. You describe work as a workflow; the engine schedules it as a DAG, runs each step inside a rootless container, and records what happened in enough detail to replay it. Agents call whichever model suits the step — hosted or local — under a budget, and a committee of reviewers decides whether the result lands.

The parts that matter are the boring ones:

• Isolation is structural. Steps run in the sandbox. There is no fallback path that quietly executes on the host when namespace setup fails, because a fallback like that is how isolation stops meaning anything.
• Nix is the packaging story. Tools, skills, services, agent harnesses — all derivations. This is what makes a run reproducible rather than merely repeatable.
• Logs are data. Timestamps, stream, worker identity and sequence travel as structured fields, never as a prefix baked into the line. Consumers read fields; they do not parse metadata back out of formatted strings.

What’s next

The near-term roadmap is on the landing page. The short version: durable run records, budget enforcement, step memoization, and a warm container pool so a step starts in milliseconds instead of seconds.

If you want to know when it opens up, the signup form is at the top of the page. It stores one address and sends one message.