SUZENT / Docs
THE SUZENT HANDBOOK

Architecture

How Suzent's runtime, tools, memory, and clients work today.

Agent Communication

Suzent treats every agent-backed conversation as an addressable session. The stable agent_id is its chat ID; kind describes how the session originated: interactive , subagent , cro

Canvas (A2UI)

The Canvas is a structured UI layer that lets the agent render interactive components — tables, forms, cards, buttons, badges — directly in the Suzent interface, alongside the chat

Chat Storage

Each chat's append-only JSONL event log is its source of truth. chats.db is an index of the logs: the chats table and its full-text search rows are what the sidebar, search and eve

Focal Agent (Suzent Regent)

The Focal Agent is the singleton chat shown to users as Suzent Regent , or Regent in the app. It sees every project, dispatches work to project sessions, and is woken when one of t

Memory Architecture

How memory is written, consolidated, indexed, and read. Companions: Memory for how the dream behaves from the outside, Memory internals for the class-by-class reference. Three tier

Memory Internals

This page describes the implementation-level structure of Suzent memory as it exists today. Layers Layer Responsibility --- --- Agent prompt and tools memory_search , memory_update

Native mobile clients

Architecture decision Suzent mobile uses SwiftUI on iOS and Kotlin/Jetpack Compose on Android. Both applications live in this monorepo; Python remains managed by uv, Android by Gra

Model capabilities and roles

This page is for contributors. For choosing providers and assigning model roles as a user, see Models & Providers. Suzent keeps a registry of per-model metadata — context window, c

Plugins

This page is for plugin authors and contributors. For installing and enabling plugins, see Plugins. A plugin is a unit the user installs and removes. It can bring packages, code, o

Chat Post-Processing

When an agent turn finishes, Suzent runs a series of background tasks — writing the transcript, updating memory, compressing context, and saving state. This page explains how that

Shared resource API

Desktop and paired native clients use a versioned resource interface at /api/v1 . Models, projects, chat navigation/details/actions, notifications, approvals, media, uploads, live

Stream recovery protocol

Desktop chat sends, retry/edit, steering, approval resume, heartbeat and Canvas turns can recover their in-progress output after a page reload or connection loss. Native and ACP pr

System Reminders & File Citations

System reminders carry runtime-authored context for the model. File citations render source references for the user. Both use Private Use Area (PUA) markers, but invisible formatti

Tool system

This page is for contributors. For what tools do from a user's point of view, see Tools. Tools extend the agent's capabilities, allowing it to interact with the filesystem, web, me