Pilot

Shipped

Pilot, your AI assistant, lives in the left sidecar of every page in your Turbobase app. Open it from the rail toggle or with ⌘/Ctrl+K, or use the full-page view at /chat. The pilot-chat setting decides whether Pilot appears in the web app, and it is off by default: until an administrator turns it on, the whole chat surface stays hidden. Asking Pilot from Slack works either way, as long as you have linked your account.

Pilot reads and writes through the same surfaces your apps do — the PostgREST API and the write boundary — so your role and permissions apply to everything it does. There is no privileged back door.

What you can ask

Look things up. “Show me open invoices”, “count customers added this month”, “find past-due sales orders.” Pilot queries the canonical data model directly, and picks up per-intent recipes (curated column lists, stats, and row actions) for common views. It can also open a record or page for you — “open customer 42” navigates there.

Ask how your business does things. Pilot searches your knowledge base (published pages only) for questions like “what’s our approval limit” or “how do we handle returns”, and can recall from semantic memory — ingested meeting transcripts, chat history, email, and documents — for “what did the customer say about X.”

Check on the system. “Is sync healthy?”, “what’s broken?”, “how many records do we have?” Pilot summarizes sync health, record counts per source, and recent sync failures, and reads configured settings. Ask “what can you do” for its own capability list.

Schedule recurring work. “Every Monday at 9am, send me open sales orders.” Pilot turns natural-language schedules into a scheduled task that re-runs a chat prompt on a timer, delivered in-app or to a bound channel (Slack).

Writes are always staged

Pilot never mutates data on its own say-so. When you ask it to create or update a record, it builds a write proposal — a card in the chat showing exactly what would change, with Confirm and Cancel buttons. Nothing happens until you click Confirm; only then does the write run through the same write boundary every app uses, with row-level security and hooks enforced. If the originating source rejects the write, you see it as a sync failure rather than a silent drop.

The same staged-confirm pattern covers configuration:

• Add records to the sync — “also sync customrecord_widget”, “pull phone calls.” Pilot proposes the subscription; custom tables and custom lists additionally wait for an admin to approve the pending row on the Data → Records page before anything is created.
• Sync more custom fields — “also sync the PO number field on sales orders.” Same flow: a pending proposal you confirm, then admin approval before the columns are added and backfilled.
• Stage guardrail rules — “block fulfillments over $10,000.” Pilot translates the intent into a structured rule and stages it as proposed; it is not enforced until an admin activates it on the Guardrails page. Pilot can only add new rules — editing, activating, or deleting existing ones happens on that page.

Skills and MCP servers

Administrators tune what Pilot knows at /admin/skills, which manages two things:

• Skills — markdown instruction packs that shape how Pilot approaches specific tasks. They come from three sources: bundled seeds that ship with Turbobase (read-only, with “Fork to edit” to copy one into your own editable set), admin-authored skills you write yourself, and registry imports from agentskills.io or skillsmp.com, which you can disable, fork to edit, or pin to a version. Each skill can target the whole instance or a specific role. Connector-owned skills for your connected sources appear in the same list automatically and are read-only.
• MCP servers — an admin-managed list of remote MCP endpoints. Today Pilot surfaces them as reference resources in its context; runtime tool-calling against them is not yet wired in.

Related

• Data model — the canonical tables Pilot queries and writes
• Guardrails — where staged guardrail rules are activated
• Knowledge base — the pages behind “how do we do X” answers
• Agent skills — the standing rules Pilot applies on every turn
• Channels — deliver scheduled tasks to Slack