DevClarity 2.7.3 — Your Coding Companion
DevClarity turns your everyday VS Code work into clear, helpful summaries — so you can focus on building, and let your activity feed write itself.
What DevClarity does for you
- Automatic activity summaries. When you finish a focused coding session, DevClarity gives you a short, friendly recap of what you worked on — refactors, fixes, experiments — without you typing a single status update.
- Deep-work recognition. It quietly notices when you're in flow and highlights those sessions, so you and your team can see when your best work happens.
- Always-on, never in the way. Your OneClarity dashboard stays up to date in the background. No popups, no nagging, no setup after the first sign-in.
- Offline-friendly. Lose connectivity? Your activity is saved locally and syncs the moment you're back online. Nothing is lost.
New in 2.7.3 — GitHub Copilot on modern VS Code
Recent VS Code versions changed where they keep Copilot chat: the conversation text now lives in separate chatSessions/*.jsonl transcript files on disk, while the internal database holds only a list of session IDs. The previous extractor looked only in the database and so found nothing on these installs. That's fixed.
- File-based extraction. DevClarity now reads the session index from the database, then loads and parses the matching
chatSessions/*.jsonl transcripts directly from disk to recover your prompts and responses. This runs first; older VS Code layouts continue to work through the existing pipeline unchanged.
- Reset Copilot Sync History. A new Command Palette command (DevClarity: Reset Copilot Sync History) clears the local record of what's already been synced, so you can force a full re-scan if needed.
- Cleaner notifications. The "no chat sessions found" notice now appears only on a genuine first run, not every time VS Code restarts after a successful sync.
Claude Code and OpenAI Codex remain fully supported alongside GitHub Copilot. All three are off by default and opt-in.
The GitHub Copilot extractor has been rebuilt from the ground up to be version-independent and resilient to future VS Code updates.
The old approach relied on a fixed list of known storage keys inside VS Code's internal database. When VS Code changed its storage format, the extractor silently found nothing. That's fixed.
What changed:
Adaptive discovery. Instead of looking for specific key names, DevClarity now enumerates every entry in VS Code's workspace database and scores each one across 25+ signals — key name patterns, data size, JSON shape, presence of message structures, code blocks, and more. The top candidates are passed through the extraction pipeline automatically.
Three-stage extraction pipeline. Each database is processed through three stages in order, stopping as soon as data is found:
- Known-schema parser — fast path for VS Code versions we've seen before.
- Generic extractor — inspects JSON structure and handles role-based, exchange-based, session-container, and turn-array formats without assuming specific field names.
- Deep walker — recursively traverses the entire JSON tree to find any recognisable prompt/response pairs when the schema is completely unknown.
Binary decoding. DevClarity now handles base64-encoded, UTF-16, and doubly-escaped JSON payloads that some VS Code versions write to disk.
Debug mode. Set devclarity.copilot.debugDiscovery: true in your VS Code settings to get a full per-database report in the Output panel — every scored key, which stage succeeded, how many sessions and code blocks were extracted, and an explanation when nothing is found.
Claude Code and OpenAI Codex remain fully supported alongside GitHub Copilot. All three are off by default and opt-in. You can disable or pause any of them anytime from the Command Palette.
Getting started
- Install the extension from the VS Code Marketplace.
- Run DevClarity: Set Email and enter your OneClarity account email.
- Start coding.
That's it. Open your OneClarity dashboard anytime to see your activity feed.
If you'd like to include AI-assistant context in your summaries, run:
- DevClarity: Enable Copilot Intelligence — for GitHub Copilot
- DevClarity: Enable Claude Code Intelligence — for Claude Code
- DevClarity: Enable Codex Intelligence — for OpenAI Codex
All are opt-in, ask for explicit consent the first time, and can be turned off at any time.
Built for developers
DevClarity is designed around one principle: your focus comes first.
- Quiet by default — no popups while you work.
- Works in the background with no noticeable impact on VS Code.
- Saves you the daily grind of writing status updates.
More coding. Less reporting.
your task is to integrate the github copilot signal processing into beta and prod vs code extensions just like claude code and codex coding sessions. update signals_api for beta and prod accordingly to support copilot signals as well. create new commands to like: enable copilot signals, rescan and others just as alrady implemented for claude and codex coding chats.
