First Run¶
After completing Installation and starting the stack, here's what to expect.
What Happens on First Boot¶
- Database migrations — creates all tables (settings, workflows, resources, knowledge, memory, etc.)
- Config seeding — environment variables are written to the
settingstable - Default LLM providers — Gemini, Claude, Ollama, and LM Studio providers are created (disabled if no API key set)
- Default workflows — example workflows are seeded (Tech News Digest, Web Research, etc.)
- Default RSS feeds — a set of news and tech feeds are created as resources
- Self-awareness indexing — architecture docs are chunked and stored in the knowledge base
Access the Admin UI¶
Open http://localhost:5001 in your browser and log in with the ADMIN_PASSWORD you set in .env.
The dashboard shows:
- Active workflows and recent runs
- LLM provider status and usage
- Skill registry (core + dynamic)
- System health
Test Telegram¶
Send /ping to your bot — you should receive pong back.
Try a few more commands:
/status → System stats (uptime, memory, skills)
/skills → List all registered skills
/workflows → List workflows with status
/help → Full command reference
Run Your First Workflow¶
- Go to Admin > Workflows
- Find "Tech News Digest" and click Run Now
- Watch the execution progress in real-time
- The result is delivered to your Telegram chat
Or trigger it from Telegram:
Try a Search¶
This invokes the web_search skill — searches DuckDuckGo, fetches top results, and synthesizes an answer via your configured LLM.
Configure MCP (Optional)¶
If you want to connect AI clients (Claude Code, Cursor):
- Go to Admin > Config
- Set
mcp.api_keyto a strong random value (category:mcp, sensitive:true) - Configure your client — see MCP Client Setup
Next Steps¶
- Configuration — fine-tune settings via the Admin UI
- Built-in Skills — explore all available skills
- Writing Custom Skills — create your own
- MCP Server — connect AI clients