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
Most clients should start with `CodexAppServer.start(_:)`. The one-call startup
68
+
API launches the local Codex app-server, verifies the selected Codex CLI against
69
+
SwiftASB's reviewed compatibility window, initializes the session, and throws
70
+
typed `CodexAppServerStartupError` values for missing, incompatible, or
71
+
unparseable CLI installs.
72
+
67
73
## Usage
68
74
69
75
Use SwiftASB when an app needs to show what Codex is doing right now, keep recent command and file activity visible, answer interactive requests, or build SwiftUI state around a running Codex turn.
Copy file name to clipboardExpand all lines: ROADMAP.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@
77
77
| Non-UI local history-reading helpers |`Partially shipped`|`CodexThread` now exposes a lightweight `HistoryWindow` page shape for recent local history, older or newer local windows around a known boundary turn id, centered `windowAroundTurn(...)` reads, centered `windowAroundItem(...)` reads, direct `ClosedTurn` reads for one turn, and convenience array helpers over those same windows. This gives non-UI callers an intentional path into the local history store without binding a UI-oriented observable, while still deferring a broader public cursor model, transcript search surface, and richer history-query helpers. |
78
78
| Public API curation |`Shipped / ongoing`| The source-organization pass has split app-wide model, MCP, thread-management, history, and observable companion values into focused public files while preserving `CodexAppServer`, `CodexThread`, and `CodexTurnHandle` as the three real owners. The connected public-surface review closed the v1 ownership model; post-v1 curation now includes app-server-owned project identity and thread source facts for launcher UI without exposing generated wire models. Future curation should stay tied to concrete public API additions. |
79
79
| DocC documentation |`Shipped / ongoing`|`Sources/SwiftASB/SwiftASB.docc/` contains a package landing page, public-handle extension pages, conceptual articles for app-wide capabilities, interactive lifecycle, thread management, history/observable companions, generated-wire boundary notes, and copy-pasteable walkthroughs for startup, progress/approval handling, diagnostics/history, and SwiftUI observable companions. The catalog is validated through Xcode `docbuild`; future work is ordinary stale-link, prose, and symbol-comment refinement as the public API grows. |
80
-
| Swift Package Index readiness |`Shipped`|`.spi.yml` declares `SwiftASB` as the documentation target, and Swift Package Index lists `gaelic-ghost/SwiftASB` with a documentation link, compatibility/build results, Package ID `9B5839D9-9551-473F-A939-841534A3FC55`, and a 2026-05-06 update timestamp for the latest confirmed indexed release. Recheck SPI after the `v1.3.0` tag is published. |
80
+
| Swift Package Index readiness |`Shipped`|`.spi.yml` declares `SwiftASB` as the documentation target, and Swift Package Index lists `gaelic-ghost/SwiftASB` with a documentation link, compatibility/build results, Package ID `9B5839D9-9551-473F-A939-841534A3FC55`, and a 2026-05-06 update timestamp for the latest confirmed indexed release. Recheck SPI after the `v1.3.1` tag is published. |
81
81
| Contributor documentation split |`Shipped`|`README.md` is now focused on Swift and SwiftUI package users, while `CONTRIBUTING.md` owns contributor setup, validation, DocC, live-test flags, generated-wire refresh, and PR expectations. |
82
82
|`CodexTurnHandle` live observable companion |`Partially shipped`|`CodexTurnHandle` owns a live `Minimap` companion that is attached when the handle is created and maintains current-state call snapshots for command, file-edit, dynamic-tool, collab-tool, and MCP item activity. It also now mirrors whether thread context compaction is active for the turn and supports explicit `complete()` handoff into a caller-owned sealed turn snapshot. |
83
83
| Additional turn event mapping |`Partially shipped`| The public event layer covers the current interactive lifecycle plus the item-start and item-complete events needed for observable call-state mirrors. Raw command-output and file-change-output deltas now stay internal as transport detail but drive the shipped `RecentCommands` and `RecentFiles` companions, and streamed or patch-updated payloads are preserved when later completed snapshots are thinner. Richer MCP-progress detail still remains internal, while warning, guardian-warning, config-warning, deprecation, MCP-server-status, remote-control-status, model-reroute, and model-verification notifications now surface through hand-owned diagnostic events. |
@@ -105,7 +105,7 @@
105
105
The next meaningful package step is no longer proving the v1 interactive
106
106
lifecycle, SPI visibility, basic history hydration, first-pass reconciliation,
107
107
or command-approval completion. Those slices now exist and shipped in the
108
-
`v1.3.0` baseline.
108
+
`v1.3.1` baseline.
109
109
110
110
The next meaningful work is to widen the reviewed app-server schema and protocol
111
111
coverage before adding more public query descriptors. Descriptors should compile
@@ -216,7 +216,7 @@ That means the current priority order is:
216
216
217
217
## V1 Readiness Checklist
218
218
219
-
This checklist records the work that made `SwiftASB` ready for the `v1.3.0`
219
+
This checklist records the work that made `SwiftASB` ready for the `v1.3.1`
220
220
tag. The goal was not to make every possible app-server feature public before
221
221
v1. The goal was to make the supported lifecycle honest, durable, well
222
222
documented, and intentionally shaped.
@@ -416,8 +416,8 @@ workflow earns them in a later feature release.
416
416
417
417
### Documentation And Examples
418
418
419
-
-[x] Update stale release references after the `v1.3.0` release.
420
-
Decision: README now names `v1.3.0` as the current released baseline and no
419
+
-[x] Update stale release references after the `v1.3.1` release.
420
+
Decision: README now names `v1.3.1` as the current released baseline and no
421
421
longer describes the package as early development.
422
422
-[x] Finish DocC symbol comments for the supported lifecycle, not just the
423
423
conceptual articles.
@@ -602,10 +602,10 @@ workflow earns them in a later feature release.
602
602
the `release/v1.0.0` branch on 2026-05-02 and on the
603
603
`release/v1.0.1-prep` branch on 2026-05-02.
604
604
-[x] Decide whether another targeted `v0.9.x` patch release is needed before
605
-
`v1.3.0`, or whether the remaining work should go straight into the v1
605
+
`v1.3.1`, or whether the remaining work should go straight into the v1
606
606
release branch.
607
607
Decision: no additional `v0.9.x` patch is needed. The remaining work should go
608
-
straight into the `v1.3.0` release branch.
608
+
straight into the `v1.3.1` release branch.
609
609
-[x] Prepare v1 release notes with explicit sections for public surface,
-[x] Add version-compatibility policy notes for the local Codex binary.
1260
1260
-[x] Refresh the compatibility window and promoted generated snapshot against the current `v0.124.0` schema dump once the added endpoint, notification, and field families have been classified.
1261
1261
-[x] Curate the public API before v1 by splitting large source files along existing responsibility boundaries where still helpful, tightening public names/defaults, and finishing targeted source-level symbol documentation for the supported lifecycle.
1262
-
Decision: completed for the `v1.3.0` boundary through the public API audit,
1262
+
Decision: completed for the `v1.3.1` boundary through the public API audit,
1263
1263
symbol inventory, source-comment pass, and focused public file organization.
1264
1264
-[x] Add the first DocC documentation catalog before v1, including a package landing page, public-handle topic groups, and conceptual articles for the interactive lifecycle, history companions, and generated-wire boundary.
1265
1265
-[x] Validate the DocC catalog through Xcode `docbuild` and document the maintainer command.
0 commit comments