Chat, history, settings.
GlassGPT 4.0 release era
Native by design. Modular by default.
A native SwiftUI chat client rebuilt around clear modules, actor-owned runtime, and steadier recovery.
- 4.5 to 4.10 Native era
- 16 modules Clear seams
- 1 runtime owner Actor-owned
- Release-grade Hard gates
4.0 architecture map
Apple-platform AI client
Production wiring only.
Focused stores and flows.
Actor plus evaluators.
SwiftData and Keychain.
Direct, gateway, files.
One runtime owner. One production root.
4.0 in four moves
A shorter way to describe the release line.
Native rebuild. Clear seams. One runtime owner. Harder release gates.
Native
SwiftUI from the start
The client was rebuilt in Swift, SwiftUI, and SwiftData.
Modules
Clear package boundaries
UI, transport, persistence, and runtime stay separate as the app grows.
Runtime
One owner for reply state
ReplySessionActor owns mutable reply state while evaluators keep decisions pure.
Discipline
Shipping got stricter
CI, accessibility, docs, localization, and performance checks became part of the release contract.
System
A few rules do most of the work.
Keep UI on the surface. Wire production once. Mutate reply state in one place.
Surface
UI stays at the edge
Chat, history, settings, markdown, and previews stay in the surface layer.
Composition
Production wiring happens once
The composition root owns assembly so dependencies do not drift.
Runtime
Reply state has one owner
ReplySessionActor owns mutation while evaluators keep recovery and terminal decisions explicit.
Transport
Routing stays outside the UI
Direct OpenAI, optional gateway routing, and file flows stay in transport.
16
Package targets with clean import boundaries.
1
Mutable runtime owner for reply state.
4
Pure decision evaluators across runtime flows.
22
Expanded release and CI gates in 4.x.
Release timeline
Five short milestones.
Curated milestones from the real changelog.
Native rewrite
- Complete native SwiftUI rewrite of the chat client.
- SwiftData and package boundaries land together.
Runtime ownership
- ReplySessionActor becomes the single mutable runtime owner.
- Composition root and coordinators replace broader controller ownership.
Engineering rigor
- Typed throws, observability, and accessibility expand the safety net.
- CI grows into a real engineering gate system.
Boundary tightening
- Settings and history ownership are tightened across application, presentation, and composition.
- Release-readiness, localization, and documentation checks become standard.
Reliability line
- Gateway modes, direct validation, and fallback handling land in transport.
- Runtime, settings, and streaming behavior are repeatedly hardened.
Support
Support, source, and privacy.
Local-first. Bring your own API key. Optional gateway routing.
English support page