References
These sources inform the agent documentation and autonomy boundary; they are not bundled dependencies.
Canonical Voidscape sources#
skill/SKILL.md— installed agent behavior and approval workflow.docs/architecture.md— data flow, pricing, backends, and security posture.docs/workflow.md— guided decision flow.docs/harness-support.md— browser, remote-host, and install boundaries.docs/ROADMAP.md— planning and parked work.- Agent-docs information architecture.
- Browser-bridge security contract.
- Browser-bridge implementation contract.
- MCP host spike and no-go recommendation.
Official harness documentation#
- Codex Chrome extension
- Codex remote connections
- Codex app browser
- Claude Code with Chrome
- Claude Code Remote Control
Vendor documentation supports vendor-documented labels only. Voidscape verification requires its own scoped test evidence.
Official provider documentation#
- Groq Speech to Text — model speed factors, file limits, and transcription endpoint behavior.
- Groq Batch API — asynchronous audio batch availability, cost model, retention, and processing windows.
Provider performance numbers describe provider-side behavior, not a Voidscape end-to-end SLA.
Pattern sources#
- Herdr agent docs — information-architecture inspiration: separate harness support, authority, workflow, explanation, and automation.
- screenpipe — optional companion patterns for local desktop capture, health/freshness reporting, and authenticated localhost services.
- automated_browser — learn-from-only patterns for structured browser actions and replayable session evidence.
Voidscape does not copy upstream code or adopt screenpipe's always-on recording as its core. It does not adopt an autonomous browser loop, full-page cloud uploads, raw eval, or cookie scraping from automated_browser. Review each upstream license and current design before any future code reuse.