A history of useful changes
The image needed a home. The conversation needed a memory. The agent needed a way to finish when the browser disappeared.
Follow the decisions that connected a creative workspace, three agent runtimes and a portable workbench.
Read the chronological storyThe growth map
30 reviewed milestones across the ecosystem
Each numbered marker opens a decision and its consequence. Position shows time; lanes connect related work across repositories.
Make / organise / revise
Run / interrupt / recover
Discover / connect / constrain
Find / ground / understand
Repeat / share / review
One problem, a useful tool
The decision in focus
A title alone did not explain the work inside a coding session.
A larger session peek showed the beginning, ending and available analysis, with previous and next navigation.
Skimming became a meaningful step between the weekly overview and a full transcript.
web-v10.20.95 · Verified tag checkpoint; reviewed implementation
These are historical source milestones. A tag is often a deployment checkpoint; the version’s shape does not measure the importance of a feature. Repository work began before the first deployment tags.
An image result needed somewhere to live and a way to change one part of it.
Projects, scenes, panels, a gallery and mask-based revision formed the first working loop.
Organisation became part of making the image, setting up the later gallery redesign.
bcae6a588 · Reviewed commit and implementation
The application existed before its deployment tag stream.
Versioned web deployment checkpoints began, with follow-up patches to build and image metadata.
Repeatable builds made frequent, small corrections practical. This is a deployment marker, not the origin date.
web-v1.0.0 · Verified tag checkpoint; reviewed implementation
Separate gallery and browse screens split the same task across two places.
A unified gallery added a hierarchy tree and bulk assignment.
The same organised image could then become a reference in a conversation.
web-v3.0.0 · Verified tag checkpoint; reviewed implementation
An image and the conversation about it needed a direct handoff.
Gallery-to-chat integration connected the visual workspace to iterative chat.
Conversations became another way to work with assets, alongside generation and revision.
web-v4.13.0 · Verified tag checkpoint; reviewed implementation
Useful coding instructions and tools were accumulating around individual sessions.
Metaclaude began as a versioned configuration repository.
Skills and selective linking developed around the distinction between shared setup and machine state.
f9efabb8d · Reviewed commit and implementation
Creative work also produced audio and documents that needed context.
The gallery broadened into a multi-type asset surface.
The organising model could serve a longer workflow than image generation alone.
web-v6.0.0 · Verified tag checkpoint; reviewed implementation
A chat client needed to follow a tool-using agent through a long turn.
Claude Engine established a stable HTTP and streamed-event boundary.
Other clients and runtimes could integrate around an explicit conversation contract.
v1.0.0 · Verified tag checkpoint; reviewed implementation
Tool discovery depended on separately running capabilities.
A schema cache gave clients a reusable catalogue.
The bridge could grow while keeping discovery separate from individual server availability.
v1.0.0 · Verified tag checkpoint; reviewed implementation
Useful decisions and connections were scattered through conversations.
Knowledge graph tools exposed triples, events, decisions, beliefs and questions.
Reading the graph still required links back to the source; extraction and grounding became the next concern.
v1.4.0 · Verified tag checkpoint; reviewed implementation
The desktop wrapper added another maintained boundary to a web application.
PanelForge chose a web-only direction and removed the NativePHP/Electron layer.
Development could focus on the browser workspace and its mobile behaviour.
web-v7.0.0 · Verified tag checkpoint; reviewed implementation
Independent stdio tools needed a consistent service boundary.
All eleven bridge servers moved onto mcp-mux.
New resources could join the shared gateway without each client learning a new transport.
v3.0.0 · Verified tag checkpoint; reviewed implementation
Codex had a different upstream protocol from Claude.
The first tagged Codex Engine adapter used app-server JSON-RPC behind the common client envelope.
The next engine could join an established client pattern while keeping its own runtime integration.
v0.1.0 · Verified tag checkpoint; reviewed implementation
Switching engines should preserve a recognisable conversation surface.
OpenCode joined Claude and Codex through the shared streaming path and reusable profiles.
Parity made differences in recovery, permissions and runtime behaviour easier to address explicitly.
web-v7.91.0 · Verified tag checkpoint; reviewed implementation
A long mobile loading hang made the workspace hard to enter.
The release reduced conversation payloads and revised timeout and reload handling.
The practical success of a feature also depended on getting into it reliably.
web-v9.12.0 · Verified tag checkpoint; reviewed implementation
A spoken conversation could be interrupted while the agent was still working.
The Apple client added interruption recovery, standby, local commands and spoken questions.
Voice interaction needed deliberate turn state, not just speech playback.
ios-v1.4.0 · Verified tag checkpoint; reviewed implementation
Another coding runtime needed the portable workbench pattern.
Metacodex selectively linked portable files and generated configuration from local overlays.
Shared skills could travel while authentication, caches and sessions stayed machine-local.
86bae28b6 · Reviewed commit and implementation
Analysis could invent duplicate names or produce incomplete graph records.
A grounded agentic analysis loop required evidence lookup, validation and a terminal receipt.
Candidate resolution and later curation could build on an explicit evidence boundary.
260b1d37f · Reviewed commit and implementation
A growing project collection needed another level of organisation.
Workspaces became the protected top level, with migration and move support.
The same gallery hierarchy could now separate broader bodies of work.
web-v10.0.0 · Verified tag checkpoint; reviewed implementation
A graphic preview and its video export needed to agree.
Animated shader backgrounds joined Kitforge, using the same rendering function for preview and export.
A browser composition could become a still image or a looping clip.
v0.5.0 · Verified tag checkpoint; reviewed implementation
Useful work also lived outside a browser, on a drawing canvas.
Freeform joined the gateway after stateful InfinitySketch proxy work.
Native surfaces could participate through explicit resources and transport handling.
v5.10.0 · Verified tag checkpoint; reviewed implementation
Written model instructions needed an execution check.
A model-policy hook validated agent starts and shared retry guidance.
The portable workbench gained a testable boundary around how delegated work begins.
v1.0.0 · Verified tag checkpoint; reviewed implementation
A client connection could disappear while a tool-using turn continued.
An outbox and ordered recovery timeline retained the completed result for later collection.
Recovery could restore the work in order; server restart recovery remained a separate problem.
v6.13.0 · Verified tag checkpoint; reviewed implementation
A long silence could be healthy waiting rather than a dead runtime.
Bounded liveness probes replaced interruption based only on silence.
Recovery decisions could depend on the actual upstream state.
v0.6.23 · Verified tag checkpoint; reviewed implementation
A new instruction needed an explicit meaning while a turn was already running.
Queue and injection steering gave follow-ups deliberate handling.
Users could refine ongoing work with a defined control contract.
v6.15.0 · Verified tag checkpoint; reviewed implementation
A visible permission choice needed to constrain the runtime itself.
Native tool profiles were validated against the installed catalogue and enforced on resumed and forked sessions.
The client choice became an engine boundary with tests across session lifecycles.
v0.6.28 · Verified tag checkpoint; reviewed implementation
Imported coding transcripts were difficult to navigate as a growing collection.
Code History added full-page list, day and week views.
Showing more sessions exposed a new problem: making a crowded week understandable.
web-v10.20.80 · Verified tag checkpoint; reviewed implementation
A dense week view made the important sessions hard to pick out.
Daily activity bars, selected digest cards and expandable session strips gave the week a readable hierarchy.
The next interaction became deciding whether a session was worth opening.
web-v10.20.94 · Verified tag checkpoint; reviewed implementation
A title alone did not explain the work inside a coding session.
A larger session peek showed the beginning, ending and available analysis, with previous and next navigation.
Skimming became a meaningful step between the weekly overview and a full transcript.
web-v10.20.95 · Verified tag checkpoint; reviewed implementation
Opening a read-only coding session still constrained the actual reading surface.
The transcript gained the whole pane, following digest, preview and typed-message corrections.
A sequence of patch checkpoints improved the complete journey from overview to reading.
web-v10.20.97 · Verified tag checkpoint; reviewed implementation
No curated milestone matches these filters. The tag inventory may still contain matching checkpoints.
Go deeper
3,666 verified tags · 21 inspected repositories · snapshot 15 Oct 2026
The same filters apply here. This index contains tag names, dates, projects and short commit identifiers. Reviewed stories above explain selected changes; a tag alone does not.
Open this section with JavaScript enabled to browse the inventory.
| Date | Project | Tag | Marker | Commit |
|---|
Curated milestones combine verified Git references with reviewed implementation and archive rationale. Commit milestones establish source changes; they are not launch announcements or present availability claims.
Git tag creator date; lightweight tags use commit date. Calendar days retain the source offset. Earliest committer timestamp reachable from the inspected HEAD; not a product launch.
All 21 scoped repositories were refreshed from their origin remotes with git fetch --tags on 15 October 2026. The 3,666 inspected tags and their commit/date metadata matched the preceding inventory. Tags are ordered by date, with iOS and macOS version families kept distinct. An “other” tag includes a test marker outside the numeric version shapes.
Snapshot date: 2026-10-15. All 21 inspected repositories returned metadata after their origin tag references were refreshed.