HIVEMINDUNLIMITED
CONTEXT
Their sessions never compact. Every turn compiles from the whole history, sized to a budget you choose per turn.
TALK FOREVER. NO SLOP.
[ HIVEMIND FOR HARNESS DEVELOPERS ]
Every agent framework, IDE agent, and orchestrator ends up writing the same thing: a compaction routine that throws away what the user said. Hivemind replaces it with two calls, and every agent built on your harness remembers everything, forever.
YOUR USERS BUILT THEIR AGENTS ON YOU.
WHEN THE CONTEXT FILLS, YOUR HARNESS IS THE THING THAT FORGETS.
THAT ISN'T A MODEL LIMIT.
IT'S A HOLE IN THE LOOP, AND THE LOOP IS YOURS.
You wrote the summariser. You tuned the window. You shipped "memory" as a vector lookup bolted to the side. Your users still open a session that knows nothing about yesterday.
Before the model: POST /turn with the message, the session, a token budget, and your recent history. The service stores the message, recalls what matters from everything this session and every session before it, and returns one contiguous block of messages sized to the budget. Hand that block to the model as the prompt, or wrap it with your own system prompt above and instructions below.
After the model: POST /conversation/store with the reply. The exchange is complete and recallable.
That is the whole contract. Tool calls, retries, and streaming stay where they are: in your loop. Run as many tool cycles as you like between the two calls and store only the final reply. Stream first, compile second. On a restart, rebuild your local buffer from your own store and land in the same session. Everything a long-lived host needs is written down at the wire level, in the docs, with working code in four languages.
Their sessions never compact. Every turn compiles from the whole history, sized to a budget you choose per turn.
TALK FOREVER. NO SLOP.
Facts said once come back when they matter, on either side of any past exchange.
SAID ONCE. KNOWN ALWAYS.
Every agent your harness runs for them reads and writes one mind, per project, per session.
ONE MIND. EVERY AGENT.
What was stored, what was recalled, what was compiled, and why. Their audit trail, in their own database.
NOTHING HAPPENS OFF THE RECORD.
Memory lives in a cluster they own. Your harness never holds it.
CUSTODY IS THE FEATURE.
Plain HTTP with a bearer key, any language, no library to vendor. Two endpoints on the hot path, three pieces of client state: a turn counter, the open exchange id, a rolling history buffer. The compiled block goes in where your prompt already goes. Your model, your provider, your key, untouched.
Read the loop, the chat-host rules, and the message shapes. Wire it into your harness against a trial account. Every agent built on you remembers by tomorrow.