Axellero Forge
BetaAn AI copilot built into Axellero Studio. Describe what you want in plain language — Forge designs, builds, tests, and deploys it, asking for your approval before changing anything.
Axellero Forge is an AI copilot that lives in a chat sidebar inside your application in Studio. Instead of assembling workflows node by node, you describe the outcome you want — Forge explores your application, proposes a plan, builds it, and checks that it works.
You: Build a workflow: when an order comes in, check stock,
save the order to the database, and respond with 200.
Forge: I'll create the workflow in three steps. First, let me look
at your database schema...Forge already knows the context you're working in — your current application, its database, integrations, and flows — so you don't need to explain your setup before asking for help.
What Forge can help with
AI agents
"Create a support agent that can look up orders in the database" — Forge builds the agentflow, wires up its tools, and chats with the finished agent to confirm it responds correctly.
Workflows
"Add a branch: if the item is out of stock, return 410" — Forge edits the flow, runs it with test data, and shows you where each step succeeded or failed.
Database
"Create a customers table with name, email, and phone" — Forge designs the schema, and can query or fill in test data on request.
Integrations
"Connect our internal REST API" — Forge sets up connectors and credentials, inspects the API schema, and tests the connection. Secrets go through a masked form, never through the chat.
Deploying
"Deploy the order workflow" — Forge freezes the draft into a new version and ships it live, behind a high-risk approval card.
Agent features
"Give the agent a knowledge base and a guardrail" — Forge wires skills, knowledge bases, guardrails, and handoffs between agents.
Triggers & scheduling
"Run this workflow every hour" — Forge creates the trigger and subscribes your workflow to it.
Debugging
"Why did the last run fail?" — Forge reads the execution logs step by step and explains what went wrong.
How a session flows
Forge works iteratively: it keeps a plan you can open at any time, checks in with you before each change, and finishes by testing what it built — running workflows with sample data or chatting with a newly created agent.
Good to know
- Forge works within the application currently open in Studio. It can't create, switch, or delete applications — pick the app first, then ask.
- Changes land in draft versions. A draft goes live only when you ask Forge to deploy it — or deploy it yourself in Studio.
- Forge groups related changes into one approval card. Building a whole workflow is usually one card, not twenty.
- Forge is in beta: it handles large features iteratively (happy path first, edge cases next), and some capabilities are still on the way.