DevDaily VS Code Extension (Sprint 1)
Captures development activity locally — without requiring git add or
git commit — and queues it for upload to the DevDaily backend.
This is the Sprint 1 slice of the roadmap in the product PRD: extension
setup, login, workspace detection, file save/create/delete/rename
detection, and a local activity queue. The backend API it talks to
(/api/v1/devices/register, /api/v1/activity, /api/v1/activity/today)
is Sprint 2 and is not implemented yet — until then, login and sync will
fail against whatever devdaily.serverUrl points to.
What it does
- Detects each opened workspace folder as a project (
PROJECT_OPEN),
reading .git/HEAD and .git/config directly for branch/remote info
when present — no git CLI dependency.
- Tracks
FILE_OPEN, FILE_SAVE, FILE_CREATE, FILE_DELETE, and
FILE_RENAME for files inside tracked workspace folders, skipping
anything matching devdaily.excludePatterns (env files, keys,
node_modules, build output, etc).
- Buffers events in memory and on disk (
globalStorageUri), flushing
them to the server on a timer (devdaily.batchIntervalSeconds) with
exponential backoff on failure — nothing is lost if you're offline or
the server is down.
- Stores the device token via VS Code
SecretStorage, not plain
settings.
Commands
| Command |
Description |
DevDaily: Log In |
Prompts for email/password, registers this device, stores the token |
DevDaily: Log Out |
Clears the stored device token |
DevDaily: Sync Activity Now |
Forces an immediate queue flush |
DevDaily: Show Today's Activity |
Shows account, queue size, last activity time |
Settings
See devdaily.* in package.json — server URL, batch interval, idle
threshold (reserved for the Sprint 3 session engine), exclude patterns,
and whether to track only files inside open workspace folders.
Development
npm install
npm run watch # esbuild in watch mode
Then press F5 in VS Code (uses .vscode/launch.json) to launch an
Extension Development Host.
npm run compile # type-check only
npm run lint
npm run package # produces a .vsix via vsce
Not in this slice
Session/idle detection (Sprint 3), git status/diff/commit collection
(Sprint 4), and the backend + AI report generation (Sprints 2, 5+) are
out of scope here. The event shapes in src/types.ts already match the
API contracts in the PRD so the backend can be built against them
directly.
