Identical prompts produce different runs. Smashq supervises parallel sessions of Claude Code, Codex and Grok Build with visible state, direct intervention, and a complete record. Understand the Harness that shapes every run, and optimize the flow around it.
Pick a folder or take one of your favorites. Choose the CLI on the tabs Claude, Codex or Grok, assign a workspace, then press Start. Below the box the list Recent resumes an earlier session in the same folder. The favorites in the sidebar are the second way: a right click offers Start with and the accent color of the project.
Home screen · Start box · Claude, Codex, GrokThe real Claude welcome TUI attaches in the main pane. Layout stays single. The session appears in the list on the left.
Claude Code · singleStart Codex from another favorite. Layout still single: the new session fills the main pane. Claude stays in the list. Two real shells, still one pane at a time.
Codex · activeSessionIdThe layout switch leaves single mode. Both sessions then share the window: Claude and Codex, top and bottom. Same shells, same list, both visible at once.
Grid view · 2 sessionsThe grid takes whatever you start. Four more sessions across three projects, and the list on the left grows with them. Every cell is a real shell; the grid badge on each session row shows which one is where.
Grid view · 6 sessionsGitHub notifications while the fleet keeps running: reviews, mentions, assignments. The bell stays in the dock so the outside world does not pull you out of the terminals.
GitHub notifications · dockIn ask mode the agent stops before it acts, and you answer in the terminal it stopped in. A Claude session that exits with an error restarts on one click in the same folder and continues the same conversation. Close the app and the sessions come back.
Ask mode · "Restart session"The Harness floats above the main window. Pick a CLI, then read the Global scope under ~/.claude/ and every project below it. Skills, agents, hooks, MCP servers, rules, knowledge, configuration and memory: the same surfaces the CLIs load.
Harness · Claude, Codex, GrokA knowledge row names the file, its first line and its category. One click opens the detail modal above the list: file, type, then the full Markdown body. You inspect the same text the agent will load, without leaving the Harness.
Knowledge · detail modalCLAUDE.md sits in Configuration and unfolds as a plain text block. The memory files sit below it, edit and delete at hand. The context that steers every run stays visible and under your hand.
Configuration · MemoryOne workspace for everything the sessions changed. The file list carries the review progress, the diff marks words rather than lines, and the overview bar on the right shows where the changes sit before you scroll. Notes attach to the line they belong to.
Mark the lines that need work and collect them as change requests. Smashq composes one prompt from all of them, carrying the code along so the agent finds the place again. Send it into the running session, or start a new one with it.
Six pillars for orientation, fourteen areas with three highlights each, and the complete community catalog under the fold. Everything here ships in the current download. What needs a Pro key carries the Pro label.
Several real shell sessions at once. Claude Code, Codex and Grok Build side by side, grid or single view, scrollback kept when you switch.
Favorites, project colors, and the config panel: CLAUDE.md, skills, hooks, GitHub, worktrees, history.
Review-Center for diffs, notes, and change requests. Part of the current download.
Kanban on GitHub Projects, notifications in the app, tasks with dates, notes global and per project.
Harness for skills and agents, markdown editor with preview, paths opened from the terminal.
Logs, diagnostics, settings, local persistence, and signed updates from smashq.de.
Open a group to see every community capability in that area. Pro features carry the Pro label; everything else is free forever under the promise below.
Smashq follows one rule, written into its architecture document: every feature that shipped in the free version stays there, permanently. Pro only adds on top: the Review-Center and GitHub notifications arrived as Pro features and replaced nothing that was free. Signed updates reach every install through the same endpoint, and that channel is never tied to a tier.
Nothing above moves. Paid tiers only ever add, and the update channel stays open on every tier, because that is the path a bug fix travels.
For everyone who runs agents on their own machine.
No account, no card, no expiry.
This tier includes:
For daily use, when the review loop starts to pay for itself.
Monthly or yearly. Cancel any time.
Everything in Free, plus:
Pro only ever adds. Nothing that Free holds moves behind it.
For teams that configure and roll out Smashq centrally.
Invoice billing. A reply within one working day.
Everything in Pro, plus (in development):
All prices include value added tax. Checkout links open payment pages hosted by Stripe. This site never handles card details.
Every artifact is signed with minisign and served from this domain. The integrated updater queries the same endpoint the download table reads. No third party is part of the trust chain.
| Artifact | Platform | Version |
|---|---|---|
| Loading releases… | ||
Each artifact is signed with minisign. The updater endpoint is smashq.de/releases/latest.json. No third party is part of the trust chain.
One download. Signed updates from the first party. The record starts with the first session.
Smashq is early and shipping. If you want to help build the product, shape how it looks, or bring it to the people who need it, write to us.
Contact: support@smashq.de