| type |
architecture |
| last-updated |
2026-09-27 |
| updated-by |
e6efc1f1 |
| sources |
docs/wiki/Architecture Overview.md |
docs/wiki/Background Subagents and Ownership.md |
docs/wiki/Conventions and Patterns.md |
docs/wiki/Execution Lifecycle.md |
docs/wiki/Operator Web Control Surface.md |
docs/wiki/Prompt Architecture.md |
docs/wiki/Session Persistence.md |
docs/wiki/Setup and Configuration.md |
docs/wiki/Troubleshooting.md |
|
| summary |
Navigable entry point for the Fro Bot Agent project wiki |
An Obsidian-powered project wiki maintained by Fro Bot. This vault provides human-readable documentation covering the architecture, subsystems, and conventions of the fro-bot/agent Bun monorepo — the GitHub Action, the Discord-first Gateway and operator web surface, the sandboxed workspace executor, the patched OpenCode harness, and the shared runtime/session primitives underneath them.
Getting started: Open this folder (docs/wiki/) as a vault in Obsidian for the best experience — graph view, backlinks, and search work out of the box. For the Dataview plugin (optional), install it from Obsidian's community plugins after opening the vault.
| Page |
Type |
Summary |
| Architecture Overview |
architecture |
Monorepo structure, module map, and the boundary between gateway execution and workspace checkout management |
| Execution Lifecycle |
architecture |
Phase-by-phase walkthrough of a single action run, from bootstrap through drain, review reconciliation, brokered push, and the final invocation outcome |
| Page |
Type |
Summary |
| Session Persistence |
subsystem |
How agent memory survives across CI runs via cache, SDK sessions, S3 object store, and pruning |
| Background Subagents and Ownership |
subsystem |
How the harness tracks, drains, and settles background subagent work that outlives the turn that dispatched it |
| Prompt Architecture |
subsystem |
How the multi-section XML-tagged prompt is assembled and why each section exists |
| Setup and Configuration |
subsystem |
Tool installation, configuration assembly, credential management, cache strategy, and oMo opt-in |
| Operator Web Control Surface |
subsystem |
Authenticated browser surface for gateway runs, including checkout provenance, preparation outcomes, and live observation |
| Page |
Type |
Summary |
| Conventions and Patterns |
convention |
Coding conventions, architectural patterns, and anti-patterns enforced across the project |
| Page |
Type |
Summary |
| Troubleshooting |
convention |
Common failure symptoms and their causes across action execution, persistence, setup, and gateway runs |
- Audience: Human developers — contributors, reviewers, and maintainers
- Content: Descriptive documentation (how the system works, why decisions were made)
- Not: Prescriptive agent instructions — those live in AGENTS.md
- Updated: Weekly via Fro Bot scheduled runs, delivered as auto-merged PRs
- Format: Obsidian double-bracket wikilinks for cross-references; YAML frontmatter for metadata
- Optional: Install the Dataview community plugin for frontmatter queries (e.g.,
TABLE summary FROM "")