Build agents your way,
and run them on Dome or bring your own.
Define agent apps on Dome or register the ones you already run. Give each a gateway to work through and a trigger to start it.
Agents
The registered identity of an agent. Name, owner, declared capabilities and a lifecycle: provisioned, active, suspended, revoked. The key issued at registration is the root of trust for every call. Revoke the agent and every call stops.
support-triagecs-prodActive
OwnerMCMaya Chen
Key
dome_at_…4f2aRegister a named agent
Create the identity your team will grant access to.
zendesk/read_ticket
support-triageacts forMPmaya.patel
Caller
Okta · OIDC
DecisionAllow
Auditsupport-triage for maya.patel
Represent who it acts for
Connect an agent action to a verified caller when delegation is required.
support-triageSuspended
StatusActiveSuspended
10:45prod-reasoningDeny · suspended
10:44zendesk/read_ticketDeny · suspended
Suspended by Maya Chen
10:42zendesk/update_ticketAllow
10:41zendesk/read_ticketAllow
10:38prod-reasoningAllow
10:36zendesk/searchAllow
Change its access state
Suspend an agent and deny its new requests until it is reactivated.
dome — bash
dome agents register --name support-triagedome agents create-key support-triage --name prodGateways
The named access surface you create and grant. A gateway composes tools and model pools into one endpoint an agent is granted as a unit. Gateways are logical, so make as many as your estate needs. A resource in no gateway is unreachable.
support-prod
gw.dome.example/support-prod
Behind this endpoint3Add
prod-modelsPool
zendeskTool
githubTool
prod-modelsPoolbilling-apiTooleval-modelsPool
Compose tools and pools
Put the tools and model pools an agent needs behind one endpoint.
support-triage
support-prod
zendesk
github
prod-models
billing-api
Grant it as a unit
Grant an agent the gateway and it reaches what the gateway holds. Nothing else is reachable.
support-devdevSupport
support-prodprodSupport
sales-assistprodSales
legal-reviewprodLegal
New gatewayfinance-prodprodFinance
New gatewayeval-sandboxdevML
it-helpdeskprodIT
New gateway
ml-batchdevML
Make as many as you need
Gateways are logical. Give each team, environment or app its own.
dome — bash
dome gateway create support-proddome gateway tool-sources add support-prod zendeskdome gateway model-pools add support-prod prod-modelsdome gateway access grant support-prod support-triageTriggers
A schedule, a webhook, or a manual run. A trigger decides when a managed agent runs. A schedule fires on a cron in your time zone, a webhook fires on a signed POST, and anyone with access can run an agent now. Every fire queues a run, and nothing is dropped.
0 2 * * *America/New_YorkSun02:00
Mon02:00
Tue02:00
Wed06:12
Thu02:00
Fri02:00
Sat02:00
Missed runs: run the newest, late
Run on a schedule
A cron in the time zone you choose. Missed runs catch up the way you set.
Deliveries
invoice.failedbilling-svc · signature validRun started
Run from a webhook
A signed POST from GitHub, Zendesk or your own service starts a run.
Running · cap 1Waiting
nightlystarted 02:00
issue-openedstarted 02:05
issue-openedfired 02:041stQueued
issue-openedfired 02:092ndQueued
Queue, never drop
Cap how many runs go at once. A fire past the cap waits its turn.
dome — bash
dome triggers create \ --name nightly --kind schedule \ --cron "0 2 * * *" --timezone America/New_York \ --target nightly-triage