Web Server
openclacky server starts an embedded HTTP + WebSocket server with a full browser-based UI. It's designed for running multiple persistent agent sessions simultaneously.
Starting the Server
openclacky server
Opens at http://127.0.0.1:7070 by default. Navigate there in your browser.
Options
| Flag | Default | Description |
|---|---|---|
--host |
127.0.0.1 |
Bind address |
--port |
7070 |
Listen port |
# Custom host/port
openclacky server --host 0.0.0.0 --port 8080
Features
Multi-Session
Create multiple named sessions — each runs an independent agent in its own working directory. Switch between them in the left sidebar.
Sessions persist across server restarts: the most recent 5 sessions for each working directory are automatically restored on startup.
Session Status
Each session shows its current state:
- Idle — waiting for input
- Running — agent is working
- Error — last task failed
Scheduled Tasks
The server includes a built-in scheduler. Tasks defined via the cron-task-creator skill run automatically on schedule, without any terminal session needed.
Create and manage tasks directly from the Web UI:
- View all scheduled tasks and their cron expressions
- Enable / disable individual tasks
- Trigger a task manually (run now)
- View run history and output
IM Channel Integration
Once configured via channel-setup, the server manages IM channel adapters (Feishu, WeCom) as background threads. The agent receives and replies to messages from those channels through the server.
Skill Management
The Web UI shows all installed skills (built-in + user-installed) and lets you enable/disable individual skills without editing files.
Permission Mode
The server always runs in confirm_all mode: file operations and shell commands are auto-approved, but tasks requiring explicit human action pause and wait. This is appropriate for a server that may run unattended.
Onboarding Flow
If no API key is configured when the server starts, it shows an onboarding flow in the browser:
- Key Setup — enter your API key and test the connection
- Soul Setup — personalize the agent (optional, can be skipped)
Once onboarded, the configuration is saved to ~/.clacky/config.yml and the server starts normally on subsequent runs.
PID File
The server writes a PID file to $TMPDIR/clacky-server-<port>.pid. On startup, if a previous server on the same port is still running, it's automatically terminated before the new one starts.