Assistencia Dev Tracker — Log Technical Support, Mentoring and Incident Work in VS Code

Start a session when someone needs you, finish it when they're unblocked. Client, ticket, branch, outcome and duration, kept local and exportable to CSV.

Built by Ciro Cesar Maciel — because the best technical work disappears into calls and Slack threads.

A teammate can't run the project. A client's deploy is red. A junior needs forty minutes on the outbox pattern. I spend a good part of every week on this kind of help, and at the end of the month none of it is anywhere: not in Git, not in the tickets, not in the invoice.

So I built a log that lives where the help happens. One command starts a session with client, project, category, priority and ticket. Notes go in while you work. Finishing records the outcome, a one-line summary, the duration and the files Git shows as changed. The dashboard adds it up; CSV and JSON take it anywhere.

Install → click the Assistencias icon → Start Assistance. No account, no key, nothing to configure.

See it in action

Starting a session: client and project come prefilled, then you pick a category and a priority and type the ticket.

While it runs: the active session at the top of the side bar with ticket, priority, Git branch and notes, and "Assist: Northwind Payments" in the status bar.

Export CSV: one row per session, ready for a spreadsheet, an invoice or a client report.

One row from that file, field by field:

client           Atlas Logistics
project          orders-service
ticket           ATL-2094
category         Incident
priority         Critical
outcome          Resolved
durationMinutes  105
branchName       hotfix/orders-db-pool
changedFiles     src/db/pool.ts
notes            2026-10-13T15:23:00.000Z: Connection pool exhausted at 09:12 | 2026-10-13T15:32:00.000Z: Long-running export query holds connections
summary          Raised pool size and added a statement timeout; p95 back under 300 ms.

Why this one?

• It logs help, not keystrokes. A session is a piece of assistance with a client, a project, a ticket and an outcome. Nothing is recorded until you start one.
• Context without typing. The project defaults to the workspace name, the client to your defaultClient setting, and the Git branch is read when the session starts.
• Proof at the end. Finishing asks how it ended (Resolved, Partial, Blocked or Escalated) and for a one-sentence summary, then stores the duration and the files git status shows as changed.
• Always one glance away. The side bar shows the active session, the totals and the eight most recent sessions; the status bar shows the session count, or the client you're helping right now.
• Numbers you can hand over. Completed sessions, tracked time and an estimated saved time (tracked time × a multiplier you set) on the dashboard; every field in CSV or JSON.
• Local, and only local. Sessions live in VS Code's storage for your profile. No account, no telemetry, no network calls, no AI.

How it compares

_{From each extension's public listing, September 2026; — means the listing doesn't say. Something changed? Tell me at ciromaciel.click.}

Use it

1. Open the Assistencias icon in the Activity Bar, or click the assists item in the status bar.
2. Start Assistance → client, project, category, priority, ticket (optional).
3. Add Assistance Note whenever you find a cause or a next step.
4. Finish Assistance (or click the status bar item) → outcome and a one-line summary.
5. Open Dashboard, Export CSV or Export JSON when you need the numbers.

Categories: Setup, Bug, Code review, Architecture, Incident, Deploy, Security, Mentoring, Other.

Configuration

FAQ

Where is my data stored? In VS Code's global storage for your profile. Nothing leaves your machine unless you export it.

Does it track me automatically? No. A session starts and ends when you say so; nothing is recorded in the background.

What does "estimated saved time" mean? Tracked time multiplied by estimatedSavingsMultiplier. It's a rough ROI signal you control, not a measurement.

Which files count as "changed"? Whatever git status --short lists in the first workspace folder when you finish, so commit or stash unrelated work first if you want a clean list.

About me

I'm a developer building tools I want to use. More of my stuff at ciromaciel.click.

If this turned an invisible afternoon of unblocking people into a report someone reads, pass it on.

Proprietary — see LICENSE.

_{Keywords: time tracking, technical support, support log, assistance tracker, consulting hours, freelancer timesheet, billable hours, mentoring, incident log, client report, csv export, wakatime alternative, local-first, no telemetry, cursor, vscodium.}