Developer dashboard · coming in the next release
Cotterpin works on your machine and keeps its figures there. The dashboard is where you can see them across all your machines, check your licence, follow the bugs you reported and the discounts they earned. It shows figures only. Your code never leaves your machine.
You may run Cotterpin on a work laptop, a home machine and a spare. Today each keeps its own counts. The dashboard adds them up, so you see what your agents did and what Cotterpin caught this week and this month, wherever you worked.
Which plan you are on, when it renews, which machines it covers, and the upgrade on offer, without digging through emails. Turning auto-renew on or off changes the subscription itself.
Every real defect you report makes Cotterpin better for everyone. The dashboard shows each report's progress and the credit and discounts it earned you.
cotterpin subscribe --claim <email>.cotterpin dashboard link: it shows a short code, you confirm it on the dashboard, and that machine is linked. A licence covers three machines; unlinking one on the dashboard frees its place.Nothing is sent from a machine until you switch it on there, in your own terminal, and you can see exactly what would be sent first.
Your plan (Watch, Pro or Team), its expiry or renewal date and auto-renew, your linked machines and when each was last seen, your Team seat if you have one, and the discounts you have earned.
The same figures as your terminal's summary line, explained: agent actions checked, guard rails fired (refused, asked, advised), commits and pushes, and what the model and effort matrix saved, by day, week and month.
Every report you sent and where it is: received, being triaged, confirmed, fixed, released. The same list cotterpin bug-report prints, with the credit each one earned.
The activity and savings report as a page or a PDF, for any range, and optional weekly or monthly reports to your own address.
What it is: when you report a real defect in Cotterpin, you earn credit, and as your credit grows you reach grades that bring discounts and early access. Why we do it: Cotterpin's guard rails get better fastest from the failures developers meet on their own code. A failure you report becomes a fix for every user, so the people who find them share in what they make possible. The grades and what they earn are on the savings page.
Each report is checked before it earns credit: is it the same failure as one already reported, the same gate or healing skill, or something already in our plan to build and deploy? A known one adds weight to the existing item, so it is fixed sooner. A new one opens a new item. Your dashboard shows which, and when the fix ships. Reports can be sent by you, one at a time, or automatically once you switch that on for a repository; you can always send or deny any report yourself.
No code, ever. Not your files, diffs, paths, commands, prompts, agent replies, commit messages, repository names or secrets. The dashboard holds figures only: dates, counts, savings, and an id for each repository, never its name or address.
The one exception is yours to make: a team pack is a .cotterpin/ folder your team commits to its own repository, holding your team's own rules. It goes wherever that repository goes, under your team's control, and never to Cotterpin.
Your terminal already shows today's figures: cotterpin report daily and cotterpin report weekly keep your history on your machine.