THE CHELUS GUIDE
Make it your own.
Start with a conversation. Add the pieces that make Chelus useful to you.
Choose your next step
Telegram
Set up your private bot, keep conversations separate, and understand the bridge.
02 / KEEP THE CONTEXTMemory & skills
Remember useful facts and save procedures you can inspect, revise, and undo.
03 / WRITE IT DOWNNotes
A folder of linked Markdown notes the agent searches, files into and keeps tidy.
04 / DO THE WORKTools & approvals
Search, edit, fetch, and run commands with an explicit approval boundary.
05 / COME BACK TO ITScheduled jobs
Run prompts or scripts on a schedule while the Telegram bridge is running.
What runs where
The agent loop, tools, local history, memory, skills, and Telegram bridge run on your device. Chelus sends context to DeepSeek, or the provider you configure, for remote model inference. Local storage does not mean your prompts stay on the phone.
Additional command-line tools and services can extend the agent. They keep their own requirements: Chelus’s dependency-free Python core does not make an external integration dependency-free.
A few terminal essentials
chelus # resume the latest conversation
chelus chat --new # start fresh
chelus sessions # list conversations
chelus show 3 # inspect a conversation
chelus usage # token and cache-hit totals
chelus notes # recent notes and broken linksIn chat, /help lists available commands. /quit ends the terminal chat, and Ctrl-C cancels a reply. A new conversation resets conversation-scoped ordinary tool approvals.
For the curious
Read the reference for commands, configuration defaults, file locations, and limits. The project status distinguishes automated coverage from live device verification.