Modules

Kickside connections — provider credentials, resource discovery, and reply targets as components.

User management and security tokens

Base contracts for userspace components

File upload handling with content processing and resource management

Kickside Widgets — shared UI web components reused across modules. Ships icon/model/multiselect/schedule pickers used by agents, knowledge, skills, and navigation appearance.

Kickside automations — the generic install/control/uninstall engine for the unified automation model (component-backed instances, id-based rollback, reflection-dispatched controls, cron-backed scheduled actions). Domain types are contributed by their own modules.

Typed executable Blocks for headless and visual Flow composition.

Convert PDF, Office, legacy Office, or RTF input into Markdown, with optional image extraction

Kickside users — auth, token storage, user/group persistence, directory lookup, per-user profile field store, admin API, and admin web component.

Kickside Models — the LLM model catalog, app-level provider profiles, DB-backed model overlays, resolver binding, discovery APIs, and settings web component. Registry ships defaults; runtime profiles/discovered models live in DB/cache.

Kickside user agents — agent/tool registries, user-created agent components, the agent resolver, runner, and capability library, with a user-facing CRUD API.

Kickside transform — the shared item transform (none|expr|llm|code|func) that maps a source item into sink/endpoint input. Exposed as a library so every automation (poller, webhook, reaction) runs identical transform semantics from one place.

Task scheduling service with interval and cron support, plus live scope resolution

Kickside Content Renderers — isolated, reusable content-viewer web components. <wc-resource-view> host picks + mounts a viewer (<wc-render-markdown>/<wc-render-pdf>/<wc-render-image>) by content-type; each viewer is its own lazy bundle so heavy deps never enter a host. Used by the wiki, uploads, inbox, anywhere a resource needs inline rendering.

Kickside knowledge bases — KB registry, document/graph KB schema and data-access stores, ingestion/injection workers, concept-graph enrichment, and a user-facing CRUD API.

Kickside inbox — central review/approval inbox with declarative, web-component-rendered item types and realtime updates.

Kickside OAuth — OAuth 2.0 connection management with PKCE, encrypted token storage, and background refresh. Exposes the connector + oauth_connection contracts that provider plugins bind to.

Provider-neutral channel responder and shared external chat runtime for direct messages and shared chat channels.

Universal external-identity linking — map a provider account (discord, slack, telegram, …) to a Kickside user via short-lived dashboard-issued codes, so any bot resolves "who is this external sender" provider-neutrally.

Kickside dashboard — a registry-driven deployment overview. Discovers the installed navigable surfaces (view.components / ui.nav_items) and renders each as a card with the human description pulled from the entry meta and the owning module's ns.definition. No hardcoded module list; the page reflects whatever is installed.