Common Workflows
This guide covers the most common workflows you'll use with the Tambo CLI, organized by scenario and use case.
Getting Started Workflows
New Project Setup
For brand new projects, use the template approach:
Adding to Existing Project
For existing React/Next.js projects:
API Key Required
After running init
or full-send
, make sure to add your API key to
.env.local
: NEXT_PUBLIC_TAMBO_API_KEY=your_api_key_here
Component Management Workflows
Adding Components Strategically
Start with core components, then add specialized ones:
Checking What's Installed
Development Workflows
Building a Chat Interface
Building a Form Experience
Building a Data Visualization App
Maintenance Workflows
Keeping Everything Updated
Migrating from Legacy Structure
If you installed Tambo components before the directory structure change (more info here):
Troubleshooting Workflows
Dependency Conflicts
If you encounter peer dependency issues:
Component Not Working
Clean Reinstall
Quick Reference
Most Common Commands
Flags You'll Use Often
For detailed information about all available flags and options, see the Global Options page.
Quick reference:
--yes
- Skip confirmation prompts--legacy-peer-deps
- Fix dependency conflicts--prefix=<path>
- Custom component directory--dry-run
- Preview changes before applying