Plan validation
Plans are checked before they run: risky steps without an approval gate, bad tool restrictions or missing undo plans fail at plan time, not mid-mission.
Describe a job in plain language. Agent Harness builds the agent, picks the right model for each step, gives it tools, a browser and a sandbox, and runs it behind permissions, budgets and an audit trail.
An agent harness is the runtime around a model that turns it into a dependable worker: it supplies tools, memory and knowledge, routes each request, enforces permissions and budgets, verifies results and records what happened. Insiro Agent Harness provides all of that so teams build agents instead of infrastructure.
Explain the task the way you would to a new hire. Insiro drafts the agent: steps, tools, knowledge sources, model and schedule, ready to test in a side-by-side preview.
A front-door router classifies each request into one of eight intents, weighs reasoning, quality, modality, complexity, cost and task type, then picks the model. Click a request, or change the model controls.
Below 70% confidence or with a missing entity, the agent asks ("Who should I send this to?") instead of guessing.
Multi-step requests split into ordered sub-tasks, and apps you still need to connect are flagged up front.
Tool ranking gets a small, capped nudge from verified outcomes in your organisation.
Agents work from a personal graph and an enterprise graph: people, projects, customers, data and documents, linked by how they actually relate. Hover a name in the answer to see the connection behind it.
Show work · 3 sources
Yes. Two efforts overlap and don't seem to know about each other. Start with:
Agent Harness runs every multi-step job as a mission: an objective, acceptance criteria, a cost ceiling, a versioned plan and verified progress.
Plans are checked before they run: risky steps without an approval gate, bad tool restrictions or missing undo plans fail at plan time, not mid-mission.
Each task attempt gets a short-lived, revocable token bound to its user, mission and tools. Child agents can never get wider access than their parent.
Each task's output is verified before downstream tasks use it, and the mission produces an acceptance report against your criteria.
Side-effecting steps declare how to reverse them. If a mission fails mid-way, Insiro can roll back what it changed.
When reality changes, the agent proposes a typed patch to its plan. Every plan version is kept with the reason it changed.
Server-derived intent keys mean a retried step never sends the same email or creates the same ticket twice.
Turn on Teach mode and do the task yourself in Insiro's cloud browser. Insiro records the steps, the apps and what to avoid, and saves it as a skill agents can run on demand.
Meeting prep
Brief on attendees, history and talking points
Deal desk check
Validate discount and terms against policy
Quarter-close checklist
Run the 18-step close and flag blockers
Invoice triage
Match bills to POs, route exceptions
PR reviewer
Review for tests, security and style
Incident commander
Open the war room and timeline
Refund triage
Investigate claims against policy
Brand voice reply
Draft replies in your tone
Example skills. Teach your own by demonstration, then share them like a document.
When a site has no API, the agent opens its own cloud browser that you can watch live and take over at any point. When a task means thousands of rows, it writes and runs code in an isolated sandbox.
Agents never call tools directly. They ask the Insiro gateway, which checks the request, brokers the user's own credentials, reserves cost and writes evidence, in this order, every time.
You can assemble an agent stack from a framework, a vector database, an observability tool and a proxy. Or you can start with one that is already governed.
| Capability | Insiro Agent Harness | DIY agent framework | Copilot agent builders |
|---|---|---|---|
| Time to first governed agent | Same day, no code | Weeks of platform work | Fast, limited actions |
| Multi-model routing with BYOK | Intent and cost based | You write the router | Single vendor model |
| Risk tiers and exact-action approvals | Built in | Build it | Basic confirmations |
| Task-scoped capability tokens | Bound, revocable, cascading | Build it | Not exposed |
| Cloud browser with human takeover | Live view, takeover, safe defaults | Add a browser service | Rare |
| Isolated code sandbox with supply-chain checks | Egress allowlist, package policy | Add a sandbox vendor | Limited |
| Rollback of side effects | Compensation plans | Build it | No |
| Hash-chained audit evidence | Fail-closed | Build it | Activity logs |
An agent harness is the runtime around a model that turns it into a dependable worker: it supplies tools, memory and knowledge, routes each request, enforces permissions and budgets, verifies results and records what happened. Insiro Agent Harness provides all of that so teams build agents instead of infrastructure.
Insiro routes across Insiro-hosted models and models from OpenAI, Anthropic Claude and Google Gemini. Organisations can bring their own API keys (BYOK), set a default model per agent or teammate, and let the router pick a fast, reasoning or coding model per request based on intent and cost.
Yes. Agent Harness imports agents from OpenAI Assistants, Claude and Gemini configurations or a JSON definition, keeping their instructions and mapping their tools to Insiro connectors. Imported agents immediately run under the same governed gateway, budgets and audit trail as native agents.
Every planned action is classified into four risk tiers. Tier 0 and 1 run immediately; tier 2 needs user confirmation; tier 3 needs owner approval and the user's own credentials. Plans containing risky steps are rejected unless they include an approval gate, and each agent carries a task-scoped capability token that limits tools and arguments.
Skills are reusable procedures taught by demonstration. You perform a task once in Insiro's cloud browser, Insiro records the steps, apps and guardrails, and agents can then run that skill on request or automatically when relevant. Skills can be shared with people, groups or the whole organisation.
Yes. Agents run code in an isolated sandbox with an egress allowlist, package policy and vulnerability scanning, and a coding agent gets a full development workspace per run. Results come back as files, tables or answers; destructive commands such as rm -rf or terraform destroy are classed tier 3 and need approval.
A 30-minute working session: we connect one data source and one app, then run a governed agent on a task you choose.