Choose tools by the job, not the presenter’s stack

Compare the capability you need, preserve uncertain product claims, and substitute tools without changing the operating pattern.

Compare the capability you need, preserve uncertain product claims, and substitute tools without changing the operating pattern.

TL;DR

  • 16 tool categories from the workshop, each with what John uses and 81 vetted alternatives in evidence tables (stars · last push · license).

  • The one move: adopt the pattern, not the exact tool — every section names the substitute that keeps the pattern alive under your constraints.

Have your agent match these to your constraints — paste this into it:

Fetch https://dewy-sleet-n5zs.here.now/agent.md?raw — a machine-readable list of every tool category in this workshop with vetted alternatives (name + URL + evidence). Ask me for my constraints (OS, license policy, budget, what I'm allowed to install), then recommend one alternative per category I can't adopt as-is, with your reasoning.

How to read this page

This workshop demos John's exact stack. You don't need John's exact stack. Every pattern taught here — tiny wrappers, preloaded context, agent-driven browsers, taste voting — works with substitutes. Below: every tool the workshop mentions, what it does in John's system, and credible open-source or commercial alternatives with evidence.

Retrieved the recorded snapshot. Star counts, last-push dates, and licenses come from the GitHub API on that date (gh api repos/<owner>/<repo>); non-GitHub products were sanity-checked by web search the same day. "NOASSERTION" means GitHub couldn't map the repo's license to an SPDX id (usually a custom or source-available license) — read the repo's LICENSE before adopting. Nothing here is an endorsement, and a few of John's tools are personal/unreleased — those are flagged, not glossed over (see the appendix).

Also mentioned in the workshop

These came up but don't need an alternatives table:

  • pi-session-id — the section 01 pi extension (MIT). The pattern (per-command shell prefix + session-scoped overrides) ports to any agent with shell hooks.
  • Zed / Finder / GitHub open-cwd targets (section 06) — editor-of-choice slots; any open/code-style CLI works.
  • Linear CLI (sections 01/05) — an example policy-wrapped command; substitute your tracker's CLI.
  • Tailscale (section 08) — how the Mac mini oracle server is reached; any WireGuard-style mesh works.
  • wrangler / inspiration-board (section 07) — covered under Publishing above.

Appendix

What we could NOT verify (flagged, not fabricated)

  • cs — no public repo found; treated as personal/unreleased, with the honest substitutes listed in §10.
  • packx — verified as John's npm package via web search (npm install -g packx), but it has no public GitHub repo we could find; star/license evidence unavailable.
  • Oracle's exact consult architecture — the fork repo exists (johnlindquist/oracle) but is empty of description/stars; capabilities described here come from the workshop's own docs.
  • Grok Build star data — proprietary, no public repo; existence verified via x.ai announcement coverage.
  • License nuances behind every "NOASSERTION" — read the repo's LICENSE before commercial adoption (notably Crush, OpenHands, herdr, Sentry, OpenReplay, Infisical, Bitwarden).

Source references