Quickstart

This walks you through the path from signup to your first working agent. Allow about five minutes.

1. Sign in

Open app.project88.io and create an account with email + password. On signup we auto-create:

• A profile (linked to your Supabase auth user)
• A personal organization (you're the owner)
• A Home canvas inside that org

You land directly on /:orgSlug — your org's Home canvas. There's no intermediate lobby and no workspace selector.

If you arrived via an invite link, signup auto-accepts the invite, prefills the invitee's email on the form, and lands you on the inviting org instead of your personal org — no manual switch needed.

2. Add a provider API key

Hit ⌘K and open Settings → Providers (or the gear icon in the breadcrumb). Add at least one provider key:

Keys are validated client-side for the right prefix, then encrypted into Supabase Vault server-side. The plaintext key is never stored in the provider_keys table — only a vault_secret_id reference. The browser never sees the decrypted value; chat completions are proxied through the chat-proxy Edge Function, which fetches the key from Vault at request time.

3. Create your first Assistant

⌘K → Agents, then + New agent. The wizard has three steps:

1. Type — pick Assistant (conversational, no pipeline).
2. Template — pick Blank to start from scratch, or one of the prebuilt templates: Support Agent, Code Reviewer, Phone Agent, Outreach Agent, Orchestrator.
3. Details — name, model, and system prompt.

Click Create and you'll be dropped into the agent's detail view (General / Config / Tools tabs). At this point the agent is ready to chat with.

4. Chat with it

Press ⌘K → Chat (or click the Chat icon in the home dock). In the chat input:

• The model selector is populated from your active provider keys.
• The agent selector lets you pick the Assistant you just created.
• The paperclip / drag-and-drop / clipboard paste all upload to the chat-attachments Supabase Storage bucket.

Type a message and hit Enter. The conversation streams in real-time. Tool calls (if any) appear as collapsible blocks above the assistant's reply.

5. The command palette

Hit ⌘K anywhere. The global command palette is more than a navigation menu — it searches across every kind of content in your org:

• Calendar events
• Pages
• Conversations
• Agents
• Record activities (calls, emails, meetings, tasks, notes)
• Data tables
• Data table rows

Search is debounced (~150 ms) and aggregates results server-side via the global_search RPC, grouped by kind. Pick a result with arrow keys + Enter and you're there. Calendar events go a step further: picking one opens its EventDetailSheet directly on top of the current canvas via the ?event=<id> query param, so you don't have to navigate into the Calendar app first.

Two behaviours worth knowing:

• Phone lookups match by canonical digits, not stored format. A row stored (910) 620-0001 is found by any of 9106200001, +19106200001, or (910) 620-0001, and the palette's phone search agrees with the table's own search box on which rows exist. The SQL and JS normalizers are twins pinned by a shared fixture file (lib/phoneSearch.fixtures.js) — see Data tables → phone search.
• The palette is org-wide. It no longer scopes to a legacy workspaces row, so pages, tables, and rows an org owns are visible to search whether they were created before or after workspaces were removed from the product.

6. Where to go next

• Connect an integration. Settings → Connections → browse 900+ Composio toolkits (Gmail, Calendar, Slack, GitHub, Outlook, and more). The agent picks up connected tools automatically. See Integrations.
• Upgrade to an Agent. When you need deterministic steps, go to your Assistant's Config tab and click Upgrade to Agent. A new Flow tab appears where you draw the pipeline. See Building Agents.
• Build an Automation. Trigger an agent on a schedule, a webhook, or from a sub-agent. See Automations.
• Plug a Project88 MCP token into Claude Code, Claude Desktop, or Cursor. Thirty read-only tools across tables, calendar, dial, inbox, pages, and templates — scoped to your own permissions in the org. See MCP.