Dostigus

Problem

Ready-made agents run on someone else's server, or on a laptop that has to stay awake. I wanted a different shape: my server, my database and my model keys. Bots run on schedules and talk with people in one chat, for a family or a small team.

What was built

A Nuxt host that starts with one docker compose command. It has a chat for people and bots, and bots have skills, schedules and files. The owner adds keys: OpenRouter, OpenAI or any compatible API. A bot can be exported as a Pack, a portable recipe, and applied on another host from a file, a zip URL or a git repository. The first finished Pack was Mailer, a mail bot over IMAP and SMTP. Between 21 September and 3 October 2026 the project got 48 ADRs and 159 commits, 147 of them co-authored with Cursor Agent. I set the tasks, made the decisions in ADRs and reviewed the results.

Key decisions

• MCP as the only data contract

  Bots and the UI reach the database through the same MCP tools. I rejected a separate REST API for the UI: two contracts drift apart over time.

• Model tiers instead of a model list

  The code knows only cheap, strong, code and toy, and the owner binds them to their providers. Switching provider changes no code, and after a failed call the host can escalate to a higher tier.

• Declarative modules before a sandbox

  I postponed running arbitrary user code: sandbox security would have taken all the time before the core worked.

• A turn journal without content

  Each bot turn records model, tokens and call count, but not message text or prompts. Failures can be debugged without screenshots and without reading conversations.

Stack

• Nuxt 4
• Vue
• Reka UI
• TypeScript
• SQLite and Drizzle ORM
• @nuxtjs/mcp-toolkit
• Docker
• image on GHCR

Status and next

Development is paused; the last commit is from 3 October 2026. The code is open under MIT.

Links

• Source