Create a Draft Work Memory yourself
Begin from a project, existing notes, a performance review, or a résumé bullet. No Git connection is required.
How it works
Create, review, and approve a Work Memory.
Start manually or use the optional Desktop Companion. Every path ends with your review and approval.
Two ways to begin
Start with what you know or let selected Git activity remind you.
Git is an optional starting point. It does not write the meaning of your work and no repository is connected automatically.
Let selected commits create a reminder
The Desktop Companion can turn safe metadata from repositories you choose into a Draft Work Memory while context is fresh.
Review a Draft Work Memory
A manual note or selected Git reminder begins on your device. Git reminders use titles, dates, file types, and change totals, never source code.
Add what only you know
Capture the problem, constraints, decisions, contribution, outcome, and impact while the context is still available.
Approve the Work Memory
Remove anything sensitive and approve only the professional experience you want to remember and reuse later.
Selected sync only
A Draft Work Memory starts locally.
Only a Draft Work Memory you select can sync to the private web app. It still needs your review before approval.
Nothing syncs automatically or becomes public by itself.
Always stays on your device
- Source files
- Diff contents
- Credentials and secrets
- Repository remote URLs
- Environment files
- Full repository path
Included in a selected sync
- Safe repository alias
- Draft Work Memory title and summary
- Commit titles
- Date range
- Files, insertions, and deletions
- File type counts
Local capture levels
Choose how much context stays on your computer.
Local detail and selected sync are separate decisions.
Minimal capture
- Commit title and date
- File type counts
- Files, insertions, and deletions
- Hashed branch and author identifiers
Standard local capture
- Commit body
- Branch name
- Changed file paths
- Ticket identifiers
These additions stay local unless a safe field is explicitly included in a selected sync.
Capture questions
Technical details without guesswork.
See the privacy page for the complete boundary.
Does Verxyon scan every repository?
No. The Desktop Companion works only with repositories you explicitly enable. You can disable capture later.
What does minimal Git capture use?
The default local capture can use the commit title and date, file type counts, change totals, and hashed branch and author identifiers.
What can standard local capture add?
Standard capture can also keep the commit body, branch name, changed file paths, and ticket identifiers on your device. Those local details are not automatically included in a selected sync.
Can a Work Memory become public automatically?
No. A selected sync creates a private Draft Work Memory that still needs your review. Reuse or sharing is a separate decision after approval.
Early access
Build your first Work Memory with us.
Help shape the capture and review experience before the Desktop Companion beta opens.
Join early access