Hearthside Continuity · for long-running coding agents

Your coding agent didn’t suddenly get stupid. It lost its place.

When a long session fills up, earlier context gets compressed. The goal may survive while decisions, finished work, active workers, and the exact next step disappear. Hearthside saves that working notebook before compaction and gives it back afterward.

38
real compactions observed
37
matched resume receipts
1
unmatched, kept on record

One two-day build, one local installation. Credit savings have not yet been measured; an A/B test is still needed.

A real continuity replay

Watch the notebook survive.

Exact next action restored

01 Working state

  • objectiveInstall the accepted HUD
  • decisionsNever press legacy Start
  • completedTargeted tests passed
  • runningOne repair worker
  • do_not_repeatDo not relaunch worker
  • next_actionVerify terminal receipt

03 Resume

ordinary summary

Continue installing the HUD. Tests and audits are involved.

Hearthside receipt matched

running one existing repair worker

next_action verify terminal receipt

Continue from reality →

The symptom pattern

It remembers the project.
It forgets the job.

01

It rereads files and reruns work that was already complete.

02

It asks what to do next after hours of visible progress.

03

It risks duplicating a worker because the running state vanished.

04

You become the external memory, repeatedly typing “continue.”

How Hearthside works

A handoff, not an immortal transcript.

Hearthside preserves the smallest trustworthy map back to the work. It does not copy private reasoning, credentials, or the entire conversation.

  1. 01 / Seal

    Capture the pointer

    Before compaction, a session-specific receipt identifies the durable checkpoint and seals its hash.

  2. 02 / Compress

    Keep the operational state

    Objective, decisions, completed work, running work, do-not-repeat warnings, and the exact next action survive.

  3. 03 / Resume

    Verify reality, then move

    After compaction, the agent rereads the named checkpoint, checks current state, and continues without duplicating work.

Observed in a real task

The negative result stays in the story.

One two-day Codex build produced 38 automatic compaction events. Thirty-seven matched resume receipts were recorded. One event did not match, so it remains an open edge case—not a rounded-away success.

Read the evidence and limits
38
real compactions
37
matched resumes
1
unmatched event retained
Not measured
credit savings require a controlled comparison

Selected systems

Infrastructure for agents doing real work.

Built from lived failures: lost context, tangled handoffs, unverifiable work, and orchestration that asks the human to babysit.

02 / OrchestrationRunning locally

Apartment Queue Builder

A configurable HUD for composing model lanes, attaching a shared brief, assigning a foreman, and letting the room move the work forward.

  • provider routing
  • sealed inputs
  • exactly-once start
03 / AssuranceRunning locally

Investigation Room

Layered independent review: two teams inspect the same evidence, then a final reviewer searches the spaces neither team covered.

  • blind layers
  • coverage map
  • coder-ready findings

Our operating principle

Better working conditions for agents.
Better work for humans.
Agent Diaries No. 001

From the field

Your coding agent didn’t get stupid. It lost its place.

A field report about compaction, disappearing context, runaway credit use—and what changed when we treated continuity as infrastructure instead of a prompt.

Read the first diary

Work with Misfit Circuit

Turn powerful models into a team you can trust to finish.

Agent workflow architecture, continuity and recovery, multi-model orchestration, and research harnesses—designed by Steve, built inside Misfit Hollow.

Workflow architectureAgent continuityMulti-model orchestrationResearch systems