CremindUsing Cremind
The four ways to reach your Cremind agent — the web UI, the desktop app, the cremind CLI, and chat channels — and when to use each.
Cremind runs as one agent behind several surfaces. Whichever one you open, you are talking to the same profile, the same conversations, and the same tool plane on the server — so you can start a thread in the browser, pick it up in the terminal, and get notified on a chat channel without anything falling out of sync.
This section covers the day-to-day surfaces. Pick the one that fits the moment.
Web UI
The browser dashboard at port 1515: conversations, settings, tools, processes, and skill events.
cremind CLI
A streamed chat REPL plus full admin over profiles, conversations, tools, agents, and config.
Chat channels
Reach the agent from an external messaging platform such as Telegram.
Documents
Drop Markdown files into a watched folder and let the agent retrieve them.
The four surfaces
Web UI
The web UI is the primary dashboard. After install, your browser opens to the Setup Wizard at http://<host>:1515/#/setup; once a profile exists, the same address serves the full app — conversations with streamed agent output, the Settings pages (LLM providers, per-profile config, channels), the Tools and Agents views, the Processes list, and the Skill Events page.
The web UI listens on port 1515 by default.
Desktop app (Cremind App)
The Cremind App is a desktop client for Windows, macOS, and Linux. It bundles the agent, so there is no separate server to install — download the installer for your OS from the Releases page, and it auto-updates from GitHub Releases.
| OS | Installer |
|---|---|
| Windows | Cremind App-Windows-<version>-Setup.exe |
| macOS | Cremind App-macOS-<version>.dmg |
| Linux | Cremind App-Linux-<version>.AppImage |
cremind CLI
The cremind command-line tool is the terminal-side counterpart to the web UI. cremind chat opens a streamed full-screen REPL against a conversation; the rest of the command groups cover conversations, tools, agents, LLM configuration, processes, profiles, channels, file watchers, skill events, and first-run setup. Almost every command mirrors a control in the web UI, and a global --json flag makes the whole CLI scriptable.
See the CLI overview for the full command table and the CREMIND_TOKEN / CREMIND_SERVER environment variables.
Chat channels
Channels let people on an external messaging platform talk to your agent. Telegram bot and userbot adapters ship with Cremind, and there is a channel API for adding more. Inbound messages create conversations linked back to the channel, so they show up in the web UI's sidebar alongside everything else.
See Chat channels for what is supported today.
One agent, many doors
Every surface authenticates as a profile and talks to the same server, so conversations and settings are shared across all of them. The CLI and the web UI in particular are designed to be used interchangeably.
A typical session
- Finish first-run setup in the web UI (or headlessly with
cremind setup). - Chat in the browser, or run
cremind chatfor a terminal REPL against the same profile. - Drop reference material into a watched documents folder so the agent can retrieve it.
- Optionally connect a chat channel so the agent reaches you where you already are.