Skip to content

docs: name the agentctl job variable and workspace flag as they are #4686

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Sinity wants to merge 1 commit into from
+2 −2
Closed

docs: name the agentctl job variable and workspace flag as they are #4686

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions TESTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ share one workstation, so `devtools test` and the pytest step of

`POLYLOGUE_PYTEST_SLOT=held` is the explicit assertion that the caller already
holds the slot. Only the pytest-group runner may set it during normal
execution. Generic `SINNIXD_JOB_ID` does not grant slot ownership.
execution. Generic `AGENTCTL_JOB_ID` does not grant slot ownership.

### Typed WebUI package checks

Expand All @@ -70,7 +70,7 @@ For the managed deployed-reader browser smoke, use the declared AgentCTL
operation:

```bash
agentctl job start polylogue deployment_browser_smoke --workspace <workspace-id>
agentctl job start polylogue deployment_browser_smoke --workspace <path>
```

### First-party browser credential journey
Expand Down
Loading