[{"data":1,"prerenderedAt":1233},["ShallowReactive",2],{"search":3,"content-guide\u002Fcode-tasks":442,"surround-\u002Fguide\u002Fcode-tasks":1228},[4,8,12,16,20,24,28,32,36,40,44,48,52,56,60,64,68,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196,200,204,208,212,216,220,224,228,232,236,240,244,248,252,256,260,264,268,272,276,280,284,288,292,296,300,304,308,312,316,320,323,327,331,335,339,343,347,351,355,359,363,367,371,375,379,383,387,391,395,399,403,407,411,415,419,423,426,430,434,438],{"path":5,"title":6,"description":7},"\u002Fguide","Guide","Product guides for Owlat — a modular, self-hosted email platform. Learn how to send campaigns, run a personal mailbox, manage a team inbox, and more.",{"path":9,"title":10,"description":11},"\u002Fguide\u002Fgetting-started","Welcome to Owlat","Set up your Owlat workspace and send your first email — from deploying the stack to verifying a domain, building your audience, and launching a campaign.",{"path":13,"title":14,"description":15},"\u002Fguide\u002Fcontact-properties","Contact Properties","Custom fields that extend built-in contact data with your own values for segmentation.",{"path":17,"title":18,"description":19},"\u002Fguide\u002Ftopics","Topics","Topics are explicit audience groups you manage by hand — ideal for opt-in subscribers, imported cohorts, and organized contact buckets you target with campaigns.",{"path":21,"title":22,"description":23},"\u002Fguide\u002Fsegments","Segments","Build dynamic, rule-based contact groups from properties, email activity, and topic membership, re-evaluated from current data each time they're used.",{"path":25,"title":26,"description":27},"\u002Fguide\u002Fforms","Forms","Form Endpoints collect new contacts from your website or landing pages by exposing a public endpoint that accepts submissions and feeds them into a topic.",{"path":29,"title":30,"description":31},"\u002Fguide\u002Fcampaigns","Campaigns & Reporting","Build and send marketing campaigns to a topic or segment with the five-step wizard, optional A\u002FB testing, and full delivery reporting.",{"path":33,"title":34,"description":35},"\u002Fguide\u002Fab-testing","A\u002FB Testing","Compare two variants of a campaign on a test group, then automatically or manually send the winning version to the rest of your audience.",{"path":37,"title":38,"description":39},"\u002Fguide\u002Fautomations","Automations","Send emails automatically based on triggers, delays, and conditions — build welcome series, trial flows, and follow-ups once and let Owlat run them.",{"path":41,"title":42,"description":43},"\u002Fguide\u002Ftransactional","Transactional Emails","One-to-one emails your application triggers in response to a user action — password resets, order confirmations, welcome emails, and similar notifications.",{"path":45,"title":46,"description":47},"\u002Fguide\u002Fcreate-campaign","Create a Campaign","Walk through Owlat's five-step campaign wizard: Basics, Audience, Content, A\u002FB Test, and Review & Send.",{"path":49,"title":50,"description":51},"\u002Fguide\u002Fsend-campaign","Send & Monitor a Campaign","How to send your campaign and track its performance with real-time metrics.",{"path":53,"title":54,"description":55},"\u002Fguide\u002Fquick-start","Quick Start","The fastest path from a blank Owlat workspace to a live email campaign, from your first template through sending and reviewing results.",{"path":57,"title":58,"description":59},"\u002Fguide\u002Ftransactional-setup","Transactional Email Setup","Set up and send transactional emails like password resets and order confirmations via the Owlat API and SDKs.",{"path":61,"title":62,"description":63},"\u002Fguide\u002Fdeliverability","Deliverability","Verify sending domains, manage your blocklist, monitor sending reputation, and stay compliant so your emails reach the inbox.",{"path":65,"title":66,"description":67},"\u002Fguide\u002Fapi-keys-webhooks","API Keys & Webhooks","Create API keys for programmatic access and set up outbound webhooks to receive real-time notifications for email and contact events.",{"path":69,"title":70,"description":71},"\u002Fguide\u002Ffeature-flags","Feature flags","Owlat is modular — every feature listed in this guide can be turned on or off. This page is the user-facing overview of how to do it.",{"path":73,"title":74,"description":75},"\u002Fguide\u002Fteam-permissions","Team & Permissions","Use role-based access to control what each member of your organization can do, with Owner, Admin, and Editor roles.",{"path":77,"title":78,"description":79},"\u002Fguide\u002Faudit-logs","Audit Logs","A chronological record of significant actions in your Owlat organization, so you can see who did what and when.",{"path":81,"title":82,"description":83},"\u002Fguide\u002Fshare-links","Share Links","Create temporary preview links to share email designs with stakeholders who don't have dashboard access.",{"path":85,"title":86,"description":87},"\u002Fguide\u002Fpostbox","Postbox — Personal Email","Per-user mailboxes with a webmail interface and native IMAP\u002FSMTP support. Run your own Gmail-equivalent personal mailbox on your Owlat instance.",{"path":89,"title":90,"description":91},"\u002Fguide\u002Fmigrate-from-google","Migrate from Google","Import your full Gmail history into Owlat over IMAP, and let your AI assistant learn from every imported conversation.",{"path":93,"title":94,"description":95},"\u002Fguide\u002Fteam-inbox","Team Inbox","Triage inbound email as a team: read AI-classified threads, approve, edit or reject agent drafts, work the review queue, and manage quarantine.",{"path":97,"title":98,"description":99},"\u002Fguide\u002Femail-editor","Email Editor","A block-based visual editor for building responsive emails that render consistently across desktop, mobile, Outlook, Gmail, and Apple Mail.",{"path":101,"title":102,"description":103},"\u002Fguide\u002Fai-agent","AI Agent & Autonomy","Configure the AI agent that classifies and drafts replies to inbound mail: auto-reply settings, the health dashboard, circuit breakers, autonomy rules, and the knowledge backfill.",{"path":105,"title":106,"description":107},"\u002Fguide\u002Fknowledge-graph","Knowledge Graph","Browse, search, and manage Owlat's typed organizational knowledge — the 7 entry types, source attribution, confidence decay, relations, and how entries are extracted from mail.",{"path":109,"title":110,"description":111},"\u002Fguide\u002Ffiles","Files","Upload, browse, search, tag, and version documents in the file library.",{"path":113,"title":114,"description":115},"\u002Fguide\u002Fchat","Team Chat","Use Owlat's built-in team chat: public and private channels, direct messages, mentions, attachments, and channels linked to an inbox conversation.",{"path":117,"title":118,"description":119},"\u002Fguide\u002Fcode-tasks","Code Tasks","Queue coding-agent tasks, watch them move from queued through review, and run the code-worker sidecar that opens the pull requests.",{"path":121,"title":122,"description":123},"\u002Fguide\u002Faudience-data","Audience Data: Identities, Relationships & Timeline","Unify a contact across email, phone, and messaging channels, merge duplicates, map relationships, and read the cross-channel interaction timeline.",{"path":125,"title":126,"description":127},"\u002Fguide\u002Fimporting-contacts","Importing & Exporting Contacts","Bring contacts into Owlat from a CSV or from Mailchimp and Stripe, export them back out, and run bulk operations on your audience.",{"path":129,"title":130,"description":131},"\u002Fguide\u002Faccount","Your Account & Data","Export your data as JSON or CSV, request account deletion with a 30-day grace period, and use the onboarding checklist and the public preference center.",{"path":133,"title":134,"description":135},"\u002Fguide\u002Fchannels","Communication Channels","Configure SMS, WhatsApp, and generic-webhook channels, monitor channel health, and understand which channels are fully live today.",{"path":137,"title":138,"description":139},"\u002Fguide\u002Fdesktop-app","Desktop App","Install the Owlat desktop app, connect one or more workspaces, switch between them, and use native notifications, tray badges, shortcuts, and deep links.",{"path":141,"title":142,"description":143},"\u002Fguide\u002Femail-templates","Email Templates","Reusable email designs that define the structure, content, and personalization of every campaign and transactional message you send in Owlat.",{"path":145,"title":146,"description":147},"\u002Fguide\u002Fai-assistant","AI Assistant","Owlat's multi-turn, streaming, tool-calling AI assistant — a private chat surface that can search your workspace and draft copy, plus @assistant replies inside team chat.",{"path":149,"title":150,"description":151},"\u002Fguide\u002Fsecurity-scanning","Sending Security & Scanning","Owlat's security scanning: a content check for spam and phishing, an attachment scan for malware, and a Google Safe Browsing URL check. Suspicious content goes to a review queue.",{"path":153,"title":154,"description":155},"\u002Fguide\u002Fsystem-updates","System & Updates","The owner-only System & Updates screen: your current Owlat version, container health, LLM spend, and the in-app one-click updater with history.",{"path":157,"title":158,"description":159},"\u002Fguide\u002Foperating-modes","Operating Modes","The different ways to run Owlat at a company — read external mailboxes over IMAP, send transactional or marketing email through a delivery provider, host your own mail server, or run a team inbox with AI — and the rules that keep each combination coherent.",{"path":161,"title":162,"description":163},"\u002Fguide\u002Fsaved-blocks","Saved Blocks","Create reusable, linked content blocks you can drop into any email — edit one and every email that uses it updates automatically.",{"path":165,"title":166,"description":167},"\u002Fguide\u002Fmedia-library","Media Library","Manage, organize, search, and reuse images and files across your emails from one centralized hub.",{"path":169,"title":170,"description":171},"\u002Fguide\u002Femail-theme","Email Theme","Set your organization's default colors, font, and email width so every new template starts from a consistent baseline.",{"path":173,"title":174,"description":175},"\u002Fguide\u002Ftranslations","Translations","Send one email in multiple languages: add per-language translations to a single template and Owlat picks the right version for each recipient.",{"path":177,"title":178,"description":179},"\u002Fguide\u002Fcontacts","Contacts","How to add, view, organize, and manage contacts in Owlat, including sources, the contact detail tabs, and subscription compliance.",{"path":181,"title":182,"description":183},"\u002Fapi","API Overview","Owlat exposes authenticated API endpoints under your Convex site URL.",{"path":185,"title":186,"description":187},"\u002Fapi\u002Fwebhooks","Webhooks","Owlat supports both outbound customer webhooks and inbound provider webhooks.",{"path":189,"title":190,"description":191},"\u002Fapi\u002Fpublic-endpoints","Public Endpoints","These routes are public-facing and usually accessed from email links or embedded forms.",{"path":193,"title":194,"description":195},"\u002Fapi\u002Fwebhook-payloads","Webhook Payloads","The authoritative wire contract for outbound webhooks: envelope, signature headers, per-event data shapes, and payload versioning.",{"path":197,"title":198,"description":199},"\u002Fapi\u002Finbound-channels","Inbound Channel Webhooks","Provider webhook reference for inbound SMS, WhatsApp, and generic-channel messages, plus the MTA mailbox and credential callbacks.",{"path":201,"title":202,"description":203},"\u002Fapi\u002Fauthentication","Authentication","Secure API access with organization-scoped API keys.",{"path":205,"title":206,"description":207},"\u002Fapi\u002Fsdk","TypeScript SDK","Typed client for the Owlat API, usable from Node.js, Bun, Deno, or any server-side JavaScript runtime.",{"path":209,"title":210,"description":211},"\u002Fapi\u002Fsdk-java","Java SDK","The official `owlat-sdk` package provides a typed client for interacting with the Owlat API from any JVM application. Requires Java 11+.",{"path":213,"title":214,"description":215},"\u002Fapi\u002Fcontacts","Contacts API","Manage contacts for your organization.",{"path":217,"title":218,"description":219},"\u002Fapi\u002Ftopics","Topics API","Manage topic membership through authenticated endpoints.",{"path":221,"title":222,"description":223},"\u002Fapi\u002Fevents","Events API","Send contact events to drive segmentation and automation triggers.",{"path":225,"title":226,"description":227},"\u002Fapi\u002Ftransactional","Transactional API","Send published transactional templates to a recipient.",{"path":229,"title":230,"description":231},"\u002Fapi\u002Fforms","Forms API","Capture subscribers through public form endpoints.",{"path":233,"title":234,"description":235},"\u002Fdeveloper","Developer Guide","Technical architecture, feature-flag model, and provider abstractions used by Owlat.",{"path":237,"title":238,"description":239},"\u002Fdeveloper\u002Fmta-system","MTA System","Owlat's custom Mail Transfer Agent for direct SMTP delivery with intelligent rate limiting, bounce processing, and IP warming.",{"path":241,"title":242,"description":243},"\u002Fdeveloper\u002Ffeature-flags","Feature flags — developer reference","How the Owlat feature flag system works: single source of truth, dependency resolution, docker profile mapping, and how to add a new flag.",{"path":245,"title":246,"description":247},"\u002Fdeveloper\u002Fhow-email-works","How Email Works","A technical deep-dive into how email actually works — from SMTP and DNS to authentication, deliverability, and the differences between marketing and private email.",{"path":249,"title":250,"description":251},"\u002Fdeveloper\u002Femail-security","Email Security","Content scanning, attachment validation, URL reputation checking, and malware detection for outbound emails.",{"path":253,"title":254,"description":255},"\u002Fdeveloper\u002Fpostbox-architecture","Postbox Architecture","How the Postbox personal-mail feature is wired — schema, IMAP server, app-password auth, outbound relay, inbound delivery, and external mailboxes.",{"path":257,"title":258,"description":259},"\u002Fdeveloper\u002Fproviders","Providers","Pluggable provider abstractions for LLM, email sending, notifications, vector stores, and analytics, selected per-deployment so self-hosters can swap implementations without code changes.",{"path":261,"title":262,"description":263},"\u002Fdeveloper\u002Fcampaign-internals","Campaign Internals","How the campaign backend works: two status machines, send pre-flight, the send orchestrator, emailSends records, and the priority workpools.",{"path":265,"title":266,"description":267},"\u002Fdeveloper\u002Faudience-internals","Audience Internals","Backend reference for contact resolution, the double opt-in lifecycle, topic subscription, the conditions registry, and segment evaluation.",{"path":269,"title":270,"description":271},"\u002Fdeveloper\u002Fautomation-internals","Automation Internals","How the automation run engine works: the step walker, the lifecycle state machine, trigger fanout, the three step types, and the resilience cron.",{"path":273,"title":274,"description":275},"\u002Fdeveloper\u002Fdeliverability-infrastructure","Deliverability Infrastructure","The Convex-side deliverability backend: provider routing, health-aware failover, sending reputation with auto-enforcement, IP warming cache, the blocklist, and the content-scan gate.",{"path":277,"title":278,"description":279},"\u002Fdeveloper\u002Farchitecture","Architecture Overview","Owlat follows a modern serverless architecture with real-time capabilities.",{"path":281,"title":282,"description":283},"\u002Fdeveloper\u002Fplatform-operations","Platform Operations","Operator reference for abuse status and the sending gate, the platform-admin roster, content review, org deletion, in-app self-update, dev endpoints, crons, and migrations.",{"path":285,"title":286,"description":287},"\u002Fdeveloper\u002Fscopes","Scopes","What each app and package in the Owlat monorepo is responsible for.",{"path":289,"title":290,"description":291},"\u002Fdeveloper\u002Fself-hosting","Self-Hosting","Deploy Owlat on your own infrastructure with Docker Compose. Complete guide from first boot to production.",{"path":293,"title":294,"description":295},"\u002Fdeveloper\u002Fself-hosting-config","Self-Hosting Configuration","Complete reference for Docker environment variables, Convex backend variables, service topology, and volume persistence.",{"path":297,"title":298,"description":299},"\u002Fdeveloper\u002Fself-hosting-dns-email","DNS & Email Setup","Configure DNS records, DKIM signing, SPF, DMARC, and bounce handling for reliable email delivery.",{"path":301,"title":302,"description":303},"\u002Fdeveloper\u002Fself-hosting-production","Production Deployment","Secure your self-hosted Owlat instance with TLS, firewall rules, backups, and monitoring.",{"path":305,"title":306,"description":307},"\u002Fdeveloper\u002Fself-hosting-maintenance","Maintenance & Updates","Keep your self-hosted Owlat instance up to date, manage backups, scale performance, and troubleshoot common issues.",{"path":309,"title":310,"description":311},"\u002Fdeveloper\u002Fself-hosting-desktop","Desktop Installer","Install Owlat on a bare Linux VPS straight from the desktop app over SSH — no terminal — with a live, animated provisioning timeline.",{"path":313,"title":314,"description":315},"\u002Fdeveloper\u002Fsetup-cli","Setup CLI & Installer","Operator reference for the Owlat self-host tooling: the install.sh one-liner, the owlat-setup CLI, the convex-deploy flow, and admin bootstrap.",{"path":317,"title":318,"description":319},"\u002Fdeveloper\u002Fconvex","Convex Backend","Owlat uses Convex as its serverless backend, providing real-time subscriptions, ACID transactions, and TypeScript-first development.",{"path":321,"title":202,"description":322},"\u002Fdeveloper\u002Fauthentication","Owlat uses BetterAuth with the Convex adapter for authentication and organization (team) management.",{"path":324,"title":325,"description":326},"\u002Fdeveloper\u002Femail-system","Email System","Owlat's email system consists of a visual editor, template management, and multi-provider sending infrastructure.",{"path":328,"title":329,"description":330},"\u002Fdeveloper\u002Femail-renderer","Email Renderer","The @owlat\u002Femail-renderer package converts editor JSON blocks into production-ready HTML emails with cross-client compatibility, CSS inlining, dark mode, and Outlook VML fallbacks.",{"path":332,"title":333,"description":334},"\u002Fdeveloper\u002Fenvironment-variables","Environment Variables","Reference for every environment variable Owlat reads across the Convex backend, web app, MTA, IMAP server, and mail-sync worker.",{"path":336,"title":337,"description":338},"\u002Fdeveloper\u002Fcomponents","Component Library","Reference for the reusable, auto-imported Vue UI components shipped in the packages\u002Fui layer.",{"path":340,"title":341,"description":342},"\u002Fdeveloper\u002Fdecisions","Architectural Decision Records","The architectural decision records for the Owlat project, each capturing the context, the decision, and the trade-offs involved.",{"path":344,"title":345,"description":346},"\u002Fdeveloper\u002Fdecisions\u002F009-model-routing","ADR-009: Task-Based Model Routing","Why Owlat supports per-task LLM model selection instead of using a single model for all pipeline steps.",{"path":348,"title":349,"description":350},"\u002Fdeveloper\u002Fdecisions\u002F010-listing-engine","ADR-010: Listing Engine","Why Owlat replaced four incompatible list-query contracts with one generic listing engine driven by per-entity descriptors.",{"path":352,"title":353,"description":354},"\u002Fdeveloper\u002Fdecisions\u002F001-custom-email-renderer","ADR-001: Custom Email Renderer Over MJML","Why Owlat built a custom table-based HTML email renderer instead of using MJML, gaining full control over VML, dark mode, and per-client rendering.",{"path":356,"title":357,"description":358},"\u002Fdeveloper\u002Fdecisions\u002F002-convex-backend","ADR-002: Convex as Backend","Why Owlat chose Convex over PostgreSQL and Firebase for real-time reactivity, co-located TypeScript logic, and zero-config scaling.",{"path":360,"title":361,"description":362},"\u002Fdeveloper\u002Fdecisions\u002F003-notion-like-builder","ADR-003: Notion-like Email Builder","Why Owlat replaced the traditional 3-panel email editor with a Notion-like single-column canvas for inline WYSIWYG editing.",{"path":364,"title":365,"description":366},"\u002Fdeveloper\u002Fdecisions\u002F004-monorepo-bun-workspaces","ADR-004: Monorepo with Bun Workspaces","Why Owlat uses a monorepo with Bun workspaces and Turborepo for fast installs, atomic cross-package changes, and cached CI.",{"path":368,"title":369,"description":370},"\u002Fdeveloper\u002Fdecisions\u002F005-custom-mta","ADR-005: Custom MTA","Why Owlat built a custom Mail Transfer Agent instead of relying solely on third-party email providers.",{"path":372,"title":373,"description":374},"\u002Fdeveloper\u002Fdecisions\u002F006-self-hosted-convex","ADR-006: Self-Hosted Convex","Why Owlat uses the open-source Convex backend for self-hosting instead of migrating to a different database.",{"path":376,"title":377,"description":378},"\u002Fdeveloper\u002Fdecisions\u002F007-pluggable-llm","ADR-007: Pluggable LLM Provider","Why Owlat uses the Vercel AI SDK with a provider abstraction layer instead of hardcoding a single LLM vendor.",{"path":380,"title":381,"description":382},"\u002Fdeveloper\u002Fdecisions\u002F008-process-architecture","ADR-008: Agent Process Architecture","Why Owlat processes inbound messages with a self-scheduling step walker plus a lifecycle coordinator instead of one sequential function.",{"path":384,"title":385,"description":386},"\u002Fexamples","Examples","Copy-pasteable integration patterns for common Owlat use cases.",{"path":388,"title":389,"description":390},"\u002Fexamples\u002Fwelcome-email","Welcome Email","Send a personalized welcome email when a new user signs up.",{"path":392,"title":393,"description":394},"\u002Fexamples\u002Fbilling-email","Billing Email","Send a billing receipt with an invoice PDF attached after a successful payment.",{"path":396,"title":397,"description":398},"\u002Fexamples\u002Fevent-automation","Event Automation","Trigger automations with custom events for trial lifecycle, feature adoption, and more.",{"path":400,"title":401,"description":402},"\u002Fexamples\u002Fcontact-sync","Contact Sync","Sync contacts from your database to Owlat using upsert patterns and bulk operations.",{"path":404,"title":405,"description":406},"\u002Fexamples\u002Fwebhook-handler","Webhook Handler","Handle Owlat delivery webhooks with signature verification and event routing.",{"path":408,"title":409,"description":410},"\u002Fexamples\u002Fmultilingual-email","Multilingual Email","Send emails in the recipient's preferred language using template translations.",{"path":412,"title":413,"description":414},"\u002Fvision","Vision","Where Owlat is heading — from email platform to unified communication intelligence powered by AI agents.",{"path":416,"title":417,"description":418},"\u002Fvision\u002Fself-hosting","Self-Hosting Architecture","How Owlat runs as a fully self-hosted stack using Docker Compose — open-source Convex backend, custom MTA, and a pluggable LLM provider.",{"path":420,"title":421,"description":422},"\u002Fvision\u002Fagent-pipeline","Agent Pipeline","Technical architecture for the inbound email agent pipeline — step modules, the walker, security scanning, threading, and human review.",{"path":424,"title":106,"description":425},"\u002Fvision\u002Fknowledge-graph","Technical architecture for Owlat's typed knowledge storage — how organizational knowledge is stored, searched, decayed, and maintained.",{"path":427,"title":428,"description":429},"\u002Fvision\u002Fmulti-channel","Multi-Channel & CRM","Technical architecture for channel adapters, unified messaging, contact identity unification, and the CRM hub.",{"path":431,"title":432,"description":433},"\u002Fvision\u002Ffile-system","Semantic File System","Technical architecture for Owlat's semantic file storage — version tracking with provenance today, plus the planned embedding-based retrieval and auto-tagging layer.",{"path":435,"title":436,"description":437},"\u002Fvision\u002Fdesktop-app","Desktop App & Advanced Agents","Architecture of the Owlat desktop shell, visualization agent, adaptive dashboard, agent health, graduated autonomy, and coding agents.",{"path":439,"title":440,"description":441},"\u002Fvision\u002Froadmap","Roadmap","What's planned next for Owlat — the documented-but-unbuilt pieces still being wired, and the enhancements on our radar.",{"id":443,"title":118,"body":444,"description":119,"extension":1222,"meta":1223,"navigation":1224,"path":117,"seo":1225,"stem":1226,"__hash__":1227},"content\u002F1.guide\u002F34.code-tasks.md",{"type":445,"value":446,"toc":1206},"minimark",[447,460,479,484,498,536,562,566,573,584,597,623,627,630,727,730,823,850,854,867,922,925,982,985,1131,1144,1154,1157,1160,1198],[448,449,450,451,455,456,459],"p",{},"Code Tasks is a queue for the AI coding agent. A task carries a plain-language description of a feature or bug fix; the ",[452,453,454],"strong",{},"code-worker"," sidecar is designed to pick it up, clone your repository, write the change with a coding agent, run the test suite, and open a pull request for you to review. The dashboard at ",[452,457,458],{},"Inbox -> Code Tasks"," shows every task and its current stage. This is an admin surface — only owners and admins can create or cancel tasks.",[448,461,462,463,467,468,473,474,478],{},"The backend queue and the dashboard work today, and the code-worker sidecar authenticates with the deployment admin key, claims queued tasks, and reports progress back. The one real deployment gap is that the bundled VPS Compose template does not yet pass ",[464,465,466],"code",{},"CONVEX_ADMIN_KEY"," to the code-worker service (see ",[469,470,472],"a",{"href":471},"#setup-the-code-worker-service-and-its-environment","Setup"," and ",[469,475,477],{"href":476},"#current-limitations","Current limitations",").",[480,481,483],"h2",{"id":482},"what-code-tasks-are","What code tasks are",[448,485,486,487,490,491,494,495,497],{},"The feature has two halves: the ",[452,488,489],{},"queue"," that lives in the Owlat backend (the ",[464,492,493],{},"codeWorkTasks"," table), and the ",[452,496,454],{},", a separate Docker container that does the actual coding work. The dashboard only reads and cancels tasks; the heavy lifting happens out-of-process in the sidecar.",[448,499,500,501,504,505,508,509,512,513,516,517,473,520,523,524,526,527,529,530,532,533,535],{},"Code Tasks is gated behind the ",[452,502,503],{},"Extract code tasks from inbox"," feature flag (",[464,506,507],{},"inbox.codeTasks","), which is ",[452,510,511],{},"off by default",". Because the flag ",[464,514,515],{},"requires"," both ",[464,518,519],{},"inbox",[464,521,522],{},"ai.agent",", enabling it also turns those on, and turning ",[464,525,522],{}," back off cascades Code Tasks off again. When the flag is on, a ",[452,528,118],{}," entry appears in the Inbox section of the sidebar; when it's off, the sidebar entry disappears and the page itself is gated by the ",[464,531,507],{}," feature requirement. See ",[469,534,70],{"href":69}," for how to toggle it.",[537,538,541],"callout",{"title":539,"type":540},"Automatic creation from inbound mail","info",[448,542,543,544,546,547,550,551,554,555,558,559,561],{},"When ",[464,545,507],{}," is enabled, inbound messages classified as a ",[452,548,549],{},"feature request"," are automatically turned into queued code tasks via ",[464,552,553],{},"createFromInbound"," (idempotent per inbound message, so the same message never files two tasks). Manual creation via the ",[464,556,557],{},"codeWorkTasks.create"," mutation still exists in addition. See ",[469,560,477],{"href":476},".",[480,563,565],{"id":564},"creating-and-cancelling-a-task","Creating and cancelling a task",[448,567,568,569,572],{},"A task needs one thing: a ",[452,570,571],{},"description"," of what you want done. Write it the way you'd write a ticket — \"Add a CSV export button to the contacts table\", \"Fix the off-by-one in the digest date range\". The clearer the description, the better the coding agent's output, because that text is passed verbatim to the agent and becomes the pull-request summary.",[448,574,575,576,579,580,583],{},"Creating a task requires the ",[464,577,578],{},"organization:manage"," permission (owners and admins). The new task starts in the ",[452,581,582],{},"queued"," stage and waits for the code-worker to pick it up.",[537,585,587],{"title":586,"type":540},"Creating a task in the dashboard",[448,588,589,590,593,594,596],{},"The Code Tasks dashboard has a ",[452,591,592],{},"New code task"," button — in the header and in the empty state — that opens a description modal and files the task via the ",[464,595,557],{}," mutation (the same mutation you can call from the Convex dashboard, a script, or your own tooling). The description needs at least 10 characters. The lifecycle below applies regardless of how the task was filed.",[448,598,599,600,603,604,606,607,610,611,614,615,618,619,622],{},"To cancel, open the Code Tasks dashboard and use the ",[452,601,602],{},"Cancel"," button on a task card. The dashboard's Cancel button only appears on ",[452,605,582],{}," or ",[452,608,609],{},"running"," tasks, but the underlying ",[464,612,613],{},"codeWorkTasks.cancel"," mutation rejects only ",[452,616,617],{},"merged"," tasks — testing and review tasks are still cancellable via the backend. Cancelling marks the task ",[452,620,621],{},"failed"," with the message \"Cancelled by user\" — there is no separate \"cancelled\" stage.",[480,624,626],{"id":625},"task-lifecycle-and-the-prtestcost-surface","Task lifecycle and the PR\u002Ftest\u002Fcost surface",[448,628,629],{},"A task moves through a fixed set of stages. The code-worker advances it as it works and the dashboard reflects each transition in real time.",[631,632,633,649],"table",{},[634,635,636],"thead",{},[637,638,639,643,646],"tr",{},[640,641,642],"th",{},"Stage",[640,644,645],{},"Badge",[640,647,648],{},"What it means",[650,651,652,665,677,690,703,715],"tbody",{},[637,653,654,659,662],{},[655,656,657],"td",{},[464,658,582],{},[655,660,661],{},"Queued",[655,663,664],{},"Filed and waiting for the code-worker to claim it.",[637,666,667,671,674],{},[655,668,669],{},[464,670,609],{},[655,672,673],{},"Running (pulsing)",[655,675,676],{},"The worker has claimed the task, set up a branch, and is running the coding agent.",[637,678,679,684,687],{},[655,680,681],{},[464,682,683],{},"testing",[655,685,686],{},"Testing",[655,688,689],{},"The change is committed; the worker is running the test suite.",[637,691,692,697,700],{},[655,693,694],{},[464,695,696],{},"review",[655,698,699],{},"Review",[655,701,702],{},"A pull request has been opened. The change is ready for a human to review and merge.",[637,704,705,709,712],{},[655,706,707],{},[464,708,617],{},[655,710,711],{},"Merged",[655,713,714],{},"The pull request was merged.",[637,716,717,721,724],{},[655,718,719],{},[464,720,621],{},[655,722,723],{},"Failed",[655,725,726],{},"The task failed, was cancelled, or produced no changes. The error is shown on the card.",[448,728,729],{},"Each task card surfaces the work product as it becomes available:",[631,731,732,742],{},[634,733,734],{},[637,735,736,739],{},[640,737,738],{},"Field",[640,740,741],{},"When it appears",[650,743,744,757,767,777,787,813],{},[637,745,746,751],{},[655,747,748],{},[452,749,750],{},"Branch",[655,752,753,754,478],{},"Once the worker creates the feature branch (named ",[464,755,756],{},"code-worker\u002F\u003Ctask-id>",[637,758,759,764],{},[655,760,761],{},[452,762,763],{},"Pull request",[655,765,766],{},"A clickable link to the PR, once the worker opens one.",[637,768,769,774],{},[655,770,771],{},[452,772,773],{},"Test results",[655,775,776],{},"A tail of the test-runner output captured during the testing stage.",[637,778,779,784],{},[655,780,781],{},[452,782,783],{},"Error",[655,785,786],{},"On failed tasks only — the reason the task stopped.",[637,788,789,794],{},[655,790,791],{},[452,792,793],{},"Cost",[655,795,796,797,800,801,804,805,808,809,812],{},"The LLM spend for the run, shown to four decimal places (e.g. ",[464,798,799],{},"$0.0123","). The field exists in the schema and UI, but the code-worker does not currently report ",[464,802,803],{},"llmCost"," (it is never sent on ",[464,806,807],{},"completeWithPR","\u002F",[464,810,811],{},"markFailed","), so in practice Cost stays empty for worker-run tasks.",[637,814,815,820],{},[655,816,817],{},[452,818,819],{},"Created",[655,821,822],{},"A relative timestamp (\"just now\", \"12m ago\", \"3d ago\").",[537,824,826],{"title":825,"type":540},"Reaching the merged stage",[448,827,828,829,831,832,834,835,838,839,842,843,845,846,849],{},"The worker opens the pull request and moves the task to ",[452,830,696],{},". To advance it to ",[452,833,617],{}," automatically, configure a GitHub webhook pointed at ",[464,836,837],{},"POST \u002Fwebhooks\u002Fgithub"," with the secret ",[464,840,841],{},"GITHUB_WEBHOOK_SECRET",". When the PR is merged, GitHub notifies Owlat and the task moves to ",[452,844,617],{}," via ",[464,847,848],{},"markMergedByPrUrl",". The merged stage is reachable in production — review is not terminal.",[480,851,853],{"id":852},"setup-the-code-worker-service-and-its-environment","Setup: the code-worker service and its environment",[448,855,856,857,860,861,863,864,866],{},"The code-worker ships as a Docker sidecar. In the bundled Compose stack it runs under the ",[464,858,859],{},"inbox-codetasks"," profile, which the ",[464,862,507],{}," feature flag turns on. It connects to your Owlat deployment over the Convex client, polls for the next ",[464,865,582],{}," task (every 10 seconds by default), and processes one task at a time.",[537,868,871],{"title":869,"type":870},"VPS Compose template omits CONVEX_ADMIN_KEY","warning",[448,872,873,874,876,877,473,880,883,884,887,888,887,891,887,894,887,897,887,899,901,902,905,906,909,910,912,913,915,916,919,920,561],{},"The worker authenticates with the deployment admin key (",[464,875,466],{},"), exactly like the ",[464,878,879],{},"imap",[464,881,882],{},"mail-sync"," sidecars, which lets it call the internal queries and mutations it drives the task with (",[464,885,886],{},"getNextQueued",", ",[464,889,890],{},"claim",[464,892,893],{},"updateBranch",[464,895,896],{},"markTesting",[464,898,807],{},[464,900,811],{},"). The dev Compose stack supplies this var, but the bundled ",[452,903,904],{},"VPS"," Compose template currently does ",[452,907,908],{},"not"," pass ",[464,911,466],{}," to the ",[464,914,454],{}," service block — so on a stock VPS deploy the worker throws ",[464,917,918],{},"CONVEX_ADMIN_KEY environment variable is required"," at startup until you add it. See ",[469,921,477],{"href":476},[448,923,924],{},"For each claimed task the worker:",[926,927,928,933,939,943,949,953,958,962,972,976],"steps",{},[929,930,932],"h3",{"id":931},"claim-the-task","Claim the task",[448,934,935,936,938],{},"It atomically claims the oldest queued task, moving it to ",[452,937,609],{}," so no other poll picks it up.",[929,940,942],{"id":941},"set-up-a-workspace-and-branch","Set up a workspace and branch",[448,944,945,946,948],{},"It clones your repository (shallow, on the base branch) into a per-task workspace and checks out a new ",[464,947,756],{}," branch.",[929,950,952],{"id":951},"run-the-coding-agent","Run the coding agent",[448,954,955,956,561],{},"It runs the coding agent (OpenCode by default) with your task description as the prompt, with a 10-minute timeout. If the agent fails or produces no file changes, the task is marked ",[452,957,621],{},[929,959,961],{"id":960},"commit-and-test","Commit and test",[448,963,964,965,967,968,971],{},"It commits the changes, moves the task to ",[452,966,683],{},", and runs the test suite (",[464,969,970],{},"vitest",") with a 5-minute timeout, capturing the output tail.",[929,973,975],{"id":974},"push-and-open-a-pr","Push and open a PR",[448,977,978,979,981],{},"It pushes the branch and — when GitHub credentials are configured — opens a pull request whose body includes your description and the test summary. The task moves to ",[452,980,696],{}," with the PR URL, test results, and cost attached.",[448,983,984],{},"The container reads its configuration from environment variables:",[631,986,987,997],{},[634,988,989],{},[637,990,991,994],{},[640,992,993],{},"Variable",[640,995,996],{},"Purpose",[650,998,999,1009,1018,1028,1041,1051,1065,1078,1095,1108,1118],{},[637,1000,1001,1006],{},[655,1002,1003],{},[464,1004,1005],{},"CONVEX_URL",[655,1007,1008],{},"The Owlat backend the worker polls and reports to. Required.",[637,1010,1011,1015],{},[655,1012,1013],{},[464,1014,466],{},[655,1016,1017],{},"Deployment admin key the worker authenticates with to call the internal queue queries and mutations. Required — the worker throws at startup if it is unset.",[637,1019,1020,1025],{},[655,1021,1022],{},[464,1023,1024],{},"GIT_REPO_URL",[655,1026,1027],{},"The clone URL of the repository the agent works in.",[637,1029,1030,1035],{},[655,1031,1032],{},[464,1033,1034],{},"GIT_BASE_BRANCH",[655,1036,1037,1038,478],{},"Branch to clone and target the PR against (defaults to ",[464,1039,1040],{},"main",[637,1042,1043,1048],{},[655,1044,1045],{},[464,1046,1047],{},"GITHUB_TOKEN",[655,1049,1050],{},"GitHub token used to open the pull request.",[637,1052,1053,1062],{},[655,1054,1055,1058,1059],{},[464,1056,1057],{},"GITHUB_OWNER"," \u002F ",[464,1060,1061],{},"GITHUB_REPO",[655,1063,1064],{},"The repo the PR is opened against. If both are unset, the worker pushes the branch but skips PR creation.",[637,1066,1067,1075],{},[655,1068,1069,1058,1072],{},[464,1070,1071],{},"LLM_BASE_URL",[464,1073,1074],{},"LLM_API_KEY",[655,1076,1077],{},"LLM configuration for the coding agent. These are the only two LLM vars the worker child actually reads.",[637,1079,1080,1088],{},[655,1081,1082,1058,1085],{},[464,1083,1084],{},"LLM_PROVIDER",[464,1086,1087],{},"LLM_MODEL",[655,1089,1090,1091,1094],{},"Passed through Compose env for convenience, but ",[452,1092,1093],{},"not read"," by the worker itself.",[637,1096,1097,1102],{},[655,1098,1099],{},[464,1100,1101],{},"OPENCODE_BIN",[655,1103,1104,1105,478],{},"Path to the OpenCode binary (defaults to ",[464,1106,1107],{},"opencode",[637,1109,1110,1115],{},[655,1111,1112],{},[464,1113,1114],{},"POLL_INTERVAL_MS",[655,1116,1117],{},"How often to poll for queued tasks (defaults to 10000).",[637,1119,1120,1125],{},[655,1121,1122],{},[464,1123,1124],{},"WORKSPACE_ROOT",[655,1126,1127,1128,478],{},"Where per-task clones live inside the container (defaults to ",[464,1129,1130],{},"\u002Fworkspace",[537,1132,1135],{"title":1133,"type":1134},"The worker has write access to your repo","danger",[448,1136,1137,1138,1140,1141,1143],{},"The code-worker clones, commits, pushes, and opens pull requests with the credentials you give it, and runs an autonomous coding agent against your codebase. Scope ",[464,1139,1047],{}," to a single repository, point ",[464,1142,1034],{}," at a branch you protect with required reviews, and treat every generated pull request as untrusted until you've read it.",[448,1145,1146,1147,1149,1150,473,1152,561],{},"For where these variables live in the deployment and how to enable the ",[464,1148,859],{}," profile, see ",[469,1151,294],{"href":293},[469,1153,70],{"href":69},[480,1155,477],{"id":1156},"current-limitations",[448,1158,1159],{},"Code Tasks is an early feature. Keep these in mind:",[1161,1162,1163,1177,1186,1192],"ul",{},[1164,1165,1166,1171,1172,912,1174,1176],"li",{},[452,1167,1168,1169,561],{},"The VPS Compose template omits ",[464,1170,466],{}," The worker authenticates with the deployment admin key, but the bundled VPS Compose template does not yet pass ",[464,1173,466],{},[464,1175,454],{}," service, so on a stock VPS deploy the worker won't start until you add that var.",[1164,1178,1179,1182,1183,1185],{},[452,1180,1181],{},"Cost is not reported."," The code-worker never sends ",[464,1184,803],{},", so the Cost field stays empty for worker-run tasks even though the schema and UI support it.",[1164,1187,1188,1191],{},[452,1189,1190],{},"One task at a time, in order."," The worker processes the oldest queued task per poll; there's no parallelism or prioritisation.",[1164,1193,1194,1197],{},[452,1195,1196],{},"No automatic retry."," A failed task stays failed. File a new task to try again.",[448,1199,1200,1201,1203,1204,561],{},"For the broader picture of how Owlat's agent handles inbound conversations and drafts, see ",[469,1202,102],{"href":101}," and the ",[469,1205,94],{"href":93},{"title":1207,"searchDepth":1208,"depth":1208,"links":1209},"",2,[1210,1211,1212,1213,1221],{"id":482,"depth":1208,"text":483},{"id":564,"depth":1208,"text":565},{"id":625,"depth":1208,"text":626},{"id":852,"depth":1208,"text":853,"children":1214},[1215,1217,1218,1219,1220],{"id":931,"depth":1216,"text":932},3,{"id":941,"depth":1216,"text":942},{"id":951,"depth":1216,"text":952},{"id":960,"depth":1216,"text":961},{"id":974,"depth":1216,"text":975},{"id":1156,"depth":1208,"text":477},"md",{},true,{"title":118,"description":119},"1.guide\u002F34.code-tasks","yQRt8dUuNBsZTz9uWJEKjoceTczyIjuaHvbUO5NrlA0",[1229,1231],{"title":114,"path":113,"stem":1230,"children":-1},"1.guide\u002F33.chat",{"title":122,"path":121,"stem":1232,"children":-1},"1.guide\u002F35.audience-data",1782846430772]