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.
Thekelisa amamethrikhi anjalo ngeviki · Umenzeli wocwaningo
Izibuyekezo zekholomu yebhodi lomsebenzi ngesikhathi umsebenzi usaqhubeka—ithimba lakho libona isimo esifanayo ku-UI.
Thumela umsebenzi kumenzeli ongaphandle kwesiphequluli. Imodeli ye-Digio streams nomsebenzi wamathuluzi, ilandelela umsebenzi, futhi igcina i-kanban nokuthi Ukwenziwa kuvumelanisiwe—ukuze ama-opharetha angalokothi aqagele ukuthi kwenzekeni.
I-ejenti yocwaningo
Fingqa izinguquko ezihamba phambili zobuholi
Okubalulekile 8Isebenza eduze kwendawo yokusebenza ithimba lakho eselivele liyisebenzisa—ayikho isistimu yomsebenzi ofanayo okufanele inakekelwe.
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.
Thumela umsebenzi kumenzeli omfunayo—umbhalo ofanayo ongawabela Ukwenza. Bhalisela ukusakaza bukhoma noma isimo somsebenzi wenhlolovo kuze kuqedwe ukuqalisa.
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.
Ikhathalogi, izifunda, isikhwama semali, nezilinganiso zokusetshenziswa—sebenzisa kanye ne-API yomenzeli kuma-UI aqaphela ukukhokha. Ukuhlanganiswa uhlolojikelele.
Each agent runs with the skills you enabled—CRM, code, research, and more—without redeploying your integration.
Yenza ngokuzenzakalela ukunikezwa osuvele ukuchaza ezincwadini zokudlala—ngenkathi abantu behlala benolwazi ebhodini nasengxoxweni.
Vumela amaklayenti acele ucwaningo noma abhale izibuyekezo kuhlelo lwakho lokusebenza—I-Digio iphethe umenzeli futhi ibuyisela isimo i-UI yakho engasibonisa ngesikhathi sangempela.
Ukuthunyelwa kwansuku zonke, ukuskena okuqhudelana naye, nokuhlolwa kwezempilo kushejuli—imisebenzi emile kanye nezibangeli ze-API kugcina imigqa igcwele ngaphandle kokugada ingane mathupha.
Vula i-PR yamadokhumenti, finyeza ukukhishwa, noma sebenzisa izexwayiso lapho isigaba sepayipi siqeda—zama futhi noma yeka ku-id yomsebenzi ofanayo uma ukugijima kukhukhuleka.
Gcina okuzenzakalelayo kuthembekile njengoba wengeza ama-ejenti, izindawo ezizungezile, namasistimu aphansi komfula.
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.
Xhuma okuzenzakalelayo kuyo yonke indawo yakho yokusebenza ye-Digio.
Read API_АГЕНТОВ.md, start agent:server, and run your first headless task against a dev workspace.