
Security News
CVE Volume Surges Past 48,000 in 2025 as WordPress Plugin Ecosystem Drives Growth
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.
tambo-cli-test
Advanced tools
The Official CLI for tambo ui.
⚠️ Note: This project is currently in active development. APIs and features may change.
npx tambo full-send
This command will:
While you can install globally, we recommend using npx to ensure you're always using the latest version:
# Using npx (recommended)
npx tambo <command>
initInitialize Tambo in your Next.js project. Two modes available:
# Full setup - recommended for new projects
npx tambo full-send
# Basic setup - just API key configuration
npx tambo init
add <component-name>Add a Tambo component to your project:
# Basic usage
npx tambo add message
# With legacy peer dependencies flag
npx tambo add message --legacy-peer-deps
update <component-name>Update an existing Tambo component in your project:
# Basic usage
npx tambo update message
# With legacy peer dependencies flag
npx tambo update message --legacy-peer-deps
Available components:
message-thread-full - Full-screen chat interface with history and typing indicatorsmessage-thread-panel - Split-view chat with integrated workspacemessage-thread-collapsible - Collapsible chat for sidebarsthread-content - Message thread with grouping and timestampsthread-history - Chat history managementmessage-input - Rich text inputmessage - Individual message display with content formattingmessage-suggestions - AI-powered message suggestionscontrol-bar - Spotlight-style command palettethread-list - Organized chat thread navigationform - Dynamic form with validationinput-fields - Text inputsgraph - Interactive charts (line, bar, scatter, pie)When you add components, they'll be installed in your project following this structure:
your-next-app/
├── src/
│ ├── components/
│ │ └── ui/
│ │ ├── message-thread-full.tsx
│ │ └── ...
│ └── app/
│ └── layout.tsx # Add TamboProvider here
└── .env.local # Your API key configuration
The CLI will automatically create/update your .env.local file with:
NEXT_PUBLIC_TAMBO_API_KEY=your-api-key
After initialization, add the TamboProvider to your app/layout.tsx:
"use client";
import { TamboProvider } from "@tambo-ai/react";
export default function RootLayout({ children }) {
return (
<TamboProvider apiKey={process.env.NEXT_PUBLIC_TAMBO_API_KEY ?? ""}>
{children}
</TamboProvider>
);
}
Note: The
"use client"directive is required because TamboProvider manages client-side state for features like thread management, message history, and component state.
For detailed documentation and examples, visit tambo.co/docs
This CLI is currently in active development. While core features are stable, you might encounter:
See demos of the components in action:
--> here <--
MIT License - see the LICENSE file for details.
We're building tools for the future of user interfaces. Your contributions matter.
Star this repo to support our work.
Join our Discord to connect with other developers.
Built by developers, for developers.
Because we believe the future of UI is generative and hyper-personalized.
FAQs
Tambo command-line tool
The npm package tambo-cli-test receives a total of 0 weekly downloads. As such, tambo-cli-test popularity was classified as not popular.
We found that tambo-cli-test demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.

Security News
Socket CEO Feross Aboukhadijeh joins Insecure Agents to discuss CVE remediation and why supply chain attacks require a different security approach.

Security News
Tailwind Labs laid off 75% of its engineering team after revenue dropped 80%, as LLMs redirect traffic away from documentation where developers discover paid products.