Changelog

Specset can now take you straight into the right project chat when you open the installed app on site. Instead of finding the project and starting from scratch, you arrive with that project's conversation context already loaded.

Project managers set the site's coordinates and matching radius in Project Settings > General. Each user chooses whether to enable the feature in the installed app. When one project matches, its chat opens automatically. When sites overlap, Specset asks which nearby project you want.

The live device location is used only to perform the match locally. It is not stored or sent to Specset, and nearby-project detection can be turned off at any time from the account menu.

See Install the app to configure a project site and enable nearby-project detection.

Design quality reviews cast a wide net on purpose, and until now that meant you did the sifting. Every issue a review files is now checked by a second, independent AI before it enters your list. The verifier goes back to the plans and specs and actively tries to disprove the finding: it re-reads the cited sheets, checks drafting conventions, and looks for the answer elsewhere in the documents.

Issues that hold up show an AI confirmed badge. Hover it to read what was checked and why the issue stands, with a link to the full verification session. Findings that do not survive are archived automatically with the reasoning saved, so they never cost you a click. The verifier also gives severity a second opinion and rewrites vague titles, so what you see is worth your time.

Real-but-minor items, like typos, leftover boilerplate, and details a later revision will fill in, are routed to a separate Cleanup list instead of your review queue. The queue keeps only findings that need someone on the design team to make a call.

Read more in Issues.

Review tables, issue lists, extractions, drafted documents: everything the agent produces is an output, and every output now lives in the Library. It ships to every workspace today, at both the project and organization level.

• One place for everything the agent makes. The Library lists every output with its type, status, and the session that produced it. Search and filter to find a deliverable weeks later, or start a new output right from the page.
• Open outputs in place. Click a row and the output opens in a side panel, so you can drill into individual checks and issues without leaving the list, or jump back into the chat that produced it.
• Chat history knows what was produced. A new "Has output" filter and per-conversation output counts make it easy to find the conversation behind a deliverable instead of scrolling by title alone.
• Checklist skills can file issues. Turn on issue creation for a checklist skill and every flagged check becomes a draft project issue, cited and ready to triage.

The Library takes over from the Agent Sessions page as the home for agent outputs. Workspaces still using Agent Sessions keep it while they transition.

Read more in Skills.

Specset is now available as a native plugin for both Claude and Codex. Install one bundle to give either agent the project context and construction workflows it needs.

• Nine shared skills. Search specs and drawings, set up projects, manage submittals and RFIs, work with closeout records, ask project agents, and administer your organization.
• Native MCP tools. Search and read structured Specset content directly, with the same tool registry on both agents.
• Secure sign-in. Local plugins use browser or device authorization through the Specset CLI. Hosted ChatGPT connections use organization-scoped OAuth.
• File transfers. Claude and Codex can stream local uploads and downloads through the CLI. Hosted clients can pass attachments and receive short-lived download links through MCP.

The plugin defaults to read-only work and asks before changing project data. Credentials stay in the local CLI or the hosted OAuth connection rather than in the conversation.

Follow the setup guides for Claude and Codex.

Tell the agent something once and it sticks. Memory carries your preferences, decisions, and working conventions across conversations, so every new chat starts already knowing how your team works.

• Saved as you chat. State a preference ("always quote fire-rating requirements verbatim") and the agent saves it as a memory, marked with a chip in the conversation so nothing is stored silently.
• Applied everywhere. Memories load into every future conversation, org-wide or scoped to a single project.
• Yours to manage. Review, edit, and delete memories under Org Settings or Project Settings, including everything the agent saved on its own.

Read more in Ask the project.

Specset can now be installed to your home screen. It opens in its own window without the browser address bar, keeps its own icon in your app switcher, and stays up to date on its own.

• iPhone and iPad. Open Specset in Safari, tap Share, then Add to Home Screen. iOS keeps installed apps separate from Safari, so you sign in once more the first time you open it.
• Android. Chrome offers Install app from the account menu, or prompts you directly. It installs as a normal Android app.
• Desktop. Chrome and Edge can install Specset the same way, from the account menu.

Specset still needs a connection to load your projects. What changes is that a dropped signal no longer means a blank page: the app starts, tells you it cannot reach the server, and gives you a retry button. When a new version ships you get an Update available badge, on phones as well as desktop.

Nothing changes if you prefer the browser. Installing is optional and the web app works exactly as before.

See Install the app for the full walkthrough, including how to update and how to remove it.

Every team has review checklists, QA workflows, and extraction jobs that are theirs alone. Skills let you teach them to the agent once, then run them anywhere with a /.

• Create by describing. Tell the Skill Creator what you want in plain language, from the skills settings page or straight from the skill picker in chat, and it authors the skill with you. Prefer full control? Build it manually in the editor.
• Checklists and review tables. Define your own categories, checks, and custom columns, and the agent fills the table with cited findings each time the skill runs.
• Project-wide extractions. Extraction skills sweep every document, spec section, drawing sheet, or RFI in scope and build a results table row by row, with a citation on every value.
• Run it anywhere. Type / in any conversation to launch a skill, org-wide or scoped to a project.

Read more in Skills.