Assistants

An assistant is the unit of identity in sidanclaw. It owns memory, channel connections, tools, scheduled tasks, and a system prompt. You can have many assistants. Each is a separate persona with its own context.

Why have multiple assistants

Memory is scoped per-assistant, so a single assistant ends up confused if you mix client-facing and internal contexts. The clean pattern is: one for internal ops, one for sales, one per public-facing project (e.g. a community Q&A bot).

Anatomy of an assistant

Identity at the centre, five capability layers around it. Every other surface in sidanclaw maps to one of these layers.

Core
Assistant identity

Name, persona, system prompt. Everything below hangs off this.

  • 01Memory

    Auto-saved facts about you and your business. Retrieved every turn.

  • 02Channels

    Workspace-owned. Web is always on; Telegram and Slack are BYO.

  • 03Tools

    Built-ins plus per-connector tools (Calendar, Gmail, Notion …).

  • 04Scheduled tasks

    Cron-like jobs the assistant runs on its own session.

  • 05Knowledge base

    Workspace-scoped, sensitivity-tiered, optionally GitHub-synced.

Solo vs. workspace-shared

Every assistant belongs to a workspace: your company brain from day 1, even when you're the only member. Invite teammates and the same assistant becomes shared. Everyone talks to the same memory and KB. See Workspaces & sharing.