Osy#betaRun it on Osyrin: osyrin.com

Reference / Agent

Osysharp.Agents.Processes — an agent's work as a step of a business process, seen from both sides

`Osysharp.Agents.Processes` is the bridge between agents and processes: each piece of an agent's work given in a run is told on that run, and the page of a piece of work says which run it is a step of.

previewagentsguidekit

Source on GitHub: Osysharp.Agents.Processes — github.com/osysharp/agents/processes ↗

You are here: Building with agents › The kits › Agents.Processes

Summary#

Osysharp.Agents.Processes is the bridge between agents and processes: each piece of an agent's work given in a run is told on that run, and the page of a piece of work says which run it is a step of.

The step itself is an ordinary call in the workflow. The bridge adds the telling, and the money: every model call of the step is charged to the run, and a limit set for each run stops a step that would pass it.

PackageOsysharp.Agents.Processes, version 1.1.0
You add it withNothing. It arrives by itself in an app that uses [[agent-kit-agents|Agents]] and [[agent-kit-processes|Processes]]; osy lock says so. without Osysharp.Agents.Processes; in the manifest keeps it out.
It sits on[[agent-kit-agents|Agents]], [[agent-kit-agents-inspector|Agents.Inspector]], [[agent-kit-llm|Llm]], [[agent-kit-processes|Processes]]
It also usesIdentity, Ui — parts of the platform's own library
Its own test appThe procurement office of a tool maker, qualifying a new supplier — kits/agents-processes/tests

Description#

What do you get without writing anything?#

  • A line on the run for each step: given, waiting on a person, finished, failed, stopped.
  • A step opened in place on the run's page, as the whole inspector.
  • A run listed from its first agent step, with nothing written in the workflow.
  • "Agent work in this run", with what each piece cost.

When do you need it?#

Shape 3. It arrives by itself.

What does it expose?#

The tables below are generated from the kit itself, not written by hand: osy kits Osysharp.Agents.Processes --surface lists each of them with the code of the kit's own test app that uses it, and the tests that show it working.

Functions you call, those its own tests show most first.

FunctionWhat it doesTests that show it
AgentWorkSubject()What a line of a run is about when it is about an agent's piece of work: the receipt, by its id.2
AgentWorkInRun(Guid run)The agent work given in a run, in order — each piece the run itself gave, with the state that gave it, how it ended and what it cost with the work it handed on.2
ProcessRunOfWork(Guid task)The run a piece of work is a step of.2

Screens and components you mount — each is one line in a page of yours.

ComponentWhat it draws
AgentStepOpened(kind, subject)A line of a run that is about an agent's piece of work opens as the whole inspector, in place.
AgentWorkOfRun(run)The agent work given in a run, with what each piece cost — under the run's history.
RunOfThisWork(task)On a piece of work's own page: the run it is a step of, and the way to it.

Go deeper#

Related

The map of the kits — which sits on which, and what each one is for

The agents family is 29 kits. Two are under everything: `Osysharp.Llm` for every model call and `Osysharp.Agents` for…

Agents in business processes — an agent's work as a step of a workflow, told on the run (Agents.Processes kit)

An agent's work is a step of a business process by being called from the process's workflow: an awaited call in a…

Processes — every run of a business process, listed and read from start to now (Processes kit)

Osysharp.Processes makes the runs of an app's workflows followable by the people who answer for them. The app names…