Changelog

5 October 2026 (later)Copy Anchor Link

The org picks its tools, in Settings

• New Tools tab in the org's Settings: every tool has an on/off switch and its Connect button. Org Admins and Managers use it. See Settings.
• Only the tools that are on are visible to the people in the org.
• Turning a tool off hides it for new links. What is already linked keeps working.
• Your own logins moved to your Settings → Connections.
• The Connections page is gone from the left menu. The deploy webhook and the deploy rules are in the org's Settings → Tools.

5 October 2026Copy Anchor Link

Settings that pass down: login length, and who can invite and create

• Set a setting once, higher up. The levels below follow it, unless they pick their own. An Admin can enforce a setting, so the levels below cannot change it. Each setting shows where its value comes from. See Settings.
• New Security tab: login length (1, 7, 14 or 30 days) for the company and the org. Each person can pick a shorter time in their own Settings → Security.
• New Permissions tab on the company, org, workspace and team: who can bring people in, and who can create workspaces, teams and features.
• Buttons you may not use are hidden, with a line that says why.
• Settings changes are in the audit log, in plain words, with their own filter.

4 October 2026 (later)Copy Anchor Link

Workspaces and teams with their own people, and a page for every place

• The left menu now shows the places you run: an Orgs, Workspaces or Teams tab, with a tree. See Companies and orgs.
• Every org, workspace and team has its own page, and a Settings button with tabs. See Settings.
• Workspaces and teams have their own Admins, Managers and Users. Rank goes down: an org Admin is Admin of every workspace and team. Every team now sits in a workspace. See Workspaces and teams.
• Invite people by email straight into a workspace or a team, with a role.
• Managers bring people in as User or Manager and remove Users. Only Admins change a role. See Roles and permissions.
• Companies have Managers as well as Admins. Company Admins rename the company and choose who runs it in Settings → Company.
• Workspace and team Admins see their own part of the audit log. Workspaces show their own usage.
• The Admin and Teams tabs moved into the org's, workspace's and team's settings.

4 October 2026Copy Anchor Link

Companies, orgs and clearer roles

• A company now holds one or many orgs. Signing up without an invite creates your company and its first org. See Companies and orgs.
• The org switcher in the top bar moves you between orgs. Sign-in opens the org you used last.
• Three roles at every level: Admin, Manager and User. See Roles and permissions.
• New audit log: who did what, and when. Records cannot be changed. Download as CSV. See Audit log.

1 October 2026Copy Anchor Link

Microsoft Teams: one approval for the whole company

• When your Microsoft admin connects Teams, it is approved for everyone.
• Others connect with limited access until then. Copy link for your admin sends them a one-week approval link. See Microsoft Teams.
• AI assistants: the short address https://mcp.seamtrail.com now works too.
• The Participants panel shows each person's role on the feature.

29 September 2026Copy Anchor Link

Atlassian personal data

• When Atlassian says an account was closed, its name becomes "Former user" in SeamTrail. Renamed accounts are updated.

28 September 2026Copy Anchor Link

Decisions cause drift

• A decision made anywhere — Slack, a Jira comment, a meeting summary, an assistant's note — is now checked against the doc sections. The tickets and pull requests it makes out of date are flagged. See Drift.
• Drift shows in the Drift tab, in the SeamTrail chat and in your AI assistant.
• Links make themselves: a ticket number inside a doc section links the ticket to it. Other tickets are matched by their description. Remove a wrong link with Not this section. See Links.
• Every assistant now gets what changed since it last looked, on every call. New feature_context tool.

27 September 2026Copy Anchor Link

Memory you can trust

• Every memory says how sure it is: recorded, said or claimed. See Memory.
• When a note contradicts an earlier decision, only the writer is asked to replace it. The earlier author is told once. Nobody else is bothered.
• New History tab: what used to be true, and what replaced it.
• The same thing noted twice is kept once, with "also noted by".
• New Usage: Admins see workspaces and people; everyone sees My usage. See Usage.

25 September 2026Copy Anchor Link

• Only a feature's people can open it. Admins see the list of features and their usage, never their content.
• Everyone on a feature sees the same picture, even without their own Jira login.
• The SeamTrail chat knows today's date and your time zone.

24 September 2026Copy Anchor Link

The SeamTrail agent can act

• It proposes a plan. Nothing happens until you confirm. Every change can be undone. See The SeamTrail agent.
• It can move, comment on and assign Jira tickets — as you, on your own login.
• When something is unclear, it asks with buttons. It remembers your team's words.
• A blocker that is Done in Jira no longer blocks a deploy. It becomes a warning.

19–20 September 2026Copy Anchor Link

• Deploy gate: your CI asks SeamTrail before a deploy. See Promotion rules and deploy gates.
• Miro boards, with drift for wireframe frames.
• Memory keeps itself true: fixed blockers and answered questions close by themselves.
• New connectors in early access: Bitbucket, Figma, Zoom, Microsoft Teams, Notion and Google.

16–17 September 2026Copy Anchor Link

• SeamTrail MCP: AI assistants read and write the same memory. They sign in by themselves. See Connect an AI assistant.
• Two logins: background work uses the org's connection; everything you do uses your own login.
• Anyone in the org can create a feature.