Use when the user asks how wick agents work — sessions, projects, presets, providers, channels (Slack/Telegram/web), the pool and its queue, scheduled messages, or where agent state lives on disk. Covers the mental model behind sessions and projects, how to point an agent at a folder, and how to reach the same agent…
Use when the user asks to look something up or act on an external system through wick — check a ticket, query a database, read logs, search Slack, call an API — or asks which connectors are available. Covers the list → drill → schema → execute discovery cycle over MCP, session workspaces for throwaway credentials, and…
Use when the user wants wick to reach an API it has no connector for yet — "buatin connector untuk X", "add a connector for this API", "wrap this cURL", "register our internal MCP server", "add an operation to that connector I made", or asks why a connector they built shows nothing. Covers the custom-connector…
Use when asked anything about wick itself — what it is, what it can do, whether an update is available, what changed in a release, how a feature works, or how to configure something. Points to the live documentation site and release feed so answers come from current sources, never from memory.
Use when the session's prompt says notes are waiting, when picking up work someone (or some earlier session) already started, when you learn something a later session would otherwise have to rediscover, or when the user mentions notes, handover, or "what did we find last time". Notes work on a plain session too — no…
Use when the user asks about installing, updating, removing, disabling, or building a wick plugin — a connector, tool, job, or service shipped as a standalone binary that wick runs in its own process. Covers the four kinds, plugin sources (upload, link, GitHub release incl. private + PAT), Add new plugin, the plugin…
Use when the user asks about agent memory or CPU limits, an agent or build being killed, paused or OOM, the Resource Guard watchdog, the Resources page, usage history, disk space, why a spawn is queued, or how to cap what an agent may consume. Covers the three guard modes and what each actually does, which platform…
Use BEFORE writing any HTML artifact, widget, diagram, chart, image gallery, or dashboard into a wick chat reply. Covers which fence to use (html vs htmlfile vs svg vs mermaid vs imagecard), the theme bridge variables an artifact must use, why fetch() is blocked inside an artifact and what to use instead…
Use when finishing a turn nobody needs to read — a monitor or poll that found nothing new, a scheduled run mid-sequence, bookkeeping between steps, progress notes nobody asked for. Also use when you are about to go silent on a thread where somebody typed a question and is waiting for the answer there, to check whether…
Use BEFORE writing any reply that will be delivered to Slack — Slack uses mrkdwn, not markdown. Plain replies go through unconverted, while replies with tables, headings, bold, label links, nested lists or code fences are sent as a Slack markdown block. Covers which path a reply takes, the syntax that differs (bold…
Use when the session's prompt names a ticket (T-XXXX), when the user talks about tickets, the board, statuses, assignees, or when a conversation has gone off the rails and the work should continue in a fresh session on the same ticket. Covers the ticket model (one ticket, many sessions), keeping status honest, and…
Use when the user asks to build, edit, debug, or run a wick workflow — a multi-step automation stored as a graph of typed nodes with triggers (cron, channel, webhook, manual). Covers when a workflow is the right tool versus an agent or a job, the node catalog, trigger types, the render context, and how to author one…
Use when an HTML artifact / widget preview in wick chat misbehaves — blank or clipped iframe, "violates the following Content Security Policy directive", a stylesheet or script that never loads, images blocked by img-src, a slide deck whose navigation is dead, or a preview that needs to read a session file. Covers the…
Use when deploying or replacing the wick binary on a running host — "how do I ship this build", reload --binary, a refused candidate ("refusing to install this binary", sha256 mismatch, "--yes was not given", "cannot replace … as this user") — or when an update caused downtime: a 502/503 during deploy, killed agent…
Use when work will outlive the turn that started it — a build, a deploy, a migration, a long test run — and you want to be TOLD how it went instead of guessing when to check. Also use when a script, cron job, or CI step on this host should be able to speak into this conversation, or should show its PROGRESS while it…
Use when a reply in the wick web chat should offer the user buttons instead of asking them to type — a proposal to approve or reject, a choice between options, a progress summary, a hand-off to another agent — and when you receive a message that starts with [postback card=…]. Covers the actioncard fence (schema…
Use when the user asks you to BUILD a wick plugin — write the code for a new connector, tool, job, or service plugin, wrap existing code as one, or turn an HTTP app, webhook receiver or remote agent into a service plugin. Covers picking the kind, starting from plugins/ /template, the Module contract and main.go entry…
Use when building, changing, testing or debugging a wick SERVICE plugin — the always-on plugin wick supervises and serves at /x/{key}/ (webhook receivers, public or token APIs, pages for signed-in users, A2A / Team remote agents). Covers the pkg/service Module (Meta, Routes, Configs, CallbackScopes, Register…
Use when you need to come back later, repeat something on a cadence, or WAIT for something to finish — a Bitbucket pipeline, a build, a deploy, a ticket or job status — without burning an LLM turn on every check. Covers wickschedulemessage type=message (wake the agent every fire) vs type=watch (poll with…
★not rated 3 3d agoA171 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: