Limitations & FAQ
What Forge doesn't do, why, and answers to common questions.
Forge is in beta, and some boundaries are deliberate design choices rather than missing features. Knowing them saves you from asking for things that won't happen.
What Forge doesn't do
- Manage applications. Forge works inside the application currently open in Studio. It can't create, switch, rename, or delete applications — if no app is selected, it will ask you to pick one and wait.
- See other applications. Each conversation is scoped to one application. Data, flows, and integrations of your other apps are invisible to it.
- Deploy without being asked. Forge can deploy — but only when you say so, and always behind a high-risk card. A build ends in a draft.
- See your secrets. Forge knows that a credential exists, never its value. Keys and tokens go through the masked credential card, not through the chat.
- Create knowledge bases or upload documents. It connects existing knowledge bases to agents; creating them and uploading files happens in Studio.
- Read attached files. There's no attachment support yet — paste text into the chat instead.
FAQ
Forge is in beta — capabilities grow release by release, so a "not yet" on this page may stop being true. When in doubt, just ask Forge whether it can do something: it knows its current abilities and will say no honestly.