Getting Started

Wiki

Getting Started

This guide takes you from a fresh install to your first productive DMJBot session.

1. Install and open DMJBot

Run DMJBot with Docker and open it in your browser. The full options are in the Installation Guide:

docker run -d -p 8080:80 -v "data-data:/data" dmjbot/dmjbot:latest

Then open http://localhost:8080 (or http://<your-server-ip>:8080 on a remote server).

2. First-run setup

The first time you open DMJBot, a short setup wizard asks for:

  1. Your display name and the assistant's name (optional).
  2. A model provider — OpenAI, Anthropic, Google, or Ollama.
  3. Provider credentials and which model to use.
  4. Memory mode.
  5. An admin login and password.

When setup finishes, sign in and you land in the chat workspace.

3. Your first chat

  1. Start a new chat.
  2. Send a simple message such as "Summarize what you can do in 5 bullets."
  3. Open Settings and confirm your model/provider is connected.
  4. (Optional) Upload a small file and ask the bot to summarize it.
  5. (Optional) Add a tool in Settings → Tools to let the bot take real actions.

4. Where things are

  • Chat — your main workspace, with a panel on the right showing assignments and running tasks.
  • Settings — identity, models, usage limits, tools, memory, devices, skills, quick buttons, and authentication.
  • Left-menu pages for Assignments, Tasks, Devices, and more.

Next steps

Once you're chatting, these are the things that make DMJBot powerful:

  • Tools and MCP — connect integrations (email, Slack, storage, and more) so the bot can do real work.
  • Devices — connect your laptop, desktop, or a server to run tools and agents on them.
  • Files and Attachments — share files with the bot and get files back.
  • Assignments — have the bot run work on a schedule or when an event happens.
  • Managing other AI Agents — let DMJBot drive Claude Code, Copilot, and similar agents.
  • Core Features — an overview of what the platform does.
  • Troubleshooting — if something isn't working.

Tip

If you use SQLite, keep your /data volume backed up — it holds your sessions, settings, and files.