Project
Project bundles agents and steps to carry out work. In the Marketplace edition, you place and run agents registered by an administrator (registered agents) on the steps. In a workflow, each run is a case: it holds its settings and artifacts as versions, and a step where a person decides checks them before the work goes on.
The ideas are the same as in the SaaS edition. This section covers only what differs in the Marketplace edition. Read Project in the SaaS edition for the shared ideas, and check the differences in the SaaS Edition Mapping Reference.
Run something small
Place a registered agent and take your first case through.
→Use registered agents
What can be placed, the step settings, and what the agent receives.
→Look up the differences from SaaS
How to read each page of the SaaS edition.
→Understand the shared mechanics
Steps, reviews and records are explained in the SaaS edition.
→Main differences from the SaaS edition
| SaaS edition | Marketplace edition | |
|---|---|---|
| Agents placed on steps | Users create them in the project (goal (instructions), guardrails, playbook, skills) | Container agents an administrator registered in the admin console. They are not created in the project, and their contents are not changed there |
| What it takes to place one in a workflow | It has a goal (instructions) | An administrator has registered a contract and it is certified |
| What you change per step | (You fix the agent) | The step settings (parameters, connections, input bindings) / environment variables (cycles) |
| Hand-over between steps | The output of the previous step passes to the next step | It passes only when you bind the files |
| Running a workflow | “Run now” | “Start case”. Settings and artifacts are held as versions |
| Shape of a workflow | It can divide into lanes and run them at the same time | Serial only |
| Review method | Stop and wait for a decision / Notify and proceed after the deadline | Stop and wait for a decision / External wait (a GitLab MR being merged). The deadline does not decide it |
| Ways to start | Manual, time, external API, email | Manual, time, external API (no email) |
| Creating with AI, consulting on improvements | Available | Not available |
| Project memory | Available | Not available |
| Execution rules | The basic rules and forbidden operations act on the run | The basic rules decide whether it can start (workflows). Outbound traffic is restricted with NetworkPolicy and “Banned URL” in the admin console |
How a project is built
A project has steps, and you place registered agents on those steps. What a registered agent does is settled by its container image and by the contract an administrator registered. A step where a person decides holds no agent: a reviewer looks at the case's artifacts and settings and decides.
| Term | Meaning |
|---|---|
| Registered agent | An agent an administrator registered under “Agent Settings” in the admin console. It runs as a container image built with the SDK |
| Contract | The agreement on the parameters, files, artifacts and connections a registered agent receives, its effect on external systems and its execution limit. Only agents used in workflows have one |
| Certification | The contract has, all in place, the SDK version, adapter version, image digest, test results and supported execution rules confirmed by testing. Only certified agents can be placed in a workflow |
| Step settings | The parameters, connections and input bindings set for each placement in a workflow, within the range of the contract |
| Case | One run of a workflow with registered agents placed. It holds its settings and artifacts as versions |
| External wait | A review method that moves on to the next step according to the state of an external service (a GitLab MR being merged) |
The other terms (step, placement, review step, run record, execution rules, ledger) are the same as in the SaaS edition (How a project is built).
How you use it
Register the agent
Register it under Agent Settings, and add a contract and certification if it is used in workflows.
Allow traffic
If the agent uses external services, allow the destinations.
Place it on steps
Place registered agents and enter the step settings.
Take cases forward
Start a case, and move it on at review steps after looking at the versions.
Look at the record
Choose what to fix from the run records and metrics.
Where to read at each stage.
- Register the agent — Settings Guide (administrators), Workflow Guide (agent developers)
- Allow traffic — Execution Rules and Traffic Guide
- Place it on steps — Agent Guide; how to divide the work is in the SaaS edition's Design Guide
- Take cases forward — Case Guide, Review Guide, Trigger Guide
- Look at the record — Record Guide
Where things are in the UI
The project screen's tabs are the same as in the SaaS edition (Overview, Execution history, Workflow history, Settings). In the Marketplace edition, the following differ.
| Where | Difference |
|---|---|
| Top of the project list | There is no “Agents” tab (Home, Projects, Insights) |
| “Add Agent” in the editor | The list switches to the list of registered agents |
| Top of the project screen | In a workflow with registered agents placed, “Start case” instead of “Run now” |
| Workflow history, run record | “Case details” leads to the case screen (progress, settings, files, records) |
| Settings ＞ Triggers and notifications (“Triggers” in a cycle) | There is no starting by email |
| Settings ＞ Connectors | There is an “External-wait webhook secret” (workflows) |
Projects can also be used through the external API. Only the endpoints called with a service account token are available (API Reference).
Quickstart
Workflow
Place registered agents on steps, start your first case, and take it through review.
→Cycle
Have a registered agent used in chat sweep on a schedule, look at the results, and stop it.
→Guides
- Agent Guide — the agents you can place, step settings and environment variables, and what the agent receives
- Case Guide — starting a case, versions of settings and artifacts, and cancelling
- Review Guide — the deadline does not decide, and external waits
- Trigger Guide — how starting differs, cycle sweeps and webhooks, and when it does not go to plan
- Execution Rules and Traffic Guide — where execution rules apply, and how to restrict outbound traffic
- Record Guide — the runtime image, unmeasured results, and why a run could not be launched
References
- SaaS Edition Mapping Reference — how to read each page and section of the SaaS edition
- Settings Reference — the values fixed in the Marketplace edition
- Glossary — the words that appear only in the Marketplace edition