Skip to main content

Forgemate

Forgemate is the assistant in the bottom-right corner of every screen. It knows who you are and what you are looking at, it can answer questions about your own workspaces and runs, and — with your explicit confirmation — it can make changes for you.

Because the launcher is on every screen, Forgemate is often the first thing a new user interacts with, before they have learned a single one of this product's nouns. So this page assumes nothing.

One feature, two names

The product calls it Forgemate, and that is the name used throughout this documentation. You will occasionally see the surface referred to generically as "the Assistant" — same feature.

What it is for​

An always-available chat that has your context. Questions it answers well:

  • "Why did my last launch fail?"
  • "Which environments in this workspace have a controller connected?"
  • "What is the difference between a project and an environment?"
  • "Create a sandbox for this project in the staging environment."

And what it is not:

  • It is not the coding agent in your sandbox. It does not have your repository, it does not run your tests, and it does not write your code. That is Claude Code or Codex, running inside a container. Forgemate is about the platform, not about your source.
  • It is not a search box over the internet. Its knowledge of PlatformSmith is built in; its knowledge of your organization comes from the same API you use.

What it can see​

Two things, and nothing else:

  1. Who you are — your identity and your permissions.
  2. What screen you are on — the workspace, project or environment you are currently looking at, so "this project" means something.

It does not read your repositories, your container filesystems or your secrets.

What it can do on your behalf — and why that is safe​

The one sentence worth understanding

Every action Forgemate takes goes through the same API as you, authenticated as you, through the same permission checks. It cannot see or do anything you could not see or do yourself.

That is architectural, not a policy: your session's credentials are carried through to every call Forgemate makes. A workspace you cannot open, Forgemate cannot read. A runtime you are not allowed to start, Forgemate cannot start. If your role is read-only, Forgemate is read-only.

On top of that, changes are confirmed. When Forgemate wants to do something that writes, it shows you a card — Forgemate wants to make a change — describing the action, and nothing happens until you approve it. Approvals expire; an expired one has changed nothing, and you can simply ask again.

Whose model key it uses​

Your organization's AI credential, resolved per request from the integrations you configured. PlatformSmith does not supply a key for it.

Two consequences an administrator should know before rolling it out:

  • Its usage bills to your account, alongside everything else on that credential.
  • A rate limit you hit is your key's limit, not a platform quota. If Forgemate says its provider is rate-limiting, that is your own account throttling — often because agents and Forgemate are sharing one key.
There is no platform-side throttling today

PlatformSmith does not currently rate-limit or budget Forgemate usage on your behalf. Every member who can open the panel can spend the organization's credential, and the platform will not stop them.

If that matters for your organization, the controls available today are who has access (roles) and whether the feature is on at all — not a spend cap. Plan accordingly rather than discovering it from a 429.

If no AI credential is configured, the panel says so. An admin can connect one under Company settings → Integrations; anyone can add a personal key under Account → My integrations.

Threads and history​

Forgemate's history is kept in threads, held server-side, so a thread is still there when you come back on another day or another machine. You can start a fresh thread whenever the subject changes.

A thread is not a "Conversation"

Forgemate's history does not appear under Conversations in the sidebar. That sidebar entry is a different product noun entirely — platform-created, multi-party threads that have nothing to do with the assistant panel.

If you ask Forgemate something and then go looking for it under Conversations, you will not find it. Your Forgemate history lives in the Forgemate panel. The four execution nouns explains all of them side by side.

Limits worth knowing​

  • Long questions get truncated answers. Forgemate works in a bounded number of steps per question. If it stops early it says so, and the answer covers only what it had gathered. Asking something narrower gets further than asking the same thing again.
  • It does not act without being asked. There is no background Forgemate doing things while you are away.

Turning it off​

  • For yourself — close the panel. The launcher can be ignored; nothing runs unless you type.
  • For the whole deployment — Forgemate can be turned off for everyone. Ask whoever operates your deployment.
  • For one person — Forgemate acts as the signed-in user, so what someone can do through it is exactly what their role allows. To change that, change their role. → Security and tenancy
Last updated on