Modules

Document analysis and field extraction

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

Telegram bot webhook handler with registry-based command routing

MCP (Model Context Protocol) server for Wippy — exposes tools to LLM clients over stdio

Userspace components for user management and integrations

Recursive web-based code editor with LSP support

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.

Docker container management with contract-based API

e2e cross-env queue fix validation (incident 2026-05-18)

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.

System monitor — stats collector and TUI dashboard for Wippy applications

Kickside MCP — user- and workspace-scoped Model Context Protocol endpoints. A user mints a scoped bearer credential whose synthetic principal is granted, over a chosen component subtree (their account root or a workspace slice), only the access the owner themselves holds. A single stateless streamable-HTTP endpoint multiplexes every credential; two-layer authz (tool allowlist + the native component access model) gates each call. Tokens are hashed at rest and shown once.

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 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 Google — Google OAuth connection provider, agent traits and connection picker for Gmail, Drive, Calendar, Docs, Sheets, Slides, Contacts and Analytics.

Kickside HubSpot — private-app-token connection provider for the HubSpot CRM. Reads include CRM records plus meetings, notes, emails, and calls; writes are limited to contacts, companies, deals, and tasks.

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.