The Console
The Pikku Console is a per-environment visual control plane for your application. Run npx pikku dev and open http://localhost:3000/console — it gives you a complete overview of your functions, wirings, agents, workflows, and configuration, all derived from the compile-time registry generated by the Pikku CLI.
The Console is currently in alpha. Features and APIs may change between releases.
Why a Console?
As your Pikku application grows, it becomes harder to keep track of everything: which functions exist, how they're wired, what permissions they require, and what secrets they depend on. The Console makes all of this visible and interactive.
Key capabilities:
- Explore — Browse functions, workflows, agents, HTTP routes, channels, MCP tools, CLI commands, gateways, and more in a structured tree view
- Manage — View and edit secrets and variables per environment, configure auth providers, manage users and per-user credentials, and connect OAuth2 integrations
- Test — Run workflows and end-to-end scenarios (persona-driven, over real HTTP) with live progress, chat with agents in a built-in playground, and run the security audit
- Visualize — See workflow graphs, your database schema, and registry diffs rendered as interactive diagrams
Architecture
The Console is served by your own server at /console and uses the same authentication and permissions as your application. Its data comes from the compile-time registry the CLI generates into .pikku/, so it always reflects the current state of your codebase. Each environment (development, staging, production) serves its own Console with environment-specific configuration.
Next Steps
- Getting Started — Launch the Console for your project
- Features — Explore everything the Console can do