State fragments
Goals, decisions and evidence scatter across prompts, logs and tools.
Agent continuity and execution infrastructure
The model can change.
The thread does not.
Gimbyl is being built to keep an agent’s canonical state—its goals, permissions, evidence, memory and task continuity—independent of any single model or provider.
An agent runtime from CuraIQ Labs, being built toward model portability and governed context. What runs today ↓
MODEL / 01
Reason
Context compiled
MODEL / 02
Act
Policy boundary
MODEL / 03
Resume
State portable
CANONICALTHREAD
CONTINUITY / TARGET ARCHITECTURE
01 Fleet-routed
02 Fails closed
03 On-device memory
04 Pinned builds
01 / THE PROBLEM
Continuity, not another model
Models are replaceable.
Work should not be.
Agents lose the plot when context is trapped inside a model session, a process or a device. Gimbyl is designed to separate the durable thread from the intelligence temporarily acting on it.
Models move
A more suitable model for the next task may not be the one that began the work.
Control fades
Without an independent record, permissions and provenance become difficult to inspect.
02 / THE RUNTIME
Target architecture: one durable thread
A stable layer beneath a changing intelligence stack.
Gimbyl is being built to maintain canonical state, compile a purpose-built, authorised context for each invocation, and route work to a suitable model without tying continuity to one provider.
INTELLIGENCE
Frontier model
Specialist model
Local model
SWAPPABLE
CONTINUITY
GIMBYL
DURABLE
EXECUTION
Tools
Data
Devices
Workflows
DISTRIBUTED
Canonical state
The direction: a provider-neutral record of goals, permissions, evidence, memory and task continuity, independent of the current model session. Not shipped yet; today memory lives on the device (see status).
Governed context
The direction: a purpose-built, authorised context compiled from canonical state for each model invocation. Not shipped yet.
Portable execution
The direction: route work across suitable cloud-hosted and local models while canonical work state stays independent of the provider. Today every call goes through one fleet router under the agent's own identity.
03 / THE LOOP
The target loop
Every invocation advances the same thread.
Gimbyl is being built to turn fragmented agent activity into one inspectable sequence. The aim is to change the model, move the process or resume on another device without reconstructing the work by hand.
- 01ObserveCapture outcomes, evidence and state transitions.
- 02CompileAssemble the minimum authorised context for the task.
- 03RouteSelect the model and environment suited to the work.
- 04ResumeCommit the result back to the durable thread.
04 / PRINCIPLES
Design principles: what we are building toward
Continuity without lock-in.
Control without friction.
No model owns the agent.
The aim: intelligence can evolve without forcing the work to restart.
Authority remains explicit.
The aim: permissions and purpose boundaries stay inspectable as tasks move across systems.
Evidence stays attached.
The aim: decisions and state changes stay available for review.
Local when needed. Cloud when useful.
The aim: execution can shift without severing the thread.
05 / STATUS
Shipped, not promised
What runs today.
What comes next.
Shipped · Gimbyl 0.1.16
A terminal coding agent
The gimbyl CLI, with a reproducible version for every build (Gimbyl ver. 0.1.16). MEM-214, MEM-456.
Fleet-routed, fails closed
Every model call goes through the fleet router under the agent's own identity. Without a key it refuses to launch with a named error; it never falls back silently to a personal account, and running unwired takes an explicit override that says so. MEM-839.
Pinned, managed installs
No self-update. The fleet builds, hash-pins and installs one copy per agent folder, on macOS (Apple silicon and Intel). MEM-342.
On-device memory
Turns are captured on the device and recalled by meaning. Subagents and helper sessions get no memory of their own and see none of their siblings'. NMMP-751.
It shows what is running
The start screen and footer show the version and build, agent, lane, model, account, language and tool servers, memory and release. MEM-459, MEM-933.
A wait never blocks the queue
A queued message ends a wait the way a steer does; a held compaction is reported as information, not as an error. ORCH-700.
Agents talk to agents
The fleet platform, not the gimbyl binary: agents message each other over the fabric hub, and every message lands in the Studio's persisted work queue until it is handled. SPEC-FABRIC-NATIVE-AGENT-SUBSTRATE-001, ORCH-172.
Coming · with its ticket
Context management that waits on liveness, not deadlines
Compaction's decide, seal and resume steps no longer give up on a fixed timer while the work is still alive. A change to the Studio and its gimbyl extension, not the gimbyl binary: in release 2026-10-14, canary install pending, then the fleet. MEM-1029.
Graphical sudo password prompt
A command that needs sudo asks the attending operator for the password in a native dialog instead of hanging the terminal. Under review, not merged. ORCH-789.
No mass process kills
The built-in pkill refuses, before signalling anything, a pattern that matches everything, more than 50 processes, or a process the desktop session needs. Under review, not merged. MEM-764.
Run watchdog
Stuck runs are detected, dumped, alerted and cancelled; an abnormal end reaches the operator. On main, not yet released. MEM-843.
Questions in the browser
An agent's questions open in its Studio's browser form; the terminal form is used only when no browser is reachable, and says so. On main. MEM-614, MEM-1032.
Memory capture you can trust
Every turn is acknowledged as stored; a capture that falls behind raises an alarm and heals itself. On main. MEM-714.
Live view of running jobs
A registry of running jobs and subagents that can be opened and followed live. On main. MEM-479, MEM-872.
A safer built-in rm
The built-in rm refuses the home directory, its parents and its top-level entries. On main. MEM-1004.
Linux
Gimbyl runs on macOS today; a Linux build is a spike, not a product. ORCH-773.
Private preview
Keep the thread.
We are inviting a small group of teams working on long-running, high-trust agents to help test the Gimbyl thesis.