Vague Studio
BetaAgents that run your work.
An agent on your own records. It watches, proposes the next action, and waits for a person to say yes.
Where you put an agent on your own records, and where the agents you already use come to reach your data.
- Every action proposed, never fired blind
- Answers cite the record they came from
- MCP keys let your other agents in, on your permissions
- Built on the eve runtime
Every action proposed, never fired blind
Answers cite the record they came from
MCP keys let your other agents in, on your permissions
Built on the eve runtime
In detail
What Studio does.
Capabilities that exist today, with the gaps stated further down.
Approval first
It asks first. Always.
A lead has asked about payment terms twice and heard nothing for three days. The agent notices, and instead of acting quietly it puts a proposal in front of you: set the response to needs pricing, then draft the follow-up. You approve it or dismiss it. The volume is the agent's job. The judgment stays a person's.
- Confirm before execute, on every action
- The proposal shows its reasoning
- Dismissing costs one click and teaches you nothing to fear
This lead asked about payment terms twice and has not had a reply in three days.
Set response to needs pricing, then draft the follow-up.
Grounded
Your records are its whole world.
The agent reads your leads, deals and notes, not the open internet. Its answers stream back with citations to the records they came from, and it sees exactly what its permissions allow, the same rules that apply to a person.
- Streamed answers with citations to the record
- Chat history retained
- Scoped by the same permissions as the rest of the suite
Arlene went quiet after the price revision on 12 March. Her last two messages both asked about the payment schedule.
Open
Your other agents get a key.
Your team already works inside other assistants. Mint an MCP key and those agents reach your records directly, with the key's permissions, instead of someone copying data between tabs. Revoke it and the door closes.
- MCP keys, minted and revoked by you
- Runs on the eve runtime
- A marketing agent with visible tool use
created 4 Mar · read leads, deals
created 11 Mar · read leads
Not yet
What is missing.
Studio is in beta. These are the parts that are not built, listed here rather than discovered in a demo.
- A visual agent builder. Today the agent is configured, not composed on a canvas.
- Multi-agent orchestration. One agent at a time, doing one job.
- An agent marketplace.
- A broad action library. In the CRM the agent currently writes notes and sets lead responses. More actions are being added.
Better together
Studio works with the rest.
Everything writes to the same customer record, so adding a second product does not mean a second migration.
Numbers that explain themselves.
See IntelligenceA pipeline that fills itself.
See DataThe whole suite
One login, one record, one bill.
Questions
Studio, specifically.
The streaming, the citations and the approval flow are real. The action library is small and the builder is not finished, so we label it.
In the CRM it answers questions with citations, writes notes to a lead and sets a lead's response status, always through an approval step. The marketing agent has a wider set of tools.
Not today, and that is a design choice rather than a missing feature. Confirm-before-execute is the whole safety model.
Through an MCP key you mint and can revoke, scoped by the same permissions as a person.
See Studio on your own data.
Thirty minutes, your records, no slides.