State fragments
Goals, decisions and evidence scatter across prompts, logs and tools.
Agent continuity and execution infrastructure
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.
A model-portable agent runtime and governed context compiler from CuraIQ Labs.
CANONICALContinuity, not another model
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.
Goals, decisions and evidence scatter across prompts, logs and tools.
A more suitable model for the next task may not be the one that began the work.
Without an independent record, permissions and provenance become difficult to inspect.
One durable thread
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.
A provider-neutral record of goals, permissions, evidence, memory and task continuity—independent of the current model session.
A purpose-built, authorised context is compiled from canonical state for each model invocation.
Route work across suitable cloud-hosted and local models while canonical work state remains independent of the provider.
Continuity in motion
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.
Built for agency that lasts
Intelligence can evolve without forcing the work to restart.
Permissions and purpose boundaries can be inspected as tasks move across systems.
Decisions and state changes remain available for review.
Execution can shift without severing the thread.
Private preview
We are inviting a small group of teams working on long-running, high-trust agents to help test the Gimbyl thesis.