Savyre VS Code Extension
Candidate sign-in for Savyre assessments (email + assessment code). Uses the Savyre API only — no local database.
Prerequisites
Setup
cd savyre-extension
npm install
npm run compile
Press F5 to open Extension Development Host.
Set Savyre: Api Base Url in settings if needed (default https://app.savyre.com; local dev: http://localhost:5000).
Sign in
Open the Savyre icon in the activity bar.
Enter email and assessment code from your invite email.
Click Sign in.
After sign-in, the extension clones and opens the assessment repo when repoUrl is configured (savyre.autoCloneRepo, default on).
Read Task & instructions and the Recommended workflow in the panel.
Click Start assessment when ready.
Stay in VS Code while working — time outside the IDE is tracked (min/sec) after you click Start assessment.
Candidate workflow (instructions in panel)
The Savyre sidebar shows overview, recommended AI-assisted workflow steps, allowed tools, and evaluation rules.
When you Start assessment, the extension creates a hidden .savyre/ folder in the cloned repo (de-emphasized in the file tree) for:
file-changes.jsonl — telemetry of manual vs assistant file savesai-session-log.md — AI should append chat and ## Assistant (files) blocks hereSAVYRE_INSTRUCTIONS.md — candidate-facing transparency + workflow expectationsSAVYRE_LOG.md — human-readable assessment activity timelineAGENTS.md — workflow rules for any coding agent.cursor/rules/savyre-ai-workflow.mdc — Cursor-specific workflow rules.savyre/manifest.json — generated/protected/required file manifest used for submit-time evidence checks.savyre/events.jsonl — machine-readable chronological session events.savyre/file-hashes.json — integrity hashes for protected assessment scaffolding files.savyre/diffs/ — diff snapshots, including final-diff.patch generated near submit.savyre/snapshots/ — milestone JSON snapshots (session start and submit)savyre/stages/01-task-input/ through savyre/stages/13-final-summary-ai-reflection/ — 13 workflow stages (input.md, summary.md, metadata.json each), scaffolded on start and required before submitsavyre/ai-interactions.md — structured AI interaction log template.savyre/session.json, .savyre/stage-status.json, .savyre/submission.json, .savyre/terminal-events.jsonl — session state, workflow progress, submit package, terminal command capture
On Submit assessment, the extension uploads the full contents of .savyre/ and .cursor/ text artifacts (logs, diffs, rules) to the server as workflow.telemetryFiles.
Session baseline (Option A): On Start assessment, a full copy of source + scaffold files is saved under .savyre/baseline/ and uploaded as workflow.baselineFiles so employers can compare before (session start) vs after (submit). Each save in file-changes.jsonl includes prevHash, newHash, optional diff, and revertedToBaseline when content matches the baseline again.
Periodic git diffs (Option B): Every savyre.periodicDiffIntervalMinutes (default 5), plus at session start and pre-submit, the extension writes numbered patches .savyre/diffs/diff-0001.patch, diff-0002.patch, … (git diff vs branch HEAD).
Command: Savyre: Open File Change Log (after starting).
Requires Git installed and on your PATH.
If clone fails on a private repo, sign in to GitHub in Cursor or run gh auth login, then retry Clone repository.
API (Savyre server)
| Method | Path |
|--------|------|
| POST | /api/extension/session/bootstrap |
| GET | /api/extension/session |
| POST | /api/extension/session/start |
Package
npm run package
Produces savyre-extension-0.1.6.vsix.
Publish update (Marketplace)
npm run publish:marketplace
Requires npx @vscode/vsce login AuryonInnovations with a Marketplace Manage PAT if not already logged in.
Privacy and data collection
Savyre is designed around session-based transparency during an active assessment.
When you sign in and Start assessment, the extension may capture workflow signals such as:
- File change metadata and diffs
- Terminal command events and test activity
- AI session log entries you or your assistant append
- Session status, timestamps, and workflow summaries
- Screen monitoring when enabled for your assessment
These signals are uploaded to the Savyre API configured in savyre.apiBaseUrl when you submit or as configured by your employer. The extension is not intended to monitor activity outside an active assessment session.
Savyre is designed not to intentionally collect secrets, API keys, or unrelated personal files. Default exclusions include patterns such as .env, *.pem, *.key, and credentials.json.
For more information, see https://savyre.com.
