agl 42.2.2 → 43.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/changelog.md +24 -0
- package/dist_serve/bundle.js +6697 -5287
- package/dist_serve/bundle.js.map +2 -2
- package/dist_serve/bundle.js.third-party-notices.json +29 -29
- package/dist_serve/bundle.js.third-party-notices.txt +29 -29
- package/dist_serve/third-party-notices.md +597 -8
- package/dist_ts/00_commitinfo_data.js +1 -1
- package/dist_ts/aglapi/aglapisurface.document.js +114 -16
- package/dist_ts/aglapi/interfaces.d.ts +30 -0
- package/dist_ts/aglapi/interfaces.js +7 -1
- package/dist_ts/classes.authstore.d.ts +7 -0
- package/dist_ts/classes.authstore.js +12 -1
- package/dist_ts/classes.browserpainttransport.d.ts +2 -2
- package/dist_ts/classes.browserpainttransport.js +9 -8
- package/dist_ts/classes.browserresourcehost.js +30 -20
- package/dist_ts/classes.cli.js +10 -1
- package/dist_ts/classes.controller.d.ts +41 -11
- package/dist_ts/classes.controller.js +232 -52
- package/dist_ts/classes.harnessoperationmanager.d.ts +44 -0
- package/dist_ts/classes.harnessoperationmanager.js +15 -10
- package/dist_ts/classes.mcpclient.d.ts +5 -0
- package/dist_ts/classes.mcpclient.js +15 -3
- package/dist_ts/classes.mcpcontrollerhost.d.ts +3 -0
- package/dist_ts/classes.mcpcontrollerhost.js +17 -3
- package/dist_ts/classes.mcptools.d.ts +4 -3
- package/dist_ts/classes.mcptools.js +20 -1
- package/dist_ts/classes.mcpvalidation.js +4 -1
- package/dist_ts/classes.ticketstore.d.ts +71 -3
- package/dist_ts/classes.ticketstore.js +299 -12
- package/dist_ts/classes.validation.d.ts +2 -0
- package/dist_ts/classes.validation.js +27 -5
- package/dist_ts/driver/classes.directreports.d.ts +23 -3
- package/dist_ts/driver/classes.directreports.js +59 -2
- package/dist_ts/driver/classes.drivereventrelay.js +3 -2
- package/dist_ts/driver/functions.driverinstructions.d.ts +1 -1
- package/dist_ts/driver/functions.driverinstructions.js +12 -3
- package/dist_ts/driver/functions.drivertools.d.ts +4 -0
- package/dist_ts/driver/functions.drivertools.js +8 -2
- package/dist_ts/fleet/classes.boardpump.d.ts +53 -3
- package/dist_ts/fleet/classes.boardpump.js +237 -32
- package/dist_ts/fleet/classes.claudeworkers.d.ts +10 -3
- package/dist_ts/fleet/classes.claudeworkers.js +43 -19
- package/dist_ts/fleet/classes.codexworkers.d.ts +5 -3
- package/dist_ts/fleet/classes.codexworkers.js +26 -9
- package/dist_ts/fleet/classes.deploymonitor.d.ts +253 -0
- package/dist_ts/fleet/classes.deploymonitor.js +821 -0
- package/dist_ts/fleet/classes.gitfacts.d.ts +61 -0
- package/dist_ts/fleet/classes.gitfacts.js +125 -0
- package/dist_ts/fleet/classes.releasereconciler.d.ts +51 -0
- package/dist_ts/fleet/classes.releasereconciler.js +101 -0
- package/dist_ts/fleet/classes.service.d.ts +13 -1
- package/dist_ts/fleet/classes.service.js +76 -7
- package/dist_ts/fleet/classes.ticketeffects.d.ts +13 -0
- package/dist_ts/fleet/classes.ticketeffects.js +42 -8
- package/dist_ts/fleet/classes.workers.d.ts +10 -3
- package/dist_ts/fleet/classes.workers.js +18 -3
- package/dist_ts/fleet/functions.controllerbuild.d.ts +23 -0
- package/dist_ts/fleet/functions.controllerbuild.js +75 -0
- package/dist_ts/fleet/functions.deployprobes.d.ts +39 -0
- package/dist_ts/fleet/functions.deployprobes.js +82 -0
- package/dist_ts/fleet/functions.deployvalidation.d.ts +27 -0
- package/dist_ts/fleet/functions.deployvalidation.js +43 -0
- package/dist_ts/fleet/functions.release.d.ts +2 -1
- package/dist_ts/fleet/functions.release.js +32 -5
- package/dist_ts/fleet/functions.releasefacts.d.ts +42 -0
- package/dist_ts/fleet/functions.releasefacts.js +46 -0
- package/dist_ts/fleet/functions.validation.d.ts +3 -3
- package/dist_ts/fleet/functions.validation.js +4 -7
- package/dist_ts/fleet/functions.watchprobes.js +7 -9
- package/dist_ts/fleet/functions.workervalidation.js +4 -3
- package/dist_ts/fleet/interfaces.workers.d.ts +30 -3
- package/dist_ts/fleet/interfaces.workers.js +14 -1
- package/dist_ts/functions.deploycli.d.ts +36 -0
- package/dist_ts/functions.deploycli.js +157 -0
- package/dist_ts/functions.mcpdeploytools.d.ts +13 -0
- package/dist_ts/functions.mcpdeploytools.js +16 -0
- package/dist_ts/functions.mcptickettools.d.ts +54 -0
- package/dist_ts/functions.mcptickettools.js +8 -7
- package/dist_ts/functions.ticketautolabels.d.ts +2 -0
- package/dist_ts/functions.ticketautolabels.js +9 -3
- package/dist_ts/functions.ticketcli.d.ts +16 -2
- package/dist_ts/functions.ticketcli.js +105 -27
- package/dist_ts/functions.ticketvalidation.d.ts +55 -0
- package/dist_ts/functions.ticketvalidation.js +26 -8
- package/dist_ts_interfaces/deployments.d.ts +241 -0
- package/dist_ts_interfaces/deployments.js +5 -6
- package/dist_ts_interfaces/fleet.d.ts +12 -0
- package/dist_ts_interfaces/fleetworkers.d.ts +21 -1
- package/dist_ts_interfaces/functions.fleetversion.d.ts +4 -0
- package/dist_ts_interfaces/functions.fleetversion.js +25 -0
- package/dist_ts_interfaces/interfaces.d.ts +4 -2
- package/dist_ts_interfaces/interfaces.js +4 -2
- package/dist_ts_interfaces/mcprequests.d.ts +3 -2
- package/dist_ts_interfaces/mcprequests.js +3 -1
- package/dist_ts_interfaces/requests.d.ts +3 -2
- package/dist_ts_interfaces/requests.directreports.d.ts +58 -6
- package/dist_ts_interfaces/requests.js +1 -1
- package/dist_ts_interfaces/requests.tickets.d.ts +25 -5
- package/dist_ts_interfaces/requests.tickets.js +2 -2
- package/dist_ts_interfaces/tickets.d.ts +71 -6
- package/dist_ts_interfaces/tickets.js +34 -6
- package/dist_ts_migration/classes.documentmigrationrunner.d.ts +7 -0
- package/dist_ts_migration/classes.documentmigrationrunner.js +14 -1
- package/dist_ts_migration/index.d.ts +2 -0
- package/dist_ts_migration/index.js +3 -1
- package/dist_ts_migration/v41_ticketclosedcolumn.d.ts +20 -0
- package/dist_ts_migration/v41_ticketclosedcolumn.js +118 -0
- package/dist_ts_migration/v41_ticketlinkrepos.d.ts +24 -0
- package/dist_ts_migration/v41_ticketlinkrepos.js +101 -0
- package/package.json +6 -2
- package/readme.md +308 -36
- package/third-party-notices.md +597 -8
- package/ts/00_commitinfo_data.ts +1 -1
- package/ts/aglapi/aglapisurface.document.ts +113 -15
- package/ts/aglapi/interfaces.ts +6 -0
- package/ts/classes.authstore.ts +13 -0
- package/ts/classes.browserpainttransport.ts +8 -7
- package/ts/classes.browserresourcehost.ts +38 -14
- package/ts/classes.cli.ts +9 -0
- package/ts/classes.controller.ts +244 -61
- package/ts/classes.harnessoperationmanager.ts +20 -14
- package/ts/classes.mcpclient.ts +17 -2
- package/ts/classes.mcpcontrollerhost.ts +18 -2
- package/ts/classes.mcptools.ts +21 -2
- package/ts/classes.mcpvalidation.ts +2 -0
- package/ts/classes.ticketstore.ts +312 -13
- package/ts/classes.validation.ts +28 -4
- package/ts/driver/classes.directreports.ts +58 -3
- package/ts/driver/classes.drivereventrelay.ts +2 -1
- package/ts/driver/functions.driverinstructions.ts +11 -2
- package/ts/driver/functions.drivertools.ts +10 -2
- package/ts/fleet/classes.boardpump.ts +235 -28
- package/ts/fleet/classes.claudeworkers.ts +36 -15
- package/ts/fleet/classes.codexworkers.ts +24 -7
- package/ts/fleet/classes.deploymonitor.ts +854 -0
- package/ts/fleet/classes.gitfacts.ts +135 -0
- package/ts/fleet/classes.releasereconciler.ts +103 -0
- package/ts/fleet/classes.service.ts +81 -8
- package/ts/fleet/classes.ticketeffects.ts +38 -6
- package/ts/fleet/classes.workers.ts +19 -5
- package/ts/fleet/functions.controllerbuild.ts +84 -0
- package/ts/fleet/functions.deployprobes.ts +84 -0
- package/ts/fleet/functions.deployvalidation.ts +50 -0
- package/ts/fleet/functions.release.ts +32 -3
- package/ts/fleet/functions.releasefacts.ts +74 -0
- package/ts/fleet/functions.validation.ts +3 -6
- package/ts/fleet/functions.watchprobes.ts +6 -8
- package/ts/fleet/functions.workervalidation.ts +3 -2
- package/ts/fleet/interfaces.workers.ts +23 -3
- package/ts/functions.deploycli.ts +156 -0
- package/ts/functions.mcpdeploytools.ts +18 -0
- package/ts/functions.mcptickettools.ts +7 -6
- package/ts/functions.ticketautolabels.ts +10 -2
- package/ts/functions.ticketcli.ts +100 -24
- package/ts/functions.ticketvalidation.ts +26 -7
- package/ts_interfaces/deployments.ts +194 -0
- package/ts_interfaces/fleet.ts +17 -2
- package/ts_interfaces/fleetworkers.ts +20 -0
- package/ts_interfaces/functions.fleetversion.ts +20 -0
- package/ts_interfaces/interfaces.ts +3 -1
- package/ts_interfaces/mcprequests.ts +3 -0
- package/ts_interfaces/requests.directreports.ts +52 -8
- package/ts_interfaces/requests.tickets.ts +20 -4
- package/ts_interfaces/requests.ts +6 -1
- package/ts_interfaces/tickets.ts +53 -6
- package/ts_migration/classes.documentmigrationrunner.ts +15 -0
- package/ts_migration/index.ts +2 -0
- package/ts_migration/v41_ticketclosedcolumn.ts +106 -0
- package/ts_migration/v41_ticketlinkrepos.ts +91 -0
- package/ts_web/00_commitinfo_data.ts +1 -1
- package/ts_web/elements.deployments.ts +1066 -0
- package/ts_web/elements.directreport.ts +2 -2
- package/ts_web/elements.directreportsession.ts +5 -5
- package/ts_web/elements.harnesscontrollerapp.ts +179 -13
- package/ts_web/elements.makedirectreport.ts +444 -0
- package/ts_web/elements.nativesession.ts +29 -1
- package/ts_web/elements.ticketboard.ts +74 -18
- package/ts_web/functions.deployments.ts +231 -0
- package/ts_web/functions.sessionchat.ts +2 -0
package/readme.md
CHANGED
|
@@ -1181,8 +1181,26 @@ repository, pre-rebase backups and release journal before retrying.
|
|
|
1181
1181
|
|
|
1182
1182
|
Land and release require `--ticket AGL-<n>` (`ticketKey` through MCP). Only a verified
|
|
1183
1183
|
owner or driver may submit them. A successful landing links the repository, branch and full
|
|
1184
|
-
commit SHA and moves the ticket to Landed. A
|
|
1185
|
-
|
|
1184
|
+
commit SHA and moves the ticket to Landed. A release is the remote's tag: once a verified
|
|
1185
|
+
release finished, fleet reads the remote's tag `v<version>` (`git ls-remote`) and, when it names
|
|
1186
|
+
the release commit (`tagged` in the result), links the operation's ticket and moves it to
|
|
1187
|
+
Released with the events the deploy monitor's release reconciler writes, one per published
|
|
1188
|
+
package with the repository and the tag's commit (`{ kind: 'release', package, version, repo,
|
|
1189
|
+
sha }`), or one with the repository alone for a repository that publishes no package, under the
|
|
1190
|
+
reconciler's keys, so whichever writes them first, they apply once. A release whose tag the
|
|
1191
|
+
remote does not hold releases no ticket; its ticket gets a comment saying so. The release lists
|
|
1192
|
+
as `contained` every other ticket in Landed whose landed commit in that repository (its newest
|
|
1193
|
+
branch or commit link there) is an ancestor of the release commit; the reconciler links and
|
|
1194
|
+
releases them from the remote's tag (see [Deployments](#deployments)). Each ticket and package
|
|
1195
|
+
uses its own atomic effect.
|
|
1196
|
+
|
|
1197
|
+
When the ticket has a release plan (see [Shared project tickets](#shared-project-tickets)), the
|
|
1198
|
+
release must be of the planned repository, and a planned version is checked against what
|
|
1199
|
+
gitzone plans before the tooling commit and again before anything is published: planned 40.6.0
|
|
1200
|
+
while gitzone wants 41.0.0 stops the release with "Release plan mismatch" and leaves the
|
|
1201
|
+
decision to the owner. The same check covers every landed ticket the release would ship whose
|
|
1202
|
+
plan names another version, and a release whose own ticket's newest commit in the repository is
|
|
1203
|
+
not on main stops before publishing too: it would not hold the ticket's work.
|
|
1186
1204
|
Native completion remains separate from `ticketSync`: a ticket refusal or unknown commit
|
|
1187
1205
|
does not erase a successful landing or release. The CLI prints both and exits unsuccessfully
|
|
1188
1206
|
when ticket synchronization needs attention. Watch emits `ticket.applied`, `ticket.failed`
|
|
@@ -1598,20 +1616,21 @@ resolves once the fleet job settled. The draft stays until the fleet delivered i
|
|
|
1598
1616
|
answer arrives within 120 seconds, the modal says the outcome is unknown, so the transcript is
|
|
1599
1617
|
checked before sending again.
|
|
1600
1618
|
|
|
1601
|
-
A report that is a Codex thread the fleet does not run (a referenced thread) opens
|
|
1602
|
-
|
|
1603
|
-
|
|
1604
|
-
|
|
1605
|
-
|
|
1606
|
-
|
|
1607
|
-
|
|
1608
|
-
|
|
1609
|
-
|
|
1610
|
-
|
|
1611
|
-
|
|
1612
|
-
session the fleet does not run opens read-only, without
|
|
1613
|
-
Claude Code session only by resuming it in a process of its
|
|
1614
|
-
that runs it, so the modal says to adopt the session with a
|
|
1619
|
+
A report that is a Codex thread the fleet does not run (a referenced thread) opens wherever the
|
|
1620
|
+
thread works, inside a project's folder or outside every project: the controller reads it through
|
|
1621
|
+
the host's shared Codex server that owns it, as the fleet reaches its own threads
|
|
1622
|
+
(`controller.directreport.read`). Its steer box sends the owner's message as an agent message,
|
|
1623
|
+
headed `[Agent message via AGL from "Owner" — the owner, in the AGL Driver view; not from the
|
|
1624
|
+
user]`: steered into the running turn or else the next one, through that same server, so AGL never
|
|
1625
|
+
becomes a second writer. A turn another Codex client runs stays that client's; the message steers
|
|
1626
|
+
it only with the turn the modal last read (`expectedTurnId`), is refused once another turn runs,
|
|
1627
|
+
and is not sent once that turn has ended. The usual agent message limits apply: 16 KiB of text and
|
|
1628
|
+
the per-task rate. The report is the owner's and reached outside every project, so no project's
|
|
1629
|
+
**Agent messages** switch applies to it. While a turn runs the modal reads again every 3
|
|
1630
|
+
seconds. A report that is a Claude Code session the fleet does not run opens read-only, without
|
|
1631
|
+
transcript or steer box: AGL reaches a Claude Code session only by resuming it in a process of its
|
|
1632
|
+
own, a second writer beside the one that runs it, so the modal says to adopt the session with a
|
|
1633
|
+
relaunch once it has settled.
|
|
1615
1634
|
Leaving the driver closes the modal.
|
|
1616
1635
|
|
|
1617
1636
|
A fleet worker opened from the session list shows the same transcript in the main area; its
|
|
@@ -1628,7 +1647,7 @@ no AGL client sends it since the Driver view lists direct reports: MCP `fleet_wo
|
|
|
1628
1647
|
`agl fleet worker list` list workers through `agl.mcp.fleet.worker.list`, which aglapi excludes.
|
|
1629
1648
|
|
|
1630
1649
|
Direct reports are sessions that report to the owner directly, each with its own ticket the
|
|
1631
|
-
owner steers it through.
|
|
1650
|
+
owner steers it through. Seven protected requests manage them, and the driver has the same
|
|
1632
1651
|
operations as tools (see below):
|
|
1633
1652
|
|
|
1634
1653
|
- `controller.directreport.appoint` names a fleet worker that is bound to a native session and a
|
|
@@ -1641,7 +1660,21 @@ operations as tools (see below):
|
|
|
1641
1660
|
and `cwd` say otherwise, and the report is that worker's. A session still running outside the
|
|
1642
1661
|
fleet is refused, never stopped; its owner stops it first. If the report cannot be recorded
|
|
1643
1662
|
after the relaunch, the error names the worker to appoint. A session a fleet worker is bound to
|
|
1644
|
-
is appointed instead.
|
|
1663
|
+
is appointed instead. A Claude Code session that an AGL project conversation records is refused:
|
|
1664
|
+
it stays that project's, and a relaunch would give the conversation a second writer.
|
|
1665
|
+
`appoint` and `adopt` take `reportsTo: { kind: 'driver' }`, the only superior so far: every
|
|
1666
|
+
report reports to the host's driver.
|
|
1667
|
+
- `controller.directreport.preflight { session, profile?, cwd? }` says, for a session the
|
|
1668
|
+
session feed lists (`session` as `controller.nativesession.read` names it), how it would become
|
|
1669
|
+
a report and what refuses that now, writing nothing. `path` is `appoint` for a session a fleet
|
|
1670
|
+
worker of the owner is bound to (with its `workerName`), `reference` for a Codex thread and
|
|
1671
|
+
`relaunch` for a Claude Code session, with `profiles`, the Claude profiles whose Claude Code home
|
|
1672
|
+
holds it, the chosen `profile` (the first by default) and `cwd` (the session's own by default).
|
|
1673
|
+
`blockers` lists each refusal with a code and the message the owner sees: `notListed`,
|
|
1674
|
+
`alreadyReport`, `workerNoTicket`, `projectConversation`, `directoryMissing`, `noProfile`,
|
|
1675
|
+
`profileHome`, and the relaunch's own checks, run as the relaunch runs them (`invalidId`,
|
|
1676
|
+
`unsupported`, `notInInventory`, `running` with its `pid`, `working`, `noAgentId`,
|
|
1677
|
+
`noTranscript`). `reportsTo` lists whom the report can report to. An adopt checks again.
|
|
1645
1678
|
- `controller.directreport.list` returns the active reports (`retired: true` adds the retired
|
|
1646
1679
|
ones). Each comes with a status derived on the read and its open ticket questions: those its
|
|
1647
1680
|
session asked and those on tickets of its `projects` (by default the project of its
|
|
@@ -1649,9 +1682,9 @@ operations as tools (see below):
|
|
|
1649
1682
|
- `controller.directreport.retire` retires one and leaves its session as it is.
|
|
1650
1683
|
- `controller.directreport.read { name, limit? }` returns an active report's newest `limit`
|
|
1651
1684
|
bundles (1-200, default 50): a fleet worker's transcript as `controller.fleet.worker.read`
|
|
1652
|
-
reads it (`kind: 'fleet-worker'`), or a Codex thread's
|
|
1653
|
-
(`kind: 'session'`, with `
|
|
1654
|
-
audited as `session.read`.
|
|
1685
|
+
reads it (`kind: 'fleet-worker'`), or a Codex thread's, read through the shared Codex server
|
|
1686
|
+
outside every project (`kind: 'session'`, with `sessionId`, the thread's `cwd`, `earlier` and
|
|
1687
|
+
the running `turnId`), audited as `session.read`.
|
|
1655
1688
|
- `controller.directreport.message { name, text, expectedTurnId? }` steers an active report the
|
|
1656
1689
|
fleet runs with the owner's own message through its `driverTicketKey` and returns the settled
|
|
1657
1690
|
job, or sends a Codex thread the owner's agent message and returns its `delivery` and
|
|
@@ -1660,6 +1693,18 @@ operations as tools (see below):
|
|
|
1660
1693
|
|
|
1661
1694
|
Each write that lands pushes `directreports.changed`.
|
|
1662
1695
|
|
|
1696
|
+
In the workspace, **Make direct report…** opens a dialog for these requests from three places: a
|
|
1697
|
+
native session's row menu in the sidebar, the toolbar of a native session's own view, and the
|
|
1698
|
+
Driver view's toolbar, which offers every native session the session list shows that is no active
|
|
1699
|
+
report yet, newest first. The dialog asks `controller.directreport.preflight` when it opens and
|
|
1700
|
+
every 3 seconds while it stays open, shows the way the session takes and every refusal by its
|
|
1701
|
+
message, and submits only once nothing refuses. The owner names the report (a name made from the
|
|
1702
|
+
session's by default) and, unless a fleet worker's session is appointed, picks its driver ticket
|
|
1703
|
+
from the open tickets, the session's own first; a relaunch also takes the Claude profile, the
|
|
1704
|
+
directory, a worker name and the prompt it resumes with. **Reports to** offers only the driver so
|
|
1705
|
+
far. **Make direct report** appoints or adopts, which checks everything again; a refusal is shown
|
|
1706
|
+
in the dialog, and a report made closes it and joins the Driver view's list.
|
|
1707
|
+
|
|
1663
1708
|
A report's name stays taken after it is retired, and one native session is held by one active
|
|
1664
1709
|
report at a time. A fleet worker's report follows its lane: a refresh or move points the report
|
|
1665
1710
|
at the successor and its native session before the predecessor is stopped and archived. If that
|
|
@@ -1811,9 +1856,28 @@ stalled, so an answered question or an orphaned lane does not wait for someone t
|
|
|
1811
1856
|
ticket board, not from the user]`. Without a live worker, or when the steer is refused, the
|
|
1812
1857
|
driver is told instead, with the answers.
|
|
1813
1858
|
- **ready** and not picked up: the driver is told.
|
|
1814
|
-
- **landed** for longer than `landedAfterHours`:
|
|
1815
|
-
`fleet_release`
|
|
1816
|
-
|
|
1859
|
+
- **landed** for longer than `landedAfterHours`: told once per repository, on the ticket that
|
|
1860
|
+
landed first, listing every such ticket and proposing one `fleet_release` for the repository
|
|
1861
|
+
(the release reconciler links and releases every landed ticket a release tag holds). Another ticket landing in the
|
|
1862
|
+
group names the repository again; a ticket without a code link keeps a notice of its own.
|
|
1863
|
+
- **a deploy that waits**: a [deploy target](#deployments) runs a version older than its
|
|
1864
|
+
repository's newest release, which was tagged more than 24 hours ago, and no open deploy plan
|
|
1865
|
+
covers that release: the owner's answer covers its plan's version only, and while a plan waits
|
|
1866
|
+
for the answer no other is asked. The pump creates one: a ticket in `ready` with a deploy plan for that
|
|
1867
|
+
release, whose question asks the owner to deploy it now, in the next maintenance window (the
|
|
1868
|
+
AGL controller: when no session is busy) or to hold. The ticket is assigned to the active
|
|
1869
|
+
direct report whose projects include the target's project, else to nobody, and the driver
|
|
1870
|
+
deploys it. A version the target was rolled back from is not proposed again, nor a target and
|
|
1871
|
+
version a ticket planned already, done ones included: a plan closed before it was fulfilled counts as a hold, whoever closed it.
|
|
1872
|
+
- **a deploy plan that is due**: the owner said to deploy now and the target still does not run
|
|
1873
|
+
the release a day later; the window the deploy was queued into is open; it was queued and no
|
|
1874
|
+
window the owner gave is planned for the target; or, for the AGL controller, no session is busy. Nothing is
|
|
1875
|
+
told while the plan waits for the owner or is held.
|
|
1876
|
+
- **a hotfix proposal**: an urgent bug found in the version a target runs (an `affects` link),
|
|
1877
|
+
whose fix landed but does not run there, and that no release plan covers yet. The notice says
|
|
1878
|
+
how to plan it: a release plan without a version, since gitzone picks the next one from what
|
|
1879
|
+
landed.
|
|
1880
|
+
- **a comment nobody hears**, in every column but `released` and `closed`: the ticket's newest discussion entry
|
|
1817
1881
|
(comments and questions, the pump's own left out) is a comment by someone not in the driver role,
|
|
1818
1882
|
nothing by the driver role or the assignee followed it, and no live fleet worker holds the
|
|
1819
1883
|
ticket, so no session was told. The notice quotes the comment and lists the Claude Code
|
|
@@ -1854,7 +1918,8 @@ above 0 and up to 720 (default 24). A saved master takes effect at once.
|
|
|
1854
1918
|
### Shared project tickets
|
|
1855
1919
|
|
|
1856
1920
|
One board spans every project. Tickets have global `AGL-<n>` keys and these fixed columns:
|
|
1857
|
-
`backlog`, `ready`, `in_progress`, `needs_input`, `review`, `landed`, `released` (done)
|
|
1921
|
+
`backlog`, `ready`, `in_progress`, `needs_input`, `review`, `landed`, `released` (done) and
|
|
1922
|
+
`closed` (done: finished work that ships no code, such as an owner decision or a survey).
|
|
1858
1923
|
Use a project filter rather than creating separate boards. Each ticket is an epic, task or
|
|
1859
1924
|
subtask, with title, markdown description, priority, labels, assignee, original source words
|
|
1860
1925
|
and attachments, branch/commit/release links, actor attribution and timestamps. Tasks can
|
|
@@ -1865,7 +1930,87 @@ a request. They can read everything, create unassigned backlog tickets and comme
|
|
|
1865
1930
|
ticket. They can update/link/move only tickets assigned to their verified session, and
|
|
1866
1931
|
only within `ready`, `in_progress`, `needs_input`, `review`. Review requires a branch link
|
|
1867
1932
|
with its full 40- or 64-character hexadecimal sha; a commit link alone does not qualify.
|
|
1868
|
-
|
|
1933
|
+
Landed requires a branch or commit link and released a release link, for every actor and also
|
|
1934
|
+
when a ticket is created in the column (`ticket_landed_evidence_required`,
|
|
1935
|
+
`ticket_released_evidence_required`); fleet land and release link their evidence first. A
|
|
1936
|
+
ticket already in a column is reordered there as it is. Only the driver or owner assigns,
|
|
1937
|
+
lands, releases or closes tickets, and a landed ticket is never closed (`ticket_closed_landed`):
|
|
1938
|
+
its code ships with the tag that holds it, so it is released, or moved back first when the code is
|
|
1939
|
+
not to ship. At its first start after AGL-916 the controller moves every
|
|
1940
|
+
ticket released by hand without a release link or any code link to `closed`, with a comment
|
|
1941
|
+
saying why; one that links code keeps its column, and the release reconciler links it from the
|
|
1942
|
+
remote tag that holds its landing (see [Deployments](#deployments)).
|
|
1943
|
+
|
|
1944
|
+
A ticket may carry a **release plan**, `releasePlan { repo, version? }`: the repository as
|
|
1945
|
+
`org/name` (`modelprofile.com/agl`; its fleet id or checkout path is accepted and stored as
|
|
1946
|
+
`org/name`), which must name one repository fleet discovery knows, and optionally the version
|
|
1947
|
+
it should reach; without a version the plan means the next release. A hotfix is a release
|
|
1948
|
+
plan on an urgent ticket, released off main. Only the driver or owner plans
|
|
1949
|
+
(`ticket_release_plan_forbidden` for a worker):
|
|
1950
|
+
|
|
1951
|
+
```sh
|
|
1952
|
+
agl ticket update AGL-931 --expected-revision 3 --release-plan bellini.io/app@0.5.1 --priority urgent
|
|
1953
|
+
agl ticket create --project agl --title "Release 41.0.0" --release-plan modelprofile.com/agl@41.0.0
|
|
1954
|
+
agl ticket update AGL-931 --expected-revision 4 --clear-release-plan
|
|
1955
|
+
```
|
|
1956
|
+
|
|
1957
|
+
A ticket may carry a **maintenance window**, `maintenanceWindow { from, to, targets }`: two
|
|
1958
|
+
ISO 8601 instants (an offset is accepted; AGL stores UTC), at most 7 days apart and with `to`
|
|
1959
|
+
not passed yet, for deploy targets the Configuration master names. The AGL controller takes no
|
|
1960
|
+
window (`ticket_window_invalid`): it is upgraded when no session is busy. A window is
|
|
1961
|
+
*scheduled* before `from`, *active* until `to` and *done* after; moving it is an update, and
|
|
1962
|
+
closing its ticket cancels it. The owner's own window counts at once. One the driver plans or
|
|
1963
|
+
moves asks the owner, in the same change, "Hold a maintenance window <time> UTC for <targets>?"
|
|
1964
|
+
with two options, `1` approve and `2` decline, and keeps its question (`questionId`); it counts
|
|
1965
|
+
once the owner approves it, and neither changes nor clears while the question is open
|
|
1966
|
+
(`ticket_window_waiting`). A **deploy plan**, `deployPlan { target, version }`, says a
|
|
1967
|
+
target should run that release or a newer one. Setting it asks the owner, in the same change, a
|
|
1968
|
+
question with three options, by id: `1` deploy now, `2` in the next window (for the AGL
|
|
1969
|
+
controller: when no session is busy), `3` hold. The plan keeps its question (`questionId`), and
|
|
1970
|
+
once asked it keeps its target and version for everyone (`ticket_deploy_plan_fixed`): it holds the
|
|
1971
|
+
owner's decision on that release. Setting the same plan again is no change while the question is
|
|
1972
|
+
open and asks anew once the owner answered; closing the ticket drops the plan, and another target
|
|
1973
|
+
or version is a ticket of its own. A plan's ticket is a *deploy ticket*, which holds no code or
|
|
1974
|
+
release, both ways: a ticket that holds code or a release (a branch, commit or release link, or a
|
|
1975
|
+
place in Review, Landed or Released), or that is closed, plans no deploy
|
|
1976
|
+
(`ticket_deploy_plan_invalid`), and a deploy ticket takes no branch, commit or release link from
|
|
1977
|
+
anyone (`ticket_deploy_plan_link_forbidden`), so `fleet land` and `fleet release` refuse it before
|
|
1978
|
+
they push or publish. A release would make the ticket done, and a done ticket's plan reaches
|
|
1979
|
+
nobody. The answer is the owner's go, and only the owner answers the question of a deploy plan or
|
|
1980
|
+
a window (`ticket_go_owner_only`). The deploy monitor closes the ticket with a comment once the
|
|
1981
|
+
target runs the version. Only the driver or owner plans either
|
|
1982
|
+
(`ticket_window_forbidden`, `ticket_deploy_plan_forbidden`), and AGL itself deploys nothing:
|
|
1983
|
+
the driver, or the direct report the plan is assigned to, deploys when the go and the target's
|
|
1984
|
+
condition allow it. A done ticket asks nobody: a question left open on a released or closed
|
|
1985
|
+
ticket shows no `openQuestion` and reaches no one's batch of open questions.
|
|
1986
|
+
|
|
1987
|
+
```sh
|
|
1988
|
+
agl ticket create --project publicdata --title "Maintenance window" --column ready \
|
|
1989
|
+
--window 2026-10-28T02:00+01:00/2026-10-28T03:00+01:00 --window-targets publicdata,shop
|
|
1990
|
+
agl ticket update AGL-940 --expected-revision 2 --window 2026-10-28T02:00Z/2026-10-28T04:00Z --window-targets publicdata
|
|
1991
|
+
agl ticket move AGL-940 --column closed # cancels the window
|
|
1992
|
+
agl ticket create --project publicdata --title "Deploy publicdata 3.1.0" --column ready --deploy-plan publicdata@3.1.0
|
|
1993
|
+
agl ticket update AGL-941 --expected-revision 5 --deploy-plan publicdata@3.1.0 # once answered: asks the owner anew
|
|
1994
|
+
agl ticket move AGL-941 --column closed # drops the plan
|
|
1995
|
+
```
|
|
1996
|
+
|
|
1997
|
+
`agl ticket` acts as the driver, so the windows it plans ask the owner and it cannot answer a
|
|
1998
|
+
go; the owner answers in the browser, in the Deployments view's go dialog or on the ticket.
|
|
1999
|
+
|
|
2000
|
+
A bug records the version it was found in with an `affects` link, keyed on the repository
|
|
2001
|
+
because app repositories often publish no package; "fixed in" is never stored but computed as
|
|
2002
|
+
the first release tag holding the commit the fix landed as:
|
|
2003
|
+
|
|
2004
|
+
```sh
|
|
2005
|
+
agl ticket link AGL-930 --affects bellini.io/app@0.5.0
|
|
2006
|
+
agl ticket unlink AGL-930 --affects bellini.io/app@0.5.0
|
|
2007
|
+
```
|
|
2008
|
+
|
|
2009
|
+
A release link comes from the remote's tag, which fleet links; only the owner links a release
|
|
2010
|
+
by hand (`agl ticket link --package --version`; `ticket_release_link_forbidden` for the driver and
|
|
2011
|
+
workers). `agl ticket unlink` (`ticket_unlink`, `controller.ticket.unlink`) removes one link exactly as
|
|
2012
|
+
the ticket holds it (a fleet release link also names `--repo` and `--sha`); only the driver or
|
|
2013
|
+
owner unlinks, and never the evidence the ticket's column requires. The authenticated web owner
|
|
1869
2014
|
has full access; the CLI reuses `agl config`'s short-lived local-owner capability. There
|
|
1870
2015
|
is no automatic dispatch. Attachment URLs must use HTTP or HTTPS; AGL stores the
|
|
1871
2016
|
reference and does not fetch its payload.
|
|
@@ -1883,7 +2028,11 @@ Trusted fleet supervision calls `OpenCodeController.applyFleetEvent(event, signa
|
|
|
1883
2028
|
actor derived from verified controller authority, never an untrusted public identity claim:
|
|
1884
2029
|
|
|
1885
2030
|
- `kind: 'landed'` requires `repo`, `branch` and a full `sha`.
|
|
1886
|
-
- `kind: 'released'` requires `
|
|
2031
|
+
- `kind: 'released'` requires `version` and `package` or `repo`; fleet names the repository and
|
|
2032
|
+
the tag's commit (`repo`, `sha`), which the release link then carries. Every `released` event
|
|
2033
|
+
AGL writes is the release reconciler's. A ticket already in Released gets the link where it
|
|
2034
|
+
stands, so a ticket whose code landed in several repositories is released on its first tag and
|
|
2035
|
+
links each repository's release as its tag appears.
|
|
1887
2036
|
- `kind: 'comment'` requires `body` (markdown or ticket reference content).
|
|
1888
2037
|
- Landing/release may also supply `body`; its comment commits with the evidence and move.
|
|
1889
2038
|
|
|
@@ -2075,14 +2224,20 @@ question to the card and the card's response to an answer.
|
|
|
2075
2224
|
An assigned worker asks on its own tickets through `ticket_question_ask`; the owner and the
|
|
2076
2225
|
driver (`agl ticket ask`) may ask on any ticket. Only the owner (`controller.ticket.answer`)
|
|
2077
2226
|
and the driver (`agl ticket answer`) answer; a worker's answer is refused with
|
|
2078
|
-
`ticket_answer_forbidden
|
|
2227
|
+
`ticket_answer_forbidden`, and the question of a deploy plan or a maintenance window only the
|
|
2228
|
+
owner answers (`ticket_go_owner_only`): that answer is the owner's go. A question takes one answer: repeating the same answer returns the
|
|
2079
2229
|
answered question unchanged, and a different one is refused with `ticket_question_answered`.
|
|
2080
2230
|
A choice must name an option, multiple choices need `multiSelect`, and text needs
|
|
2081
2231
|
`allowCustom`. Asking and answering each advance the ticket's revision and add an `asked` or
|
|
2082
2232
|
`answered` activity entry; neither takes an expected revision.
|
|
2083
2233
|
|
|
2084
2234
|
Every ticket carries `autoLabels`, computed on read and never stored. `openQuestion` is
|
|
2085
|
-
present while the ticket has an unanswered question
|
|
2235
|
+
present while the ticket has an unanswered question and is neither released nor closed, `planned`
|
|
2236
|
+
while it has a release plan, a deploy plan or a maintenance window and is neither released nor
|
|
2237
|
+
closed, and `undeployed` while it was released in a version that some deploy target of one of its
|
|
2238
|
+
repositories does not run yet, a target that never answered its probe included: it holds until
|
|
2239
|
+
every target is seen running the release (read from a set the deploy monitor keeps,
|
|
2240
|
+
never from git inside the ticket transaction). Label filters (`--label`, `label` in
|
|
2086
2241
|
list, board and search, through the web, CLI and MCP) match hand labels and AutoLabels alike.
|
|
2087
2242
|
A hand label may not use an AutoLabel's name (`ticket_label_reserved`), and AutoLabels cannot
|
|
2088
2243
|
be set or removed.
|
|
@@ -2186,8 +2341,18 @@ other-person assignments and historical authors/activity stay unchanged. **New t
|
|
|
2186
2341
|
**New epic** ask for the new ticket's project, starting at the one chosen in the filters, else
|
|
2187
2342
|
its epic's. Every ticket belongs to one, so the dialog offers no "No project", says so below the
|
|
2188
2343
|
field and, confirmed without a project, opens the projects instead of creating; the controller
|
|
2189
|
-
refuses a ticket without one as well. **Released**
|
|
2190
|
-
three cards
|
|
2344
|
+
refuses a ticket without one as well. **Released** and **Closed** start folded to their count
|
|
2345
|
+
and their newest three cards, Closed with a grey ring apart from Released; the button in a header
|
|
2346
|
+
opens the column. The AutoLabels have
|
|
2347
|
+
filter chips with counts above the columns, `undeployed` in amber and `planned` in blue; a
|
|
2348
|
+
card shows a ticket's release plan as a "plan:" chip and its `affects` links as "found in".
|
|
2349
|
+
The ticket's detail has a **Where it runs** section (`controller.deploy.ticket`): where the
|
|
2350
|
+
work landed, the first release that holds it, and whether each deploy target of the repository
|
|
2351
|
+
runs it, with **Open in Deployments** (a link, `#deployments`, which the app routes itself; a new
|
|
2352
|
+
tab opened on it shows the view), reloaded as `deployments.changed` arrives. A ticket with a maintenance window or a deploy plan has a
|
|
2353
|
+
**Planned** section with the window and where it stands, or the deploy and the owner's go; a
|
|
2354
|
+
ticket that plans and ships no code shows that section alone. The history says a change of
|
|
2355
|
+
plans in words ("planned the maintenance window to Tue Oct 27, 02:00–03:00 for shop"). Assignees offered are the viewer and AGL's
|
|
2191
2356
|
tracked conversations that are not archived; a ticket's existing assignee is kept exactly as the
|
|
2192
2357
|
controller holds it.
|
|
2193
2358
|
|
|
@@ -2200,6 +2365,109 @@ it, and an open editor keeps its draft. The board reads itself again on every
|
|
|
2200
2365
|
opens its ticket: description, links (repository, branch, short sha), the
|
|
2201
2366
|
source words, the discussion with its composer, and the ticket's history.
|
|
2202
2367
|
|
|
2368
|
+
### Deployments
|
|
2369
|
+
|
|
2370
|
+
What runs where is observed, never claimed. A release is the tag `v<version>` on the
|
|
2371
|
+
repository's remote; what a deploy target runs is what its probe answers. The AGL controller is
|
|
2372
|
+
the built-in target `agl-controller` (its package version, its start time, the commit it runs in
|
|
2373
|
+
a development checkout, its HEAD, and the digest of the dependency tree it installed; an
|
|
2374
|
+
installed package names no commit, and its digest tells a reinstall apart); other targets are configured in the Configuration
|
|
2375
|
+
master and answer a JSON version document:
|
|
2376
|
+
|
|
2377
|
+
```json
|
|
2378
|
+
{
|
|
2379
|
+
"fleet": {
|
|
2380
|
+
"deployTargets": [
|
|
2381
|
+
{ "id": "publicdata", "name": "publicdata", "environment": "production", "repo": "coffee.link/publicdata",
|
|
2382
|
+
"project": "publicdata", "deployWhen": "window",
|
|
2383
|
+
"probe": { "kind": "http", "url": "https://publicdata.example/version", "versionPointer": "/version", "shaPointer": "/sha" },
|
|
2384
|
+
"deploys": "tsdeploy deploy", "downtime": "none" }
|
|
2385
|
+
]
|
|
2386
|
+
}
|
|
2387
|
+
}
|
|
2388
|
+
```
|
|
2389
|
+
|
|
2390
|
+
A target's id is lowercase letters, digits, `.`, `_` and `-`; `repo` is `org/name`; `project`
|
|
2391
|
+
is the AGL project its deploy plans go to; the URL is http(s) without credentials, and a
|
|
2392
|
+
redirect is a failed probe; the pointers are JSON pointers (`versionPointer` defaults to
|
|
2393
|
+
`/version`). `deployWhen` is `anytime` (the default) or `window`: such a target is deployed
|
|
2394
|
+
only inside a maintenance window. A target with `probe: { "kind": "controller" }` replaces the
|
|
2395
|
+
built-in one and takes no `deployWhen`: the controller is upgraded when no session is busy.
|
|
2396
|
+
|
|
2397
|
+
The controller fetches the remotes its targets, release plans, `affects` links and landed
|
|
2398
|
+
tickets name, and probes every target, every five minutes. It mirrors each remote's main into
|
|
2399
|
+
`refs/agl/remote-main` and its `v*` tags into `refs/agl/remote-tags` of the checkout (a failed
|
|
2400
|
+
fetch keeps the last mirror), never the remote-tracking branch a fleet land or release pushes and
|
|
2401
|
+
checks, and every read takes releases from there. When a target answers another version,
|
|
2402
|
+
commit or set of artifacts than it ran, it records an observation
|
|
2403
|
+
(`agl_fleet_deploy_observations`: the target and a sequence number, the repository, version,
|
|
2404
|
+
commit, when, the version before, and the artifacts: the controller's installed dependency
|
|
2405
|
+
tree, none for an HTTP target) and publishes the fleet event `deploy.observed`. A target is
|
|
2406
|
+
down after two failed probes in a row: `deploy.probe.failed` is published once, and
|
|
2407
|
+
`deploy.probe.recovered` when it answers again. All three reach the driver. A target that names
|
|
2408
|
+
a commit other than the one its version's tag names is shown **untagged**; a short commit
|
|
2409
|
+
(7 to 64 hex digits) is the tag's when the tag's commit starts with it.
|
|
2410
|
+
|
|
2411
|
+
A ticket in Landed or Released, for each repository its code landed in (its newest branch or
|
|
2412
|
+
commit link there that remote main holds) whose release it does not link yet, is linked to the
|
|
2413
|
+
first release tag holding that commit by the deploy monitor's release reconciler (actor
|
|
2414
|
+
`agl:release-reconciler`), once per ticket, release and package. The link names the packages that
|
|
2415
|
+
release is known to have published, those a fleet release published and saw at every registry;
|
|
2416
|
+
for a tag cut elsewhere it names the repository and version alone. The first such tag moves the
|
|
2417
|
+
ticket to Released; the release of each other repository is linked as its tag appears, where the
|
|
2418
|
+
ticket stands. A fleet release asks for a pass when it is done. Everything else is computed when
|
|
2419
|
+
it is read:
|
|
2420
|
+
|
|
2421
|
+
```sh
|
|
2422
|
+
agl deploy status [TARGET] [--json] # running version and commit, since when, probe, newest tag, what does not run yet, open bugs, deploys, plans, windows
|
|
2423
|
+
agl deploy history TARGET [--json] # every version observed, newest first; a newer one before an older one is a rollback
|
|
2424
|
+
agl deploy probe TARGET [--json] # ask a target now; deploy scripts call it after a deploy, it claims nothing
|
|
2425
|
+
agl release status [REPO] [--json] # newest tag, release plans, and the landed tickets the next release would ship
|
|
2426
|
+
```
|
|
2427
|
+
|
|
2428
|
+
The MCP and driver tools are `deploy_status`, `deploy_history`, `deploy_probe` and
|
|
2429
|
+
`release_status`. "Open bugs on the running version" are tickets not closed that were found in
|
|
2430
|
+
the version a target runs or an earlier one (an `affects` link whose tag the running tag holds;
|
|
2431
|
+
by version order where either has no tag on the remote), and whose fix does not run there: no
|
|
2432
|
+
fix landed, or the running tag does not hold the commit it landed as. A released ticket is not running yet while
|
|
2433
|
+
some target of one of its repositories runs a version whose tag does not hold its release there, or
|
|
2434
|
+
has never answered its probe.
|
|
2435
|
+
|
|
2436
|
+
A target deploys when its condition and the owner's go allow it. `deploy status` shows each
|
|
2437
|
+
target's condition: any time; in a window, open while a [maintenance
|
|
2438
|
+
window](#shared-project-tickets) for it is active; for the AGL controller, when no session is
|
|
2439
|
+
busy (it counts the busy ones). Only a window the owner gave counts: the owner's own, or one
|
|
2440
|
+
the driver proposed and the owner approved; one that waits for the owner's go or that the owner
|
|
2441
|
+
declined opens nothing. It also shows the windows planned for it, each with the owner's go, and
|
|
2442
|
+
its deploy plans, each with the owner's go: waiting for the answer, now, in the next window (the
|
|
2443
|
+
window the deploy is queued into, the first one the owner gave for the target), when idle, or
|
|
2444
|
+
held. Only the owner's answer is a go. When a target runs the planned version or a newer one,
|
|
2445
|
+
the deploy monitor comments on the plan's ticket once and closes it (actor
|
|
2446
|
+
`agl:deploy-monitor`). AGL deploys nothing itself except `agl upgrade`, which keeps its
|
|
2447
|
+
own owner gate: the driver, or the direct report a plan is assigned to, deploys, and the board
|
|
2448
|
+
pump tells them when a plan is due.
|
|
2449
|
+
|
|
2450
|
+
The web app's header has a **Deployments** entry beside Board, with a badge counting the
|
|
2451
|
+
targets behind their newest release, rolled back, not answering or with a deploy plan that
|
|
2452
|
+
waits for the owner's go, and the maintenance windows that wait for it. The view shows four tiles (behind, released but not running, open
|
|
2453
|
+
bugs on running versions, probes), the targets table (running version and commit, since when,
|
|
2454
|
+
newest release, what does not run yet, open bugs, the next step: a proposed hotfix, a deploy
|
|
2455
|
+
plan and its go, a release plan or a deploy), the plans and what changed. The plans list has
|
|
2456
|
+
the deploy plans, which open the go dialog while they wait (the plan's question with its three
|
|
2457
|
+
answers as buttons, what the target runs, when it deploys and who deploys it), the maintenance
|
|
2458
|
+
windows, which open the window dialog, or the go dialog (approve or decline) while one the driver
|
|
2459
|
+
proposed waits for the owner's go, and the release plans. A row of the targets table opens
|
|
2460
|
+
the target's sheet: what it runs, when it deploys with its windows and deploy plans, the tickets
|
|
2461
|
+
not running there yet, its open bugs, its history and how it deploys, with **Probe now**,
|
|
2462
|
+
**Plan window** and **Plan release**. **Plan window** asks for the targets (the AGL controller
|
|
2463
|
+
is not offered), the start and end in the reader's time zone, says what happens, and creates a
|
|
2464
|
+
ticket with the window in `ready` in the first target's project; a planned window is moved
|
|
2465
|
+
with **Save window** and cancelled with **Cancel window**, which closes its ticket. **Plan
|
|
2466
|
+
release** puts a release plan on a chosen ticket or a new one, showing what the release would
|
|
2467
|
+
ship from git; **Plan hotfix** turns an urgent bug found in a running version into an urgent
|
|
2468
|
+
release plan, for the next version unless one is named. The view follows
|
|
2469
|
+
`deployments.changed`.
|
|
2470
|
+
|
|
2203
2471
|
### Configuration: one master for every harness
|
|
2204
2472
|
|
|
2205
2473
|
AGL keeps one **master configuration** and projects it onto Claude Code, Codex, OpenCode and Flex. The master is harness-agnostic and versioned in AGL's database; you never edit a harness's native files by hand again.
|
|
@@ -2402,7 +2670,7 @@ A removal that fails is resumed with backoff, and it resumes across restarts and
|
|
|
2402
2670
|
|
|
2403
2671
|
### Conversations
|
|
2404
2672
|
|
|
2405
|
-
The sidebar is the session list (`controller.sessionfeed.list`, then `sessionfeed` deltas). It holds the sessions of every harness across every registered project: the conversations AGL tracks, the Flex and OpenCode sessions of a project folder that AGL does not track yet, the threads on the shared Codex app-server, Claude terminals, and the Claude Code sessions of the host's home and of the fleet profiles' own homes. A conversation that is tracked, run by a fleet worker and present on the Codex server is one row. Each row shows its harness, its state (working, needing input, completed or failed), its name, the last reply's opening for tracked conversations and workers, the tickets it is linked to, and when it last changed; a newly created session joins at the feed's next pass. Selecting a row opens it: a tracked conversation opens, an untracked one is tracked first, a Claude terminal opens in the Terminals view, a session a fleet worker runs opens that worker, and any other Claude Code session or Codex thread opens where it runs, whatever its directory (see [Sessions outside every project](#sessions-outside-every-project)). Opening a session never registers a project: the project matters only when a new session is started. A row AGL cannot open says why in the sidebar, for example that its project is no longer registered. A ticket chip opens that ticket on the board. Right-click, the ContextMenu key or Shift+F10 opens the row's menu: a conversation's own menu, **Rename** and **Terminate** for a terminal, or **Copy session id
|
|
2673
|
+
The sidebar is the session list (`controller.sessionfeed.list`, then `sessionfeed` deltas). It holds the sessions of every harness across every registered project: the conversations AGL tracks, the Flex and OpenCode sessions of a project folder that AGL does not track yet, the threads on the shared Codex app-server, Claude terminals, and the Claude Code sessions of the host's home and of the fleet profiles' own homes. A conversation that is tracked, run by a fleet worker and present on the Codex server is one row. Each row shows its harness, its state (working, needing input, completed or failed), its name, the last reply's opening for tracked conversations and workers, the tickets it is linked to, and when it last changed; a newly created session joins at the feed's next pass. Selecting a row opens it: a tracked conversation opens, an untracked one is tracked first, a Claude terminal opens in the Terminals view, a session a fleet worker runs opens that worker, and any other Claude Code session or Codex thread opens where it runs, whatever its directory (see [Sessions outside every project](#sessions-outside-every-project)). Opening a session never registers a project: the project matters only when a new session is started. A row AGL cannot open says why in the sidebar, for example that its project is no longer registered. A ticket chip opens that ticket on the board. Right-click, the ContextMenu key or Shift+F10 opens the row's menu: a conversation's own menu, **Rename** and **Terminate** for a terminal, or **Copy session id**, **Copy directory** and **Make direct report…** (see [Driver session](#driver-session)) for a native session. Conversations archived in AGL leave the list.
|
|
2406
2674
|
|
|
2407
2675
|
A failed row of any kind leads its menu with **Acknowledge and remove** (`controller.sessionfeed.acknowledge`). The controller records, for the owner, that row's failure as of the time the row shows, and the row leaves the Failed group until the session moves again: new activity or a new failure brings it back. Nothing else changes: the session and its transcript, a fleet worker's dispatch fence and error, its tickets and the unknown-dispatch record stay as they are, and nothing is sent, resumed or stopped. The acknowledgements are kept in the controller's database and survive a restart; a row that changed since it was listed, is no longer failed or is gone is refused. From the command line the owner does the same with `agl feed` (see [CLI](#cli)); no agent, worker or MCP tool can acknowledge, so a worker never hides its own failure. The composer's open-sessions action shows the sidebar and moves focus into the list. The list header offers three actions.
|
|
2408
2676
|
|
|
@@ -2718,6 +2986,8 @@ Every signaling pair is bound to the exact peer, credential, resource authority,
|
|
|
2718
2986
|
|
|
2719
2987
|
Chrome captures the active tab directly and uses native video encoding, decoding, congestion control, and pacing. GPU compositing and encoding are requested automatically where supported; the actual capabilities and encoder are reported rather than assumed. The detail quality policy preserves text resolution and lets Chromium adapt frame rate under pressure. Capture is capped at 2560 by 1600 pixels, 60 frames per second, and 16 Mbps; a second application downscaling loop is no longer used. The higher frame cadence reduces the wait between input and its visible result; congestion control and CPU adaptation still apply. The receiver requests a minimal jitter buffer where supported, and the browser applies its own minimum. Hidden viewers close their media peer and reconnect when visible; the final viewer leaving stops native capture. Human video viewers do not enable JPEG screencasting. Agent screenshots remain available independently.
|
|
2720
2988
|
|
|
2989
|
+
A browser with cleanup still pending remains fenced until its native capability closes. That fence belongs to its project and browser resource: unrelated resources can still open. A retiring resource reports that cleanup is pending. Paint shutdown interrupts byte streams while joining native teardown, so a blocked stream cannot keep its own cleanup waiting indefinitely.
|
|
2990
|
+
|
|
2721
2991
|
While a view stays open, the controller renews its BrowserRuntime lease before expiry after rechecking the stored resource, authenticated viewer, and runtime authority. Renewal preserves the media connection and browser incarnation. Closing the view cancels renewal, closes the viewer's media peer while signaling is available, then revokes the lease and closes the transport. A stalled renderer has a bounded cleanup deadline; lease revocation still owns final media cleanup.
|
|
2722
2992
|
|
|
2723
2993
|
Select **Settings → General → Browser video → NVIDIA GPU (native)** to use the Rust
|
|
@@ -2840,7 +3110,9 @@ agl restart [--port 4097]
|
|
|
2840
3110
|
agl service install [startup options] | status [--json] | uninstall | protect
|
|
2841
3111
|
agl upgrade [--port 4097] [--registry <url>] [--grace-period-seconds 300] [--continue-sessions] [--json]
|
|
2842
3112
|
agl mcp [--port 4097]
|
|
2843
|
-
agl ticket list|get|create|update|move|comment|link|assign [options] [--json]
|
|
3113
|
+
agl ticket list|get|create|update|move|comment|link|unlink|assign|ask|answer [options] [--json]
|
|
3114
|
+
agl deploy status [TARGET] | history TARGET | probe TARGET [--json]
|
|
3115
|
+
agl release status [REPO] [--json]
|
|
2844
3116
|
agl feed list [--state failed] [--json] | acknowledge <row-id> --updated-at <ms> [--json]
|
|
2845
3117
|
agl foreground [options]
|
|
2846
3118
|
agl temp-password [--port 4097] [--ttl-hours 24]
|
|
@@ -2975,7 +3247,7 @@ A failure reference from the Errors dialog appears in those logs on the line the
|
|
|
2975
3247
|
|
|
2976
3248
|
### Rolling back to 41.x
|
|
2977
3249
|
|
|
2978
|
-
41.1.0 and the later 41.x releases are the ones
|
|
3250
|
+
This section is for 42.0.0 to 42.1.x: 41.1.0 and the later 41.x releases are the ones they roll back to. A release that plans deploys (AGL-909) is not rolled back to 41.x, which refuses its tickets; see the next section. 42.0.0 to 42.1.x keep a port's trusted-proxy secret sealed in the controller's database and never exports it, and `agl remote set` can store gateway sources, which 41.x cannot enforce. To roll back a port that this release serves behind a TLS reverse proxy:
|
|
2979
3251
|
|
|
2980
3252
|
1. Stop the controller and run `agl remote unset --port <port>`. It moves the port back to `http://localhost:<port>` and removes its passkey and every paired device, so the next start prints a setup code. A 41.x controller refuses to start on a configuration with gateway sources, and its refusal names this command.
|
|
2981
3253
|
2. Roll back and start the controller. Roll back only while no upgrade is open: 41.x refuses an upgrade transaction this release created.
|
|
@@ -2987,9 +3259,9 @@ The audit events of types 41.x does not know (`remote.*`, `device.*`) stay in th
|
|
|
2987
3259
|
|
|
2988
3260
|
### Rolling back from a release that plans deploys
|
|
2989
3261
|
|
|
2990
|
-
A later release that plans deploys (AGL-909) stores what 42.1.0 cannot read: release plans, maintenance windows and deploy plans on tickets, `affects` links, release links without a package, the Closed column, and the Configuration master's `fleet.deployTargets`. 42.1.0 and earlier refuse a ticket or a master that holds any of them, so roll such a release back to 42.
|
|
3262
|
+
A later release that plans deploys (AGL-909) stores what 42.1.0 cannot read: release plans, maintenance windows and deploy plans on tickets, `affects` links, release links without a package, the Closed column, and the Configuration master's `fleet.deployTargets`. 42.1.0 and earlier refuse a ticket or a master that holds any of them, so roll such a release back to 42.2.0 or a later 42.2.x. 42.2.0 reads all of it and acts on none of it: it probes no deploy target, plans and asks nothing, and moves no ticket to Closed.
|
|
2991
3263
|
|
|
2992
|
-
While the master holds `fleet.deployTargets`, 42.
|
|
3264
|
+
While the master holds `fleet.deployTargets`, 42.2.0 refuses every save of the master, from the CLI or the browser, and the refusal names `fleet.deployTargets`. It reads them, but saving them is left to the release that acts on them. To change the master after the rollback, save it without `fleet.deployTargets`; that removes the targets until you configure them again on the later release. Or remove them on the later release before rolling back.
|
|
2993
3265
|
|
|
2994
3266
|
### Migrating From `hcon`
|
|
2995
3267
|
|