Claude Code adds assisted design and cross-session chat

Two additions to Claude Code on 22 August, and neither one is a new model: assisted design and cross-session chat. StartupHub.ai published it and it circulated the same day via Google News. These are changes to how you work inside the CLI, which is where this kind of thing either shows up or does not.

The second one is worth pausing on, because it touches a limitation anyone using Claude Code daily has run into. Until now, each session lived alone.

The terminal silo

You open three terminals for three lines of work and you get three contexts that never talk to each other. What one session figures out about the database schema never reaches the one touching the frontend, and what the third one just broke in the tests is news to nobody. The usual workaround has been copy and paste between windows, or leaving notes in a shared file and hoping the other session reads them.

Cross-session chat changes the topology, not the model. One session can address another that is still alive and hand it a finding or ask it for something, with the receiving session's context intact.

It is not the same as a subagent

The distinction is worth marking, because people will conflate them. A subagent is born for a task, works in its own context and returns a report: it is disposable by design, and that is a virtue when you want to isolate a long search without polluting the main conversation. A peer session is something else: it carries hours of work, it has read files, failed and corrected itself, and it knows things that do not fit into a startup prompt. Being able to talk to it means reusing all of that context instead of rebuilding it.

The price of that advantage is coordination. Two sessions that talk to each other are also two sessions that can edit the same file with two different plans. Parallelism without discipline does not give you more throughput, it gives you more merge conflicts.

Design in a terminal tool

The other piece sounds contradictory: design inside a CLI. The practical reading is that the real friction point is not drawing, it is the handoff. Someone decides a visual direction in one tool, someone else translates it into components in another, and along the way decisions nobody documented get lost. Having the design step happen where the repository already is shortens that trip, especially on small teams where the same person does both jobs.

We do not expect it to replace a designer. We do expect it to cut down the number of generic screens that come out of a prompt with no reference, which is the most visible problem in generated frontend today.

How it fits with what was already there

Claude Code has been stacking primitives for a while: skills to package reusable instructions, subagents to delegate, hooks to attach shell commands to lifecycle events, MCP to call external tools and plugins to distribute all of it. Almost all of them are vertical: the session sends work downward or outward. Cross-session chat is the first clearly horizontal piece, and that is why it moves more than the headline suggests. The official Claude Code documentation is still the place to check the detail of each primitive before building anything on top.

Who this changes something for

For a solo developer with one session open, not much. For someone maintaining a monorepo and working three fronts at once, quite a lot: the handoff stops being a hand written summary and becomes a conversation between two contexts that already know what the project is about. For teams, the interesting question is whether this ends up as a shared way of working or just an individual shortcut.

What to watch

Operational questions remain: what permissions a message arriving from another session inherits, whether the scope stays on the same machine or crosses machines, and what it costs to keep sessions open and listening. None of that gets settled in a headline.

Our reading, with the information published so far, is that cross-session chat is the change most likely to alter the daily work of anyone already juggling several windows, and also the easiest one to misuse. It gets interesting when someone shows a real flow of two sessions coordinating without stepping on each other, and we have not seen that yet.