First weeks: bug-fix sprint and the graph goes live
17 Mar 2026 – 11 Apr 2026·by Specsight
The first month after launch settled into a rhythm: change reports themselves shipped at the start of the window, AI tools gained read-only access through a new gateway a week later, and most other work was sharpening rough edges that surfaced in the first couple of weeks.
What's new
·Change reports arrived — pick any date range, get a structured release-notes document with a written summary, public share links, and a downloadable PDF.
·Scheduled reports — set a weekly or monthly cadence and the report is generated automatically.
·AI tools can now read product knowledge directly — compatible assistants such as Claude Desktop and Cursor connect through a read-only gateway covering project lookup, summaries, search, and change history.
·Password-free sign-in for AI tools — a consent screen approves access without anyone pasting a key.
·Stuck releases now recover automatically — when an analysis sits more than fifteen minutes without progress, it is abandoned and a fresh one is queued with the latest changes.
·A Feedback button arrived in the dashboard — a modal where any member can send bug reports, ideas, and questions to the Specsight team.
What's changed
·Date ranges in change reports are now end-inclusive, so the chosen final day is fully covered in the result.
·Onboarding lets a new team skip the GitHub step and pick a plan first, instead of waiting on it to proceed.
·The diagram canvas restores zoom alongside grab-to-drag panning, with fit-to-view to recentre on the whole graph.
·Reports generated before a re-analysis now carry a clear "stale" notice when opened, warning that the numbers may not match the current state.
·The release-ready email reads in plain language now, with a shorter subject and no internal jargon.
·Concurrent releases on a watched branch are queued instead of dropped, so every release reaches the analysis pipeline.