Agree on the goal.
Talk through what you want to change with an agent. The project records the goal and each decision, and the agent turns the discussion into a plan you can revise.
Gimbal · Product ambition
A multi-model software- and agentic-process engineering workspace.
Tell an agent what you want accomplished. It chooses and starts the appropriate workflow; you watch the work, inspect its shape and step in when needed. Engineers and agents author workflows in Go. You can understand them through their diagrams without learning how to launch them.
Agent-started workflows and workflow understanding are partially implemented; validation is unknown. See the promise inventory.
AN EXAMPLE WORKFLOW
01 / PLAN Break down the goal
Give a planning agent the outcome and constraints.
02 / IMPLEMENT Make the change
Give the coding agent a specific task and the files it needs.
03 / CHECK Review the result
A validator compares the work with the goal, then accepts it or sends notes back to the coder.
How Gimbal works
A project goes from conversation to a run you can watch.
Let the agent start the work.
The conversation agent discovers the appropriate workflow, supplies its inputs and starts it. You do not need to operate a launch form. The accepted run appears as a linked event in your session and a new tab, so you can follow the work without losing your place.
Watch the run and step in.
Open the run to see its progress, or browse a workflow guide and diagram to understand how it works. Inspect what an agent was asked and what it produced. Step in when a decision is yours, or stop a run that is heading the wrong way.
The project workspace
Your project keeps its history across agents and machines.
Conversations, diagrams, run results, and shared documents stay in one place. Give direction by voice, share an image or document, switch models, or run work remotely without losing the project thread.
For what ships today, see Delivery status.