You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .changeset/project-playground-debugger.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,6 @@
4
4
"@openagentpack/cli": minor
5
5
---
6
6
7
-
Replace the fixed Playbook showcase with an `agents.yaml`project debugger. Playground now watches project inputs, performs fingerprint-protected per-Agent Plan and Apply operations, streams operation and Session events, and manages explicit temporary attachment cleanup without mutating YAML or Deployment declarations.
7
+
Replace the fixed Playbook showcase with project-aware debugging. `agents playground` remains a read-only `agents.yaml`Session Preview, while `agents project workbench`watches and edits a directory project, performs fingerprint-protected Build/Plan/Publish operations, streams operation and Session events, and manages explicit temporary attachment cleanup.
8
8
9
-
Add SDK source-path tracking, runtime-scoped Agent planning, stable plan fingerprints, and stale-plan enforcement. The CLI now launches Preview with `agents playground -f/--file [--agent <id>]`, exposes the project console separately through`agents workbench`, and falls back to the diagnostic Workbench for missing, invalid, empty, or unselected multi-Agent projects; the former `playground --provider` option is removed.
9
+
Add SDK source-path tracking, runtime-scoped Agent planning, full-project planning, stable plan fingerprints, and stale-plan enforcement. Preview stays at `agents playground -f/--file [--agent <id>]`; the project console moves under`agents project workbench --project <directory>`.
Copy file name to clipboardExpand all lines: .changeset/workbench-resource-editing.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,4 +2,4 @@
2
2
"@openagentpack/playground": minor
3
3
---
4
4
5
-
Add Workbench editing and removal for existing `agents.yaml`resources with server-side YAML previews, conflict and reference protection, automatic project runtime planning, and separately confirmed Apply.
5
+
Add Workbench editing and removal for resources already present in a directory project. Agent JSON, instructions Markdown, Skill metadata/content, and project resources use server-side redacted previews, revision conflicts, reference protection, explicit Build, full-project Plan, and separately confirmed Publish.
agents project validate # validate JSON, Markdown, skills, and local files
82
+
agents project build --dry-run # preview organization and generated YAML
83
+
agents project build -y # freeze the current source into a Build
84
+
agents project publish -y # publish exactly that Build and record a version
85
+
agents project workbench#edit and debug the same directory project
86
86
```
87
87
88
-
Run `agents playground -f agents.yaml` to open an Agent directly in Preview; single-Agent projects are selected automatically, while multi-Agent projects accept `--agent <id>` or open the Workbench for selection. Use `agents workbench -f agents.yaml` to open the project console without creating a Session. Playground reads every Agent and Provider from YAML and watches local dependencies. In the Workbench, Resources can edit or remove existing Agent, Environment, Skill, Vault, Memory Store, and File declarations through a server-generated YAML Diff; saving updates `agents.yaml` and automatically refreshes the project Plan. Local versions remain absent until the user explicitly enables them in the project-level Versions tab or with `agents version enable`. When enabled, a successful Apply versions changed YAML; the Versions tab uses the same switch as `agents version enable|disable`, browses history, and restores historical YAML as a forward working-tree change.
88
+
Directory projects keep global settings in `project.json`, each Agent under `agents/<id>/`, Agent instructions in `instructions.md`, and local Skill source either beside its Agent or under the shared `skills/` directory. Build promotes a Skill to the shared directory when multiple Agents reference it and deterministically writes `.openagentpack/build/agents.yaml`. Publish never runs Build implicitly.
89
89
90
-
The CLI exposes local history through `agents version status|enable|disable|list|preview|restore`. Workbench and CLI share one local switch per `agents.yaml`: `agents version enable` creates a baseline when needed and enables successful Apply versions in both hosts, while `version disable` disables them in both. `store.json` contains only the switch and head; immutable linked entries live under `entries/`, and complete YAML lives in content-addressed `blobs/`, so Git is not required. Restore writes historical YAML into the working tree without changing version history. Neither `agents.state.json` nor referenced files are included. Deployment and Channel declarations stay read-only and are excluded from Workbench project Apply. Missing or invalid projects open the diagnostic Workbench.
90
+
Workbench and CLI share `agents project version status|enable|disable|list|preview|restore`. Versions are Git-independent full source-tree snapshots: immutable manifests point to content-addressed text and binary blobs, while `.openagentpack/state.json` is always excluded. Restore writes a historical tree forward into the working directory without moving version history or remote State. Deployment and Channel declarations remain read-only in Workbench but participate in full project Publish.
91
+
92
+
The original YAML workflow remains available through `agents init`, `validate`, `plan`, `apply`, and `destroy`. `agents playground -f agents.yaml` continues to open a YAML Agent Session Preview, but YAML Apply no longer creates project versions and cannot be used inside a directory-project root.
91
93
92
94
▶ [Watch the full Playground demo](https://github.com/user-attachments/assets/bf51b8d8-f2ed-464b-bca9-0709fefcc44d)
93
95
@@ -175,29 +177,31 @@ The [`examples/`](./examples) directory has runnable configs for every provider,
175
177
176
178
## Using the SDK
177
179
178
-
Cloud project runtime capabilities are available programmatically from `@openagentpack/sdk`; Node-only local project versions are provided separately by `@openagentpack/project-versions`:
180
+
Cloud runtime capabilities are available from `@openagentpack/sdk`. Directory compilation, Build/Publish, and full-tree versions are exposed by `@openagentpack/project-workspace`, backed by the storage primitives in `@openagentpack/project-versions`:
179
181
180
182
```ts
181
-
import { resolveProjectConfig, planProjectContext } from "@openagentpack/sdk";
182
-
import { createProjectVersionService } from "@openagentpack/project-versions";
See the [SDK reference](./docs/reference/sdk.md) for the public API surface.
190
194
191
195
## WebUI
192
196
193
-
`apps/webui` is a Vite single-page project workbench for inspecting and debugging the Agents declared in `agents.yaml`; `apps/server` exposes the SDK over an OpenAPI surface. Run both from the repo root:
197
+
`apps/webui` is a Vite directory-project Workbench; `apps/server` exposes directory editing, Build/Publish, versions, and Session debugging over an OpenAPI surface. Run both from the repo root with `AGENTS_PROJECT_ROOT` pointing at a project:
194
198
195
199
```bash
196
200
bun install
197
201
bun run dev # server + webui together
198
202
```
199
203
200
-
Or launch the packaged local UI with `agents playground -f <path/to/agents.yaml>` for Preview or `agents workbench -f <path/to/agents.yaml>` for the project console. Provider, model, tools, memory, skills, and resources come from YAML; the UI does not override them. Deployment declarations are displayed read-only.
204
+
Launch the packaged project console with `agents project workbench --project <directory>`. Use `agents playground -f <path/to/agents.yaml>` only for the legacy YAML Session Preview. Workbench edits directory source, requires an explicit Build, and publishes the reviewed Build; it never edits Provider ownership or pushes Git state.
0 commit comments