kickside

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.

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 Hub — module discovery and lifecycle management. Ships the kickside-hub System surface plus a standalone onboarding component that recommends real catalog modules and reviews selected installs sequentially through Keeper.

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.

Kickside security — scope and policy administration surface for app-owned security scopes.

Kickside UI — platform navigation API plus admin UI surfaces. Ships the kickside-appearance web component (a System tab) that edits navigation layout, categories, and per-surface overrides backed by kickside.ui settings.

Kickside Data Sync automation kind — source-to-destination synchronization built on the shared automation engine.

Kickside realtime — a centralized contract for pushing topics to connected UIs. broadcast() fans out to every client via the wippy/relay central hub; notify() targets one user's hub. Any module (nav, inbox, …) publishes through one seam so all UI reacts live.

Render a PDF — from a URL or a binary blob — into per-page PNG, JPEG, or WEBP images

Kickside KB10 — the document/graph knowledge-base engine. Owns the kb10_* schema and node/edge/embedding store, durable embeddable/queryable/deletable bindings, and the kb_store engine contract used by kickside/knowledge.

Multi-user-safe Streamable HTTP MCP connections and dynamic agent tools for Kickside.

Kickside SSO — user single sign-on via OAuth2/OIDC identity providers (Google, Microsoft/Entra, GitHub, generic OIDC). Pluggable connectors, settings-driven configuration, account linking by verified email.

Kickside SSO — Google login provider. A registry-declared sso.provider (descriptor + credentials + its own enable-gate) for the kickside/sso core; rendered by the shared provider card.

Optional visual authoring, versioning, and run lifecycle for published Workflows composed from canonical Blocks and native Dataflow nodes.

Kickside sessions — a self-contained web component that lists the user's chat sessions and lets them rename, resume, restart, preview, and delete. Reuses the wippy/session API; ships a single start-token endpoint for "new chat with the same agent".

Kickside DM — bridges inbound external direct messages onto private, user-owned agent chats. After pairing an external identity to an internal user (surfaced via inbox), a DM is backed by a user-owned kickside.core thread; a provider-chosen automation runs the agent on it under the user's actor, and replies go back out via kickside.connection.

Kickside — modular AI workspace. Ships the runnable shell and core services; administrators add optional capabilities from the Hub during or after setup.

Kickside Discord provider — bot-token connection, reply provider, resource discovery, normalized inbound adapter for DM/channel bots, and data-sync source/sink for channel messages.

Web research tools and typed evidence Sources backed by Google and Brave search.

Sandboxed Lua execution and one canonical Run Code Block, bounded to an installer-whitelisted tool set. Ships the Block editor, SDK-reference and assist endpoints, a dry-run-validated generator, and the agent trait.