Every Claude Code user has watched a new session start from zero. You open it on a system you built last week, ask for a small feature, and the agent begins by rediscovering your own architecture: which service owns the data, which frontend calls it, which type the two of them share. The conversation that explained all of that is gone or compressed into a summary, and the source files show what exists without saying what depends on what. 

So far, the main answer is memory. Claude Code loads CLAUDE.md instructions and its own auto-memory notes at the start of every session, and since September 17, the redesigned Projects, in beta in Claude Code cloud sessions, keep a shared memory across threads, so Claude can recall that “the release moved to Friday” or “who to check in with before touching the billing service.” I wanted to test a different source of context: the dependency records a build platform writes when it creates each version of a component.

Disclosure: I’m an engineer at Bit Cloud, a platform that builds, hosts, and deploys even a single app from its first component, with coding agents working on it over MCP. I asked Claude to build on it to see what an agent can do when the platform records each part and its dependencies as they are versioned. The project and its build records are public.

The system was a small support console I had built with Claude Code earlier, and I wrote up how I built and deployed it separately.

Source link