Product updates

We're introducing Landscape from AI Transform Studio Visual MCP Apps.

The agent builds a nested map of the estate from the sources you connected — business capability maps and application landscapes. You can colour by a view, and reopen that map later with the sources still attached.

We're adding OAuth so you can sign in as a user to a MCP server. The add-server flow now supports that sign-in, including servers that need an organization app rather than a public link.

Once you sign in, the agent can use that server in the session.

Three more templates for work that usually lives in a register, a policy pack, and a journey slide that never meets the systems behind it.

The forum that funds work and the forum that lets it go live rarely share a picture. These three templates write the packet those rooms actually decide from.

Keep, consolidate, retire, or reinvest is a decision, not a grid in a spreadsheet. These templates walk one slice of the estate at a time.

Principles that cannot be applied in a forum next Tuesday are not principles. This pack is the definitions, the test against the estate, and the trail of exceptions.

After the programme, someone still has to say who owns each capability and which shared platform the firm will actually fund. Two templates for that work.

We're introducing Factory. Factory is how you create a workbench: you describe the repeating job, approve the plan, and Factory writes the folder tree you then run.

We're also releasing a library of workbench templates. On day one, two templates for deal work:

We're introducing Workbenches. A workbench is a folder tree for a transformation job: numbered stages, each a folder with its own brief — what it reads, what it writes, and what you check.

The tree is the job. Status lives in those folders, so you can open any stage and see where the work stands. The agent works one folder at a time, and a gate sits between stages — the next folder does not open until you have reviewed that stage. That is how a repeating transformation job stays structured, instead of one long thread.

We're introducing Goals on the session. A goal is for long-running work: you set the objective once, and it stays on the session while the agent works through it.

The agent can keep that objective in view across turns, the same way a coding agent holds the job it is working on. You can edit or clear the goal when the work changes.

We're introducing sub-agents so the main session can hand a slice of work to another agent. There are two modes.

One carries this session: the child starts with the conversation so far, which is useful when the slice depends on what you already covered. The other starts fresh: a self-contained prompt and no parent history, so that slice has its own context.

The child reports back with a result. You stay on the main thread.

We're introducing Plan mode. Before the agent starts the work, it writes a plan and waits for you to review it.

You can approve the plan, change it, or send it back. Nothing runs against your connected systems until you say so. This is the same idea as planning a change in a coding agent before it edits the repo: agree the approach, then run it.

When the agent needs a decision from you — which source to use, whether to take the next step — the session holds and shows that wait in chat.

You answer, and the run continues from the same place.

We're introducing Tasks in chat. Tasks are a checklist the agent keeps on the session and checks off as it progresses through the work.

Each item shows whether it is done, in progress, or still open. If you reopen the chat later, the list is still there in the transcript, so you can see how far the work has got.

We're introducing present mode. It opens the artifact full-screen from the Stage: the same board, the same connected data, without the rest of Studio around it.

Some actions need a person before they run: a write, a sensitive tool, a step you have not seen yet.

We're introducing approvals in the session. You see what is about to happen, then allow it or hold it. The rest of the session can continue while that gate is open.

We're introducing Roadmap from AI Transform Studio Visual MCP Apps.

The agent assembles the work from the sources you connected, on a timeline. You can rework dates while you are still deciding.

We're introducing Kanban from AI Transform Studio Visual MCP Apps.

The agent builds the board from the data sources you connected. You can move a card, ask the agent to re-sequence, and the board updates. You can reopen that board later with the sources still attached.

We're introducing a catalog of MCP servers you can connect in Studio. Pick one from the list, or add a custom server by URL and keep it as a profile on the session.

Once you connect it, the agent can use that server's tools in the session. The catalog is a starting set — we'll keep adding supported servers. You choose what the session can reach. Studio does not replace those systems.

We're launching AI Transform Studio, an agentic workspace for enterprise transformation work.

You and an agent work the same question against the systems you already run, and leave with a living artifact you can reopen. Bring the AI models your organization already uses.