GiState
Private beta — waitlist open

One session.
Every model.

GiState is the harness that keeps your AI work coherent across models. Route a live session between GPT, Claude, and Gemini, hand off mid-task, and resume anywhere — your state carries over, compressed and portable, without a single copy-paste.

session-4471 main depth 3 checksum ······
Raw session

          
Compressed gist

Snapshot

Stripe webhook retries were dropping on signature mismatch. Root cause found: the raw body was parsed before verification. Fix applied, staging clean for 40 min.

Atomic facts

endpoint /hooks/stripe
lib stripe@17.4.0
failing_event invoice.paid

Abandoned approaches

  • Bumping the retry window — masked it, never fixed it

Open loops

  • Replay the 3 dropped events from Tuesday
  • Add a signature-failure alert
refinegpt-5 claudegemini state survives every handoff

Memory layers retrieve facts.
GiState preserves state.

Other tools store what your user prefers. GiState preserves what your agent is doing — files reviewed, decisions made, work in progress — and hands it off intact to any model.

Git semantics for context

Branch, merge, checkout. Time-travel through your agent's state with a complete lineage graph.

Portable across models

Compress on Claude. Rehydrate on GPT. Continue on Gemini. The state survives every handoff.

Epistemic boundaries

The model knows what it knows. Configurable strict mode refuses to confabulate when information isn't in state.

How it works

Three primitives compose every workflow.

01

Refine

Compress raw conversation context into a versioned gist. Deterministic — same input, same output, every time.

02

Merge

Atomically combine two states. Truth registry arbitrates conflicts. Advisory locks prevent race conditions.

03

Rehydrate

Reconstruct a model-specific prompt from any gist. Five archetypes optimized per provider.

Built for people who lose the thread

If you've ever re-explained a codebase to a fresh chat window, this is for you.

Agent developers
Give long-running agents a state layer that survives restarts, handoffs, and provider outages.
Engineers in long sessions
Debugging that spans days shouldn't restart from zero every morning.
Teams sharing context
Hand a live session to a teammate as a versioned artifact, not a wall of pasted transcript.
Anyone rate-limited
Hit a cap on one provider, keep working on another. The session doesn't care.

Stop losing context.

We're onboarding a small group first, in order. You'll get an invite, and we'll ask what breaks.