✨ Available on CodeCanyon — Krikkit: from a brief to a living site.

AI Chat

Chat is the primary way users build. The agent streams replies, runs tools, writes files, and can inspect the live preview in a browser-like pipeline.

Composer

Multi-line prompt input
Attachments — images for vision-capable models (POST …/workspace/chat/attachment)
Model selector — when Admin → Lab Console allows model selection
Project tasks panel — TodoManager plan list
Send starts (or continues) an agent session

Streaming UI

Element	Meaning
Thinking	Collapsible “Thought for N s” from `<Thinking>…</Thinking>`
Tool cards	Active/complete labels (`taskNameActive` / `taskNameComplete`)
File write cards	Fenced `lang file="path"` blocks applied to the workspace
Clarifying questions	Structured `<ClarifyingQuestions>` JSON — one question at a time with radio options
Credits	Balance; insufficient → upgrade drawer

Stream: GET …/chat/stream/{messageId} (SSE).
Cancel: POST …/agent/sessions/{sessionId}/cancel.

Optional notification sounds when a run finishes (admin: Lab Console).

Clarifications

When the goal is ambiguous, the agent asks structured questions instead of free-form bullets. Answers return as a follow-up user message; then implementation continues.

Agent tools

Schemas live in resources/prompts/Builder/Tools.json (runtime meta in config/builder_tools.php).

Executable tools

Tool	What it does
`parse_ui`	Structured UI → file writes
`GetOrRequestIntegration`	Check/request Supabase (and similar) before inventing backends
`ApplySupabaseMigration`	Propose SQL migration (user Allow/Skip)
`GenerateDesignInspiration`	Design brief for the project
`TodoManager`	Plan tasks: set / move / add / read / mark done

File directives (non-Task)

Directive	Format
Write / edit	Fenced code with `file="path"`
Delete	`<Delete File file="path" />`
Move	`<Move File from="…" to="…" />`

Typical tool order: parse_ui → integrations → migrations → design inspiration → todos → search/ls/read → web → InspectSite.

Browser / InspectSite

InspectSite is how the agent “looks at” the running site:

User asks for a visual change or the agent wants to verify UI
Agent calls InspectSite with preview URLs
Screenshot service returns images into the tool result
Agent reasons over the capture and edits files or suggests design tweaks

This pairs with user Inspect mode (click-to-select + inspector) described in Workspace.

Plan → build (todos)

TodoManager streaming creates a checklist. The composer shows Project tasks. Users can follow plan stages before heavy generation.

Auto build-fix

After edits, Krikkit can run npm run build and open a background-fix stream if the build fails (…/agent/background-fix). Limits: KRIKKIT_BUILDER_CHAT_AUTOFIX_MAX_ATTEMPTS, product repair caps.

Limits (operators)

Env / config	Role
`KRIKKIT_BUILDER_CHAT_MAX_MESSAGES`	History window
`KRIKKIT_BUILDER_CHAT_HISTORY_MAX_CHARS`	Context size
`KRIKKIT_BUILDER_CHAT_MAX_TOOL_ROUNDS`	Tools per turn
`KRIKKIT_BUILDER_CHAT_MAX_CONTINUATIONS`	Continuations
`KRIKKIT_CREDITS_*`	Metering
`KRIKKIT_READ_FILE_MAX_RESULT_BYTES`

SearchRepo