Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.eluu.ai/llms.txt

Use this file to discover all available pages before exploring further.

Five concepts make up most of Eluu. Once you have these, the rest of the product makes sense.

​
Colleague — the thing that does the work

A colleague is the central entity. It has a name, a role, a personality, a set of abilities, and a private workspace. You build colleagues. You don’t build prompts. A team typically has three to five colleagues, each focused on a different job: a sales colleague, a customer success colleague, an engineering on-call colleague. Each colleague has its own:
  • Workspace (a Git-backed file system that persists across every session).
  • Memory (a CLAUDE.md instruction file you maintain).
  • Tool permissions (Auto, Review, Block per tool).
  • Skills (packaged workflows it can invoke).
  • Integrations (which tools it can call, scoped per user).

​
Session — one conversation

A session is a single continuous conversation with a colleague. You can have many sessions open at once, each in its own tab. Sessions are persistent — close the tab and reopen weeks later, the history is there. In API responses you’ll occasionally see “task” — that’s the same thing.

​
View — a live dashboard

When the answer to your question is more than a paragraph, your colleague will build a view — a live dashboard with KPIs, charts, tables, and action buttons. Views update as your colleague gathers more data and can stay live forever. Views come in two flavours:
  • Inline — embedded directly in the chat. Good for one-off summaries.
  • Persistent — saved at /t/{team}/views/... so you can return to it. Good for things you’ll re-open.
Your colleague generates views. There’s no manual editor — you ask, the colleague builds.

​
Job — recurring work

A job is a colleague task that runs on a schedule. Jobs run on intervals (every 30 minutes), on cron expressions (weekdays at 9am NYC time), or once at a future time. Each run becomes a session, complete with full history. So you can scroll through last Monday’s morning briefing the same way you’d scroll through any chat. The API and the database call jobs “reminders”. The product UI calls them jobs.

​
Hard Drive — your team’s files

Everything your colleagues produce — reports, charts, code, data, images — lands in the Hard Drive, organised by which colleague made it. Files are versioned automatically. Click any file to open it in a panel-tab viewer that handles markdown, code, PDFs, Office docs, spreadsheets, images, and more. From a file you can re-open the chat that produced it.

​
How they fit together

You write a message
         ↓
A colleague reads its memory, picks tools, executes
         ↓
The conversation lives as a session
         ↓
Side effects:
  • files land in the Hard Drive
  • dashboards land as views
  • if scheduled, the whole thing repeats as a job
Everything cross-references. A view links to the session that built it. A file links to the session that wrote it. A job’s history is a list of sessions.

​
Two surfaces, same colleague

Every colleague is reachable from two places:
  • The web app at app.eluu.ai — chat, views, files, settings.
  • Slack — @mention your colleague in any channel that’s mapped to it.
Plus, soon, a third: the Eluu Slack apps support team-branded and per-colleague Slack bots so you can run @AcmeAssistant in your workspace alongside the platform @Eluu bot. The colleague’s memory is shared across surfaces. A conversation that started in Slack is in the same memory the web app reads from.

​
Visibility — who can see what

Two values, used everywhere:
  • Personal — only you can see and use it.
  • Shared — your whole team can see and use it.
Applies to colleagues, integrations, and views. The filter tabs on each list page are Mine / Shared — there is no “All” tab.

​
Permissions — what a colleague can do

Each tool a colleague can call has a permission state:
  • Auto — runs without asking.
  • Review — asks you to approve before running.
  • Block — invisible to the colleague entirely.
Review is the default for tools that mutate external state (sending email, updating a CRM record). Auto is the default for read-only tools.

​
What’s not a separate thing

A few things that look like separate concepts but are not:
  • An output is a file. It lives in the Hard Drive.
  • A chat is a session. Same thing.
  • An artifact is a file. (You’ll see “artifact” in some URLs and the API.)
  • A task is a session. (Code term.)

​
Where to next

Personal vs Shared

The visibility model in detail. Who sees what, who can edit, what changes when you flip the toggle.

Tool permissions

Auto, Review, Block — when to use each, and how Review works in practice.

Glossary

Every term, in alphabetical order.

Create a colleague

Start putting these concepts to work.