agent:server
Local or deployed Node service that proxies authenticated runs to your workspace—pair with npm run collab:server for live UI sync.
Run agents from your stack: start npm run agent:server, stream tokens and tool events, track jobs, and stop or retry runs. Complements Public API v1 (billing, catalog) with execution-focused endpoints documented in API_АГЕНТОВ.md.
Ṣe okeere awọn metiriki osẹ · Aṣoju iwadii
Awọn imudojuiwọn iwe igbimọ iṣẹ-ṣiṣe lakoko ti iṣẹ naa nṣiṣẹ — ẹgbẹ rẹ rii ipo kanna ni UI.
Fi iṣẹ ranṣẹ si oluranlowo lati ita ẹrọ aṣawakiri. Digio streams awoṣe ati iṣẹ ṣiṣe irinṣẹ, tọpa iṣẹ naa, ati tọju kanban ati Lati ṣe ni amuṣiṣẹpọ — nitorinaa awọn oniṣẹ kii ṣe laro ohun ti o ṣẹlẹ.
Aṣoju iwadi
Ṣe akopọ awọn iyipada opo gigun ti epo fun olori
Atoju 8Ṣiṣẹ lẹgbẹẹ aaye iṣẹ ti ẹgbẹ rẹ ti lo tẹlẹ — ko si eto iṣẹ ṣiṣe ti o jọra lati ṣetọju.
Create a Digio team, hire agents, and issue a workspace API key with the scopes you need. Keys stay on your servers—see security for isolation and rotation.
Fi iṣẹ-ṣiṣe ranṣẹ si aṣoju ti o fẹ-ọrọ kanna ti iwọ yoo fi si Lati ṣe. Ṣe alabapin si ṣiṣan ifiwe tabi ipo iṣẹ ibo titi ti ṣiṣe yoo pari.
Deliverables land in Done on the task board; teammates can review in chat or trigger the next job from your app.
POST a task payload to an agent, subscribe to SSE or WebSocket streams, and correlate responses with kanban columns. Ideal for integrators who already use Digio workspaces but need headless automation.
Local or deployed Node service that proxies authenticated runs to your workspace—pair with npm run collab:server for live UI sync.
Consume partial model and tool events as they arrive—build your own dashboards without polling chat history.
List active jobs, inspect status, stop a run, or retry with the same standing-task id—mirrors buttons in the workspace UI.
Workspace keys and roles keep automation inside the team boundary you choose—paired with Digio’s security model.
Katalogi, awọn agbegbe, apamọwọ, ati awọn iṣiro lilo — lo lẹgbẹẹ Agent API fun awọn UI ti o mọ ìdíyelé. Integrations awotẹlẹ.
Each agent runs with the skills you enabled—CRM, code, research, and more—without redeploying your integration.
Ṣe adaṣe awọn imudani ti o ṣapejuwe tẹlẹ ninu awọn iwe-iṣere-lakoko ti eniyan duro ni lupu lori igbimọ ati ni iwiregbe.
Jẹ ki awọn alabara beere iwadii tabi awọn atunwo atunwo lati inu ohun elo rẹ—Digio n ṣakoso aṣoju ati da ipo UI rẹ le ṣafihan ni akoko gidi.
Awọn ọja okeere ni alẹ, awọn ọlọjẹ oludije, ati awọn sọwedowo ilera lori iṣeto kan-awọn iṣẹ ṣiṣe ti o duro pẹlu awọn okunfa API jẹ ki awọn ila kun laisi abojuto ọmọ-ọwọ.
Ṣii PR docs kan, ṣe akopọ itusilẹ kan, tabi awọn titaniji ipin nigbati ipele opo gigun ti epo ba pari — tun gbiyanju tabi da duro lati id iṣẹ kanna ti ṣiṣe ba lọ.
Jeki adaṣe adaṣe ni igbẹkẹle bi o ṣe ṣafikun awọn aṣoju, awọn agbegbe, ati awọn eto isale.
Separate keys per environment — staging and production workspaces never share the same secret.
Link standing tasks — reuse the same task id for retries so kanban history stays coherent.
Surface status in your UI — stream events to operators; they can still open team chat for nuance.
Stop long runs early — cancel from your app when upstream data changes mid-job.
So adaṣiṣẹ pọ si iyoku aaye iṣẹ Digio rẹ.
Read API_АГЕНТОВ.md, start agent:server, and run your first headless task against a dev workspace.