01 / Input
Speak the rough idea
Typeless keeps the capture layer fast, so product direction starts messy and gets refined in motion.
SigStack 5.0 / Focus
sigstack5.0
A Codex-first stack for shipping real apps with fewer moving parts.
Codex is the center. OpenAI models do the day-to-day coding loop inside it. Typeless handles fast input, Supabase holds product state, Vercel ships the result, and Claude stays as the backup brain.
4
Core tools
1
Backup AI
5.0
Version
Current default
The stack got smaller on purpose.
SigStack 5.0 is no longer a catalog of every tool that ever helped. It is the short list that actually drives the work right now.
Backup, not the center
Claude stays in the workflow.
I would not remove Claude from the story completely. It should be framed as the second-opinion layer, not the primary coding environment.
The new story is a simple loop.
Fewer moving parts makes the site feel more honest: capture intent, build in Codex, persist in Supabase, ship on Vercel.
02 / Build
Code inside Codex
Codex is the cockpit for repo edits, tests, previews, and the OpenAI model loop that does the actual implementation work.
03 / Persist
Store product state in Supabase
Auth, data, storage, and operational truth live in one boring, inspectable backend instead of scattered glue.
04 / Ship
Push the result through Vercel
Preview, production, analytics, and rollback stay close to the code path so the stack keeps shipping momentum.
What to take away
Most of the old page was true, but no longer useful.
Remove the old plugin/MCP count flex. It made the site feel like a tool museum instead of a current workflow.
Remove the machine-fleet diagram as the headline. It can exist in private ops docs, but it is not the product story anymore.
Remove newsletter/support clutter from the main page. The 5.0 page should sell clarity, not every adjacent surface.
Remove old quick-start symlink instructions. The public promise is the working stack, not repo plumbing.
Keep, but demote
A few rails still belong under the floorboards.
These are still part of how good work happens, but they should not be the hero message of the public site.
GitHub stays as plumbing
Source control, PRs, and durable handoffs still matter; they just do not need to compete with the primary stack.
Repo docs beat public complexity
Operational details belong in AGENTS.md, handoffs, and private docs instead of a landing page full of internals.
Visual QA remains non-negotiable
Previews, screenshots, and real browser checks stay in the workflow because polish needs evidence.