Extension
Commands, settings, local workspaces, and local-first behavior.
Commands
| Command | What it does |
|---|---|
| Shiplogue: Generate Today's Update | Gathers activity for the active project and writes a draft. |
| Shiplogue: Generate Weekly Recap Now | Compiles the stored daily drafts immediately; the scheduled recap runs automatically. |
| Shiplogue: Connect Cloud | Validates and stores a connector key in SecretStorage. |
| Shiplogue: Cloud Status | Shows the connected workspace, plan, and scopes. |
| Shiplogue: Disconnect Cloud | Removes the connector key. Local generation still works. |
| Shiplogue: Set API Key | Stores a BYOK provider key in SecretStorage. |
| Shiplogue: Set Reminder Time | Sets the local daily reminder. |
| Shiplogue: Configure Keyboard Shortcut | Opens the editor's keybinding UI. |
The generation panel opens with Cmd+Shift+' / Ctrl+Shift+'.
Every Friday at 18:00 local, Shiplogue compiles the stored daily drafts into a
weekly recap, adds it to draft history, and shows a notification. It is static:
it does not rescan commits, files, prompts, or the network. Change the schedule
with shiplogue.weeklyRecap.day and shiplogue.weeklyRecap.time. Each synced
summary records its IDE/agent source tags, including every source used in a
multi-source summary.
Local workspaces
Each project or repo folder is its own local workspace. Generating in a project only uses activity and prompts scoped to that project, and the cloud dashboard keeps the project name on the synced draft. You can keep as many local workspaces as you work in; cloud workspace limits are separate.
Cloud settings
| Setting | Default | Purpose |
|---|---|---|
shiplogue.cloud.url | https://shiplogue.dev | Cloud origin. Use http://localhost:3000 for local development. |
shiplogue.cloud.enabled | true | Turn off to keep drafts local even with a key connected. |
shiplogue.cloud.estimatedMinutesSaved | 10 | Estimate recorded with each synced draft; 0 reports none. |
shiplogue.telemetry.enabled | false | Opt in to anonymous usage metadata. Never includes draft text, prompts, paths, repositories, or error messages. |
shiplogue.weeklyRecap.enabled | true | Automatically compile the weekly recap. |
shiplogue.weeklyRecap.day | friday | Day for the automatic recap. |
shiplogue.weeklyRecap.time | 18:00 | Local time for the automatic recap. |
Send and history
Send uses the workspace's Delivery targets configured in the dashboard. The
extension queues a cloud delivery, polls for the result, and marks the draft sent
only after the target reports success. If the cloud returns 402, the extension
shows the Pro upgrade prompt instead of a generic failure.
Pro users page cloud history directly in the History tab. Each cloud entry includes its source tags, local project, and sent/scheduled metadata; free users keep the local history window.
Local-first defaults
- IDE activity is stored on your machine, not uploaded as raw events.
- Provider keys and connector keys live in the OS keychain through SecretStorage.
.env, credential files, keys,.ssh, and.gitignored paths are filtered before storage.- Cloud sync is inactive until a connector key is connected.
- Stand-up content sent to the cloud is limited to the final draft in 0.1.9.
- Telemetry requires a connector key and explicit opt-in; it sends metadata only.
Supported platforms today
VS Code, Cursor, and Antigravity are available now. Zed, JetBrains, PyCharm, WebStorm, GoLand, Eclipse, Kiro, VSCodium, Trae, Positron, and other editors are coming soon; they require separate adapters and are not included in the current VSIX.