Send a UI change to your coding agent
Use Superset Design Mode to select an element in your preview and send its element context to your coding agent.

Einblicke vom Superset-Team zu parallelen Coding-Agenten und Entwicklerproduktivität.
Use Superset Design Mode to select an element in your preview and send its element context to your coding agent.

Select lines in a pull request diff and send feedback to an agent in Superset, then review its changes beside the PR checks.

Publish an agent-created design or report as a Superset Page, pin feedback to the relevant element, and review the next version at the same link.

A practical Claude Code and Codex workflow: scope three tasks, isolate them in Git worktrees, handle a blocked agent, and test the combined result before merging.

Set up a recurring Superset agent check on a connected host, inspect its workspace, and handle offline runs. Includes a bounded maintenance prompt and review checklist.

We'll be updating our name later this month. Nothing will change besides the name.

See how your agent usage stacks up. Then challenge a friend.

Connect an iPhone to your Superset workspaces, unblock Claude Code or Codex, and inspect changes. Includes Pro requirements, host setup, and offline troubleshooting.

Prompt coding agents, follow terminal sessions, and review changes from your iPhone. Pick up the Superset workspaces you already use on your computer.

Keep useful context when a coding agent gets stuck. Learn when to resume, fork a session, or hand a summary to another agent.

Our prediction for when the software factory actually arrives, the four tiers on the way there, and the first production run, starting in September.

Give coding agents separate workspaces, keep track of blocked tasks, and review changes while other agents keep working.

Create separate workspaces for coding agents, review their diffs, and merge changes. Learn what Git worktrees isolate and which resources remain shared.

An attempt to crystallize our plans for 2026

I ran out of technical content to write for the blog so here is something I am interested in instead.

Git worktrees have been around since 2015. For most of that time, they were a curiosity. Now they're having a moment. This is the story of how they came to be and why they suddenly matter.

How we built a process-isolated terminal host that survives app restarts, handles backpressure gracefully, and enables cold restore from disk.
