Cloud workspace
The dashboard, accounts, connector keys, and synced data.
Local projects vs cloud workspaces
A local workspace is a project or repo folder in your editor. It is unlimited and never needs an account. A cloud workspace is the private Shiplogue team your synced drafts belong to. Free includes one cloud workspace; additional cloud workspaces are planned for Pro.
The extension sends the local project name with each draft so multiple projects can share one cloud workspace without their summaries being merged. It also sends the IDE/agent source tags and structured coverage counts (no file paths or contents). The dashboard shows a Projects list, connected Sources, and a coverage strip plus the English draft inside each summary accordion.
Sign in and workspace
The dashboard is server-rendered and requires a Better Auth session. On first sign-in Shiplogue creates a personal cloud workspace.
Two gates protect the dashboard:
- A valid session.
- At least one active connector key.
If either is missing, the dashboard redirects to sign-in or onboarding.
Connector keys
Create one named key per supported platform, editor, or machine. The full key is shown once; only a SHA-256 hash, prefix, and last four characters are stored.
Keys can be revoked independently. Revoking the last active key sends the workspace back to onboarding on the next dashboard request.
Send the key as a Bearer token:
Authorization: Bearer shp_live_...Cloud data
The Postgres schema stores:
- users, sessions, and cloud workspaces
- connector keys
- opt-in activity events
- stand-ups, local project names, and delivery records
- integrations, subscriptions, and usage events
The current extension syncs finished drafts only. The events API is ready for opt-in redacted activity metadata, but the extension does not send raw activity yet. Product telemetry is a separate opt-in and contains metadata only.
Delivery targets
Connect Slack, Microsoft Teams, or Discord webhooks from Dashboard → Delivery.
The webhook URL is encrypted at rest and never returned to the extension. A
standups:send connector scope is required to queue a send.
Sends are queued as delivery batches and polled by the extension. Pro history
returns the final sent targets, so scheduled/cloud sends show as Sent in the
extension's History tab.
Dashboard metrics
The dashboard reads real database aggregates:
- stand-ups generated
- updates delivered
- estimated time reclaimed
- activity events and source count
There is no seeded dashboard content. Empty states are real empty states.
Plan limits
- Free: one cloud workspace, daily and weekly summaries, copy to clipboard.
- Pro (coming soon): unlimited cloud workspaces, all supported platform connections, 30/60/90-day history, and scheduled Slack/Teams/Discord delivery.
Billing
Pro is billed through Polar. The dashboard opens Polar checkout and the Polar customer portal; Shiplogue never receives card details. Subscription webhooks update the workspace plan, and Pro features are enforced server-side.