Treva — Connect Your Editor to Your Project Map

Treva detects file save activity in your editor and updates your project's journey path in real time. PMs see progress as you code — no status updates, no check-ins, no workflow changes.

Automatic detection — saves are batched every 5 minutes and matched to milestones
Privacy-first — file paths are used for matching then discarded. No code content, no keystrokes, no individual metrics
Zero friction — install, paste a token, pick your project. Then just code

Setup

1. Generate a token

Go to trevahq.com → Settings → API Tokens → name your token (e.g. "My MacBook") → Generate → copy the trv_... token.

2. Install the extension

Install Treva from the VS Code Marketplace, or search "Treva" in the Extensions panel.

3. Connect

When the extension activates, you'll see a notification: "Connect your editor to your project map". Click Set up Treva, paste your token, and select your project.

That's it. The status bar shows your project name and when data was last sent. Just code — the map updates automatically.

Features

Status bar — shows connection state at a glance:

Connected: project name + "Last sent: 3 mins ago"
Paused: tracking paused (click to resume)
Sending: batch in progress
Error: connection issue (click to reconnect)
Disconnected: no token configured

View Sent Data — open a panel showing exactly what Treva sent: file paths, branch, timestamps. Full transparency.

Pause / Resume — pause tracking anytime from the command palette. Your choice, always.

Git branch detection — automatically tracks your current branch so the dashboard shows which branch activity is on.

Commands

Command	Description
`Treva: Select Project`	Connect to a Treva project (prompts for token if needed)
`Treva: Pause Tracking`	Temporarily stop sending activity
`Treva: Resume Tracking`	Resume sending activity
`Treva: View Sent Data`	Open panel showing exactly what was sent
`Treva: Disconnect`	Remove token and project selection

Settings

Setting	Default	Description
`treva.serverUrl`	`https://www.trevahq.com`	Treva server URL
`treva.batchIntervalMinutes`	`5`	How often to send activity batches (1–30 minutes)

Privacy

Treva is built on a simple principle: measure reality, don't surveil people.

File paths only — used for milestone matching, then discarded. Never stored on the server.
No code content — Treva never reads, sends, or stores any code.
No keystrokes or idle time — only file save events are detected.
No individual metrics — all activity is aggregated at the milestone level. No leaderboards, no per-person tracking.
Your token, your control — pause, view data, or disconnect anytime.
OS keychain storage — your token is stored in VS Code's SecretStorage (backed by your OS keychain), never in plaintext.

This is the same privacy model as Treva's GitHub integration: metadata is processed for matching, then discarded.

Requirements

VS Code 1.85 or later (also works in Cursor and other VS Code forks)
A Treva account with at least one project
Git (for branch detection)

Troubleshooting

Extension says "Disconnected" — Run Treva: Select Project from the command palette to set up your token and project.

Status bar shows "Error" — Click the status bar item to reconnect. Check that your token hasn't been revoked in Settings → API Tokens.

No activity showing on dashboard — Make sure your project has commit intelligence enabled (Project Settings → GitHub & Signals). Activity batches are sent every 5 minutes by default.

Treva

trevahq