Five surfaces. Plus everything underneath.
Top-level navigation is what a human actually thinks about: work, procedures, triggers, context, scopes. Agents, builder, packs and integrations live inside the issues that need them.
The work, in one keyboard-driven list.
Dense rows. Status icons that scan in a glance. Quick filters for Open, Needs review, Needs attention, Done, Scheduled. Open any issue to see properties, activity, attached workflow runs.
Procedures, written once. Re-attached to every issue.
Each step persists its result. The process can sleep for hours, wait for human approval, invoke sub-workflows, and survive every restart. Compose business logic the same way you write any TypeScript.
step.run(name, fn)Execute & persist. Safe to retry.step.sleep(name, '14d')Pause hours, days, weeks.step.waitForEvent('approval')Block until a signal arrives.step.invoke('sub-flow', input)Compose workflows.ctx.collections.*Read & write any QUESTPIE collection.agent.run(capability, input)Hand off to a configured capability.workflow_configs as steps + defaults. Attach one to any issue, or trigger via Schedules.Time triggers that produce real work.
A schedule either creates an issue with a template, or runs a workflow directly. Pick cron, pick a workflow, decide what happens on overlap. The product surface stays human.
Knowledge
Context, docs, brand rules, references. Indexed for semantic search. Workflows and agents query knowledge before they decide.
3 results · pricing-style.md · landing-copy-v2.md · brand-voice.md
Projects
Workspaces, repos, scopes. Each project has its own issues, workflows, schedules and defaults. Multi-tenant by design.
Like Lovable, but it edits real QUESTPIE code.
Describe a change and the builder modifies collections, admin views, routes, components and content as a real commit. Live preview, human approval, full audit. Hosted on Cloud or self-hosted.
Where your team already talks. Where your code already lives.
Autopilot connects to the channels your humans use and the systems your code runs in. Issues, approvals, digests, deploys. Flow through Slack, GitHub, email and MCP.
Business capability, installable in one command.
A pack bundles skills, workflows, schedules, MCP tools and knowledge seeds into a single installable unit. Drop one in, get a working capability. Share with your team or the community.
$ autopilot pack install @questpie/pack-marketing-contentregistry · @questpie / public · private soonAgents your data trusts. Models you choose.
An agent is a profile: capability, allowed tools, MCP scope. Point it at a provider. Anthropic, OpenAI, local. And let it work through the same RBAC rules that apply to your humans.
Same RBAC as humans. Annotated routes auto-discovered as tools. Schemas and OpenAPI shipped as MCP resources, so agents know your data model without you wiring prompts.
A terminal cockpit, in the same package.
The same product, operated from your terminal. Open in any repo, inspect runs, steer sessions, retry failed steps. Keyboard-first, session-scoped. Ships with the Autopilot package.
$ autopilotopen the TUI in the current workspace$ autopilot statushealth, current run, ready tasks$ autopilot run-task QAP-246execute one issue in a fresh session$ autopilot logs --followcondensed session log, conversation mode$ autopilot retry QAP-238re-run a failed task with remediation$ autopilot note QAP-246 'focus only on HookContext'persistent steering for the next stepSelf-host the open package. Or run hosted on Cloud.
Autopilot is MIT. Self-host as long as you like. Workflows are TypeScript, schemas are Drizzle, everything stays in git. When you outgrow one machine, point Cloud at the same project. Hosted Autopilot inherits all of it: same code, same data, plus managed runtime and the Cloud deploy bridge.