CLI, add-ons, and Builder

TanStackCLI

alpha

Turn TanStack knowledge into project changes.

CLI brings together project commands, docs search, modular integrations, and the Builder so TanStack Start apps can be scaffolded and customized with current TanStack context.

Total DownloadsWeekly DownloadsGitHub Stars

CLI

project commands and generated changes

Docs

search, fetch, and introspect

Builder

visual stack selection and export

tanstack cli

npx @tanstack/cli create --list-add-ons --json
npx @tanstack/cli search-docs "router loaders" --library router
npx @tanstack/cli doc query framework/react/overview --json

Why CLI

Project setup is where documentation meets the filesystem.

The hard part is not printing a template. It is choosing the right TanStack libraries, wiring partner integrations, following current docs, and leaving the user with a project they can understand.

A CLI that knows TanStack instead of guessing.

Commands can start from TanStack docs, packages, examples, and integration metadata rather than generic project templates.

CLI introspection turns docs into agent context.

Use JSON commands for docs, libraries, add-ons, and ecosystem data so generated work can reference current TanStack conventions.

Integrations become selectable building blocks.

Auth, databases, styling, deployment, and more can be composed into a Start-ready app without burying every choice in hand-written setup.

The Builder makes the stack visible.

Use the web UI to select libraries and partners, preview generated choices, and export a plan the CLI or agent can execute.

1

Discover

Search docs, examples, packages, and integrations through direct CLI commands.

2

Choose

Select libraries, partners, deployment targets, and app shape.

3

Generate

Create or modify files with TanStack-specific conventions in mind.

4

Review

Inspect the generated plan and project changes before shipping.

Project workflow

Discover, choose, generate, review.

CLI should help a team move from product intent to project files without hiding the important decisions behind a magic template.

Builder output

Make the stack visible before files change.

The Builder turns app intent into a readable stack brief: TanStack libraries, partner integrations, deployment target, generated files, and CLI-ready configuration.

libraries

Start, Router, Query, Form

partners

Cloudflare, Clerk, Drizzle

files

routes, server fns, env, deploy config

CLI config

.tanstack.json and chosen add-ons

The output is not just a template. It is a stack decision record that an agent, CLI command, or developer can follow.

Developer ergonomics

Generated code should still feel authored.

CLI is strongest when it gives teams inspectable changes, traceable docs context, and a clear path back to the choices that produced the project.

Open source ecosystem

CLI connects the docs, packages, partners, and people.

Maintainers, integrations, examples, partners, and GitHub sponsors keep the project workflow grounded in real TanStack usage.

GitHub Sponsors

Wow, you've come a long way!
Only one thing left to do...