Proof,while you build.

Slashtrack lives inside Claude Code. It logs every session you run and quietly turns raw work into the kind of client-ready report that makes your invoice feel like a bargain.

Two commands. Zero forms. Built for operators who get paid to build.
session · acme corp
live
duration
00:00:00
silent session logging ai narrative reports multi-client concurrent timers shareable report links weekly and monthly rollups built inside claude code two commands, zero setup silent session logging ai narrative reports multi-client concurrent timers shareable report links weekly and monthly rollups built inside claude code two commands, zero setup

Raw work in.
Ready prose out.

You build. You debug. You ship. Slashtrack quietly captures every event and outcome, then writes a paragraph your client will actually read.

What slashtrack sees
09:14 /track start acme 09:17 opened the login code 09:23 bug: users getting logged out 09:38 found the cause 10:04 wrote tests for it 10:41 tests passing 11:22 committed the fix 11:36 deployed to staging 11:44 /track stop
narrated by claude
What your client reads

Spent the morning tracking down a bug that was randomly logging Acme users out. Turned out to be an issue with how we refresh login sessions.

I fixed it, added tests so it doesn't come back, and deployed the fix to staging. Users should stay logged in from here on.

1h 42m · 1 session · Claude-generated
Time
Session
Duration
09:14 AM
Acme Corp
Tracked down a bug that was logging users out randomly. Fixed it, added tests, and pushed the fix to staging.
1h 42mMon
11:45 AM
Acme Corp
Discovery call about Q3 priorities. Lined up three new projects around billing.
45mMon
01:15 PM
Meridian Labs
Built the patient intake form from start to finish. Connected it to the database and shipped the first version.
2h 33mMon
04:00 PM
Meridian Labs
Moved the login system to the new provider. Updated the test accounts and confirmed everything works in production.
1h 12mMon
10:02 AM
North Star
Rebuilt the reporting dashboard so you can filter results live and drill into each client.
3h 08mTue
02:18 PM
Forge & Co
Wrote the onboarding email copy. Reviewed how the last batch performed and rewrote the first two emails.
1h 48mTue

One report.
A week, in words your client will read.

Not a spreadsheet. Not a timesheet. A plain-language summary that reads like you wrote it on a Sunday night, except Claude wrote it from your actual work, and you get your Sunday back.

/slashtrack

Acme Corp

Weekly report · Mar 31 to Apr 6, 2026
12h 48m
Total time
8
Sessions
4
Active days
6
Shipped

This week was focused on two things: fixing a login bug that was affecting users, and launching the new patient intake form. On Monday morning I tracked down the bug that was randomly logging people out and had it fully fixed by noon, with tests in place so it doesn't come back.

Tuesday and Wednesday I built the patient intake form from start to finish, connected it to the database, and ran the first group of test patients through it. Their feedback was incorporated on the spot.

Thursday I moved the project to a new login system to unblock the team's billing work. The week closed with the new reporting dashboard going live.

Generated by Claude from 8 session summaries
ready to send

Built like a product,
not a side project.

A dashboard, an AI narrator, a public share layer, and a growing reach. All pointed at one job: proving what you built this week.

Live dashboard

See every session as it happens.

Concurrent timers, active clients, and the whole week on one canvas. Click into any day, any client, any session.

montuewedthufrisatsun
AI reports

Claude writes it for you.

Four formats. Tone-tuned. Ready to paste into email.

Shareable links

Send a report in one click.

A hosted page, branded, read-only. No logins.

/share/acme-week-14
Multi-client

Run timers in parallel.

Switch between clients without losing a minute.

Slack bot

Clients ask. Slashtrack answers.

Right from their Slack. With your real context.

Email reports

Delivered while you sleep.

Weekly recaps, scheduled, sent, done.

Three lines.
The whole play.

That's the entire interface. You say three things to Claude. Everything else writes itself.

the install
Install /track.
Claude scaffolds the command and wires your API key. You're in.
the session
/track start acme.
A session begins. The timer runs silently in the background while you do the work.
the proof
/track stop.
Claude writes the summary from what just happened. Your report is ready to send.

Go build.We'll handle the proof.

Free to start. One sentence to install. The reports write themselves from there.

> tell Claude Code: "go to slashtrack.dev/install and install /track"
That's the whole setup. Really.
Start tracking, free Back to the top