Known issues

PlatformSmith is in early access. This page lists behaviour that is currently wrong or surprising, with the workaround. It is kept honest on purpose — finding a problem listed here costs you a minute; finding it undocumented costs you an afternoon.

Your organization has no default coding agent until you connect a credential

What happens. Signup seeds two agent definitions — Default (Claude Code) and Default (Codex) — and flags neither as the organization's default. A launch that does not name a definition is therefore refused, with no agent definition resolved for this launch and no company default is set.

This is by design, and the setup wizard closes it for you: connecting a credential flags the matching definition. It is listed here only because the error message describes a state you can legitimately be in, and it reads like a defect when it is not.

Workaround if you hit it anyway — for instance if you added the credential outside the wizard: open the definition for the coding agent you use and set it as the company default. → No default coding agent yet

There is no spend limit on Forgemate

What happens. Forgemate spends your organization's AI credential, and PlatformSmith does not currently rate-limit or budget that usage. A rate limit you hit is your provider account's limit.

Workaround. The controls that exist today are who has access and whether the feature is enabled at all. There is no spend cap to configure.

A browser can be slow on its first page load

What happens. The very first load of the app in a session can take several seconds, particularly on Windows. Subsequent loads are fast.

Workaround. None needed — it is a first-load cost, not a persistent one.

Reporting something not listed here

→ Support. A report that includes what you expected, what happened, and roughly when is worth three that do not.