Foundations

17 Mar 2026 – 11 Apr 2026by Ola Piętka

+13 added~4 editedacross 8 features· 8 releases

Change reports arrived first, turning any date range into a written summary you can export or share. A connection to AI tools like Claude Desktop and Cursor followed, and a Feedback button now sends questions straight to the Specsight team.

Key changes

Change reportsTurn any date range into a written summary — download it as a PDF, share it by link, or schedule a recurring cadence.
AI toolsThe spec opened to Claude Desktop, Cursor, and other compatible tools, with a password-free sign-in path so agents can read it directly.
FeedbackA button in the dashboard lets any member send a bug report, idea, or question straight to the Specsight team.

Worth knowing

OnboardingSkipping the GitHub step no longer blocks setup — you can connect a repository later and still reach the dashboard.

Digests

added+4 added

ContextActionOutcome

user on the reports pagerequests a report for a chosen date rangethe report is queued; the row shows a generating status while Specsight writes it in the background

user on the reports page with a completed reportopens the reportthe report opens with a Specsight-written summary at the top and structured release-notes sections below

user on a completed reportdownloads the report as PDFa formatted PDF downloads with a cover page and the release notes inside

editor or admin on a completed reportgenerates a public share linka public URL is created; anyone with the link can read the release-notes view of the report while the internal change-details view stays private

MCP

added+3 added

ContextActionOutcome

member on the MCP integrations pagecopies the MCP server URLthe URL is copied to the clipboard, ready to paste into an OAuth-compatible AI tool such as Claude Desktop

admin on the MCP integrations pagegenerates a new connection key for an AI toolthe full key is shown once for copying; afterwards only the prefix is listed alongside the other connection keys

AI agent connected with a valid tokencalls one of the read tools (such as list projects, get scenarios, or search)Specsight returns the requested spec data in a structured form the agent can read

Feedback

added+3 added

ContextActionOutcome

user anywhere in the dashboardclicks the Feedback buttona feedback modal opens with a category selector, a message field, and a submit button

user in the feedback modalpicks a category, writes a message, and submitsa confirmation toast appears and the modal closes; the submission is sent to the Specsight team for review

user in the feedback modalsubmits the form but the request failsan inline error explains the submission could not be sent; the message stays in the field so it can be tried again

Connect an AI Tool

added+2 added

ContextActionOutcome

user on the OAuth consent screenpicks an organisation and approves accessthe user is sent back to the AI tool with an authorisation code the tool uses to finish signing in

AI tool that has just received an authorisation codeexchanges the code for access tokensSpecsight issues a short-lived access token and a longer-lived refresh token; the tool can now read the spec

GitHub Integration

+1 added~1 edited

ContextActionOutcome

project with a watched branchnew code is merged to that branch~~Was: a sync is triggered; if another sync is already in flight, this one is dropped — only the latest merge triggers a fresh sync once the running one finishes~~a sync is queued automatically; once it completes, the spec reflects the new behaviour

project with a sync stuck past its timeoutnew code is merged to the watched branchthe stuck sync is cleaned up by the timeout sweeper and a fresh one is queued for the latest changes

Onboarding

~1 edited

ContextActionOutcome

user on the onboarding GitHub step~~Was: chooses to skip the GitHub step~~chooses to connect GitHub later~~Was: the wizard advances to the project setup step; project creation is blocked until GitHub is connected~~GitHub step skipped; advances to the plan selection step

Digests

~1 edited

ContextActionOutcome

user viewing a report that was generated before the last re-analysisopens the report~~Was: the report opens normally; nothing indicates that a re-analysis has happened since it was generated~~a "Stale: generated before a re-analysis" notice is shown, warning that the numbers may not match the current spec

Email Notifications

~1 edited

ContextActionOutcome

member with scan-complete notifications enabledSpecsight finishes analysing one of their projects~~Was: an email titled "Project [name] analysis complete" arrives with the change counts — added, changed, removed scenarios — and links to each updated feature~~a "Your [project] spec is ready" email is sent, with the new feature and scenario counts inside