kickside

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.

Typed executable Blocks for headless and visual Flow composition.

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 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 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.

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

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.

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

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

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.

Kickside Transfer — export and import a user's own components (and their backing data) between environments. Owns the exportable-component picker, the batch orchestrator, archive packaging, and the export/import API.

Kickside webhooks — user-minted, secret-secured, schema-validated public webhook endpoints. Each webhook is a thread-backed component (class kickside.webhooks) that acts as a data-flow trigger source; the public endpoint verifies the secret, validates the body against the webhook's declared schema, and appends it as a thread event the poller drains.

Kickside webscout — web research tools and an installable GTM candidate scan through Google Custom 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.

Kickside Atlassian — Jira and Confluence provider. Self-declares as an oauth_provider discovered by kickside/oauth (3LO) and supports stored-credential connections (Cloud API token / Server PAT). Ships agent tools (JiraRead/JiraWrite, ConfluenceRead/ConfluenceWrite) over a shared authenticated transport.

Kickside Google — Google OAuth connection provider, agent traits and connection picker for Gmail, Drive, Calendar, Docs, Sheets, Slides, Contacts and Analytics.

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.

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 PhantomBuster — API-key connection provider with agent discovery, read/write tools, and an installable GTM candidate pull.