Menu

Two Paths to Take an Agent Runtime onto Mobile: a Remote Console and an On-Device Go SDK
📰

Two Paths to Take an Agent Runtime onto Mobile: a Remote Console and an On-Device Go SDK

DEV Community: go·rebornace·2 days ago
#g7vBu9nn
#devtogo#devto#dev#device#approval
Reading 0:00
15s threshold

Project: Baize — a team-facing AI assistant runtime (Go 1.25+, MIT)

Repo: https://github.com/rebornace/baize

This is the follow-up to From a Single Agent Loop to an Auditable Runtime: Baize's Architecture . That post covered the server-side runtime; this one focuses on the two mobile paths.

Baize is a single-process Agent runtime written in Go that sits alongside your business systems, consolidating the LLM, tools, legacy HTTP APIs, and human checkpoints into auditable runs. Once the server side was stable, mobile was not built as a simple mobile web page. Instead, Baize offers two paths: one uses a Capacitor shell to remotely control the full console, so you can approve work on the go with zero development; the other compiles the Go orchestration core into an Android AAR and an iOS XCFramework via gomobile, so the conversation runs on the device and the UI is drawn entirely by your own app.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.