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.

A colleague is an Eluu teammate you build. Each colleague owns one business function or role and replaces what you’d otherwise buy as a focused AI SaaS product. It has a name, a role, a personality, a set of abilities, and a private workspace that persists across every conversation. This page is the overview. The five-step wizard for creating one is in Create a colleague.

​
One colleague = one role

The mental model that makes Eluu work: a colleague maps to a business role, not a task type. Don’t build a “data colleague” or a “writing colleague” — those are too vague. Build a “sales operations colleague” or a “customer success colleague”. How tightly you scope a role depends on the size of the work:
Org sizeWhat one colleague typically owns
Personal use or 1-person teamAn entire function — one “sales colleague” does prospecting, outreach, and pipeline.
Startup (5-25 people)One function each — sales, customer success, ops, marketing, research. Three to five colleagues total.
Scaling (25-100)Sub-functions — meeting intelligence, renewals, inbound triage as separate colleagues.
EnterpriseDozens of colleagues running real workloads in parallel, on schedules, with verification loops.
You add colleagues as you grow. The platform stays the same.

​
What a colleague is

A colleague has five layers, configured in five wizard steps:
StepWhat you set
1. IdentityName, role, description, avatar, cover, visibility (Personal or Shared)
2. PersonalityVoice, tone, refusals, default workflow
3. AbilitiesModel, speed tier, skills, custom playbooks, context files
4. BehaviourCoding/output rules, communication rules, safety rules, custom rules
5. IntegrationWhich integrations the colleague uses, and the permission for each tool
Once you save it, you can reach the colleague from every surface — web app, Slack, browser extension — and it remembers everything across sessions.

​
How many colleagues you should have

Most teams start with three to five colleagues, each focused on a different role. A useful pattern:
  • A general assistant — the default colleague Eluu created for you on sign-up.
  • One per business function — sales, customer success, engineering on-call, marketing.
  • One per recurring deliverable — a “weekly briefing” colleague, a “morning digest” colleague.
Building more colleagues is cheap. They’re configuration. Don’t pile every responsibility on one colleague. A colleague that does five unrelated jobs is worse than five colleagues each doing one. Sharper roles produce sharper results — and the workspace memory of a focused colleague compounds faster. If a colleague’s role description fits in one sentence, the role is well-scoped. If it needs three sentences with “and” between them, split it.

​
The list page

Open Colleagues in the sidebar to see all colleagues your team has built.
  • Two filter tabs: Mine and Shared. There’s no “All” tab.
  • Mine shows colleagues you’ve built as personal (only you can use them).
  • Shared shows colleagues anyone on your team can use.
  • The Add colleague button opens the creation wizard.
Each card shows the colleague’s avatar, name, role, description, and a Personal/Shared chip.

​
Personal vs Shared

Visibility is a single setting on the colleague’s Identity step.
  • Personal — only you see the colleague, its sessions, its workspace, and its files.
  • Shared — your whole team uses the colleague. Conversation history, files, and workspace are visible to all members.
Only the creator of a colleague can change its visibility. Other team members (even admins) can’t toggle it. See Personal vs Shared for the full model.

​
What you can use to extend a colleague

Three extension points:
  • Skills — packaged, reusable workflows. Import from a GitHub URL or pick from your team library. Use these when you have a multi-step procedure you’ll repeat. See Skills.
  • Custom playbooks — slash commands defined per colleague. Use these for prompts you re-run frequently. See Slash commands.
  • Context files — files the colleague always has loaded in its workspace. Useful for style guides, product docs, account lists.

​
Permissions on a colleague

Members on your team can use any Shared colleague. Whether they can edit it is a separate question:
  • The colleague’s creator can always edit and delete it.
  • Owners and admins can manage colleagues if canManageColleagues is enabled (default for both roles).
  • Plain members cannot create, edit, or delete colleagues.
Members can still chat with shared colleagues. They can’t change the configuration.

​
Memory — the moat

Each colleague has its own workspace: a Git-backed file system that persists forever. Across sessions, your colleague writes notes, builds files, accumulates context. After a few weeks of use:
  • It knows your team’s projects and how you talk about them.
  • It knows your data shape and where things live.
  • It knows your tone and style preferences.
You can’t export this. Switching products means starting from zero. This is the most underrated feature of Eluu — and the reason teams that adopt rarely leave.

​
Where to next

Step 1 — Identity

Start building a colleague. Name, role, description, visibility.

Editing a colleague

Update an existing colleague. The five-step interface is the same.

Personal vs Shared

The visibility model in depth.

The mental model

How colleagues fit with sessions, jobs, views, and files.