How to get help

Four ways, in the order worth trying them: the first three answer immediately, the fourth is us, within one business day.

1. Help with the installation

If Orakul isn't on your server yet, or the install stopped partway, everything about it lives on the installation page: what to prepare in advance, the six wizard screens with screenshots, and the form for sending us the log.

A failed install almost never has to be started over. Most steps have usually completed by then, and it can be resumed from where it stopped. Copy the log with the "Copy log" button and send it through the form on that page — we work out what happened and tell you what to do next. It's part of the deployment and costs nothing extra.

2. Ask Orakul Help inside your own panel

Every installation ships with the Orakul Help agent (@help). Pick it from the agent list under "Agent Chat" and ask in plain words. It knows your panel and answers about it, rather than in generalities collected from the internet.

What it covers:

  • Installation and setup — preparing the server, first-run configuration, updating the platform, database backups.
  • Keys and integrations — where to obtain GEMINI_API, TG_API, OPENAI_API, ANTHROPIC_API, PAGESPEED_API_KEY, and where to paste them under "API Keys".
  • Building agents — "Subagents → Hire a specialist": role key, model, temperature, system prompt; attaching knowledge base documents and tools; switching on background execution.
  • Access control — the users allowlist, Telegram permissions, one-time passwords, the "Junior" flag and agent groups.
  • Scheduling — recurring CRON tasks and one-off runs: Telegram messages, generated PDF reports.
Ask "What can you do?" and the agent answers with a map of the system

3. Automating your own process — start from the blog

Chances are a similar process is already written up. The blog carries finished agent configurations: a copywriter, an SEO specialist, a technical-audit router, proposal preparation, an account manager.

These aren't inspirational stories — they're the configuration: the full system prompt, the numbered workflow steps, the tool on each step, what belongs in the knowledge base, and where people trip. Your own process is almost always assembled from the nearest write-up: the step instructions and the knowledge base change, the structure stays. There's no need to start from a blank page.

All agent write-ups →

4. None of the above — write to us

Describe the task or the problem in your own words: what you were trying to do and what happens instead. We reply by email within one business day. If a chat is easier, message us on Telegram.