Dashboard
A walkthrough of the dashboard pages, how Settings is grouped, how sign-in works, and how to watch the bot while it works.
What the dashboard is for
The dashboard is the main way you talk to GolemCore and the main way you watch what it is doing. Every feature has a page of its own; if the bot did something, there is a place in the dashboard where you can go look at it.
On the very first boot, before you have added any LLM provider, the dashboard shows an onboarding screen instead of the normal layout. As soon as you finish onboarding, the full dashboard appears.
The pages you will use
- Chat — where you actually talk to the bot. Replies stream live; tool calls and progress show up inline as the bot works.
- Settings — every dial, toggle, and key. Organized into a small catalog so related concerns sit together.
- Scheduler — anything that runs on a schedule: Auto Mode goals, recurring tasks, cron triggers.
- Sessions — the history of every past conversation, with the full record of what the bot did each turn.
- Logs — live runtime output. The first place to look when something is wrong right now.
- Skills — the list of skills installed on this bot, plus the marketplace for adding new ones.
- Webhooks — incoming HTTP triggers from other systems (CI, alerts, GitHub).
- Diagnostics — health checks for the bot, its providers, and its connected services.
How Settings is laid out
Settings is the largest surface, so it is split into themed sections instead of one giant list. You will spend most of your configuration time in the first two groups.
Runtime controls
General, LLM Providers, Model Catalog, Model Router. The core dials every other feature depends on.
Core
Plugins
Plugin Marketplace and one settings page for each plugin you install. Each plugin owns its own corner.
Extensions
Runtime and tools
Filesystem, Shell, Automation, Voice, Skills, Memory, MCP, Usage, Updates. Per-feature configuration.
Features
Operator safeguards
Rate limits, Security, Compaction, Diagnostics, SelfEvolving controls. The advanced and safety-related knobs.
Advanced
Signing in
Sign-in is intentionally simple. There is one account, called admin. The first time the bot starts, it generates a temporary password and prints it to the log; you read it once and then change it.
A few rules to know
- The username is always
admin— there are no multi-user accounts. - The first password from the log is temporary. Open Settings → Security and rotate it before you put the bot somewhere reachable.
- You can pre-set the password at container start with the
BOT_DASHBOARD_ADMIN_PASSWORDenvironment variable, which skips the temporary-password step.
Watching the bot work
Chat is built on a live websocket, so you see the bot work as it works: which model started, when a tool was called, when a retry happened, and when the turn finished. You do not need to refresh.
When something looks off in Chat, the same information lives in three places afterwards: Sessions for the historical detail, Logs for the live runtime output, and Diagnostics for the health checks. Whatever Chat could not show clearly, one of those three pages can.
What to do next
Related pages