Pilot launch

12 Apr 2026 – 22 Apr 2026by Ola Piętka

+6 added~6 edited−1 deletedacross 7 features· 3 releases

Feedback became a two-way channel: a history page collects every submission, shows the Specsight team's replies inline, and carries attachments. Mentions and other alerts now also appear in an in-app notifications menu, not only by email.

Key changes

FeedbackA history page lists every past submission with its status, shows replies from the Specsight team inline, and displays any attached images.
In-app alertsMentions and other updates that previously only arrived by email now also collect in a menu inside the dashboard.
ExportsThe spec can now be saved as Markdown alongside PDF and Excel, and any single feature can be saved on its own.
ChangelogExpanding a release now shows a per-feature breakdown with the before and after of every changed detail, instead of a separate link.

Worth knowing

IntegrationsThe API Keys page is now the MCP page; the old write-capable script key was removed in favour of read-only tool access.
Plan limitsThe free tier is now capped at a single project.

Feedback

+4 added

ContextActionOutcome

user on the feedback history pageviews the pageevery past submission is listed with its category badge, status pill, submission date, and any reply from the Specsight team

user on the feedback history page with a submission that has a response from Specsightviews the entrythe Specsight team's reply appears directly below the original submission

user on the feedback history page with a submission that includes attachmentsviews the entrythe attached images appear inline with the submission

user on the feedback history page with no submissions yetviews the pagean empty state explains how to submit the first piece of feedback via the Feedback button in the dashboard

Export

+2 added

ContextActionOutcome

user on the spec pageopens the export menu and chooses Markdowna Markdown file downloads, with a table of contents and scenarios grouped by category

user viewing a single feature in the specexports that featurethe export contains only that feature and its sub-features, with a breadcrumb showing where it sits in the wider tree

MCP

~1 edited−1 deleted

ContextActionOutcome

~~Was: member on the API Keys page~~member on the MCP integrations pagecopies the MCP server URL~~Was: the URL is copied to the clipboard, ready to paste into an AI tool that accepts an API key~~the URL is copied to the clipboard, ready to paste into an OAuth-compatible AI tool such as Claude Desktop

~~admin on the API Keys pagegenerates a key for a custom script that calls the public Specsight APIa full-access key is shown once for copying; the script can read and write spec data using the key~~

Email Notifications

~2 edited

ContextActionOutcome

member with mention notifications enabledanother member @-mentions them in an annotation~~Was: an email arrives with the annotation snippet and a link back to the scenario~~an in-app notification appears immediately and an email arrives with the annotation snippet and a direct link to the scenario

user on the notification preferences pagetoggles an email type off~~Was: the preference is saved; events of that type no longer trigger an email~~the preference is saved immediately; events of that type stop sending emails but in-app notifications still appear

Changelog

~1 edited

ContextActionOutcome

user on the changelog pageexpands a sync entry~~Was: the entry opens into a list of affected features with a count of changes under each; the individual scenario changes sit behind a separate link~~the entry opens into a per-feature, per-scenario breakdown showing the before and after of every changed field

Annotations

~1 edited

ContextActionOutcome

user in the annotation popover with an @-mention in the notesubmits the annotation~~Was: the annotation is saved; the mentioned member receives an email with the snippet and a link back to the scenario~~the mentioned member gets an in-app notification — and an email too, if they have mention emails enabled

Feature Map

~1 edited

ContextActionOutcome

user on the feature map page where graph generation has failedviews the page~~Was: an error notice is shown; the page suggests upgrading the plan if the failure was due to a plan limit~~an error notice is shown; admins and developers see a button to try regenerating the graph