Workspace
Files and artifacts
Create, read, mutate, copy, move, search, render, archive, extract, hash, and verify real artifacts.
Node Hub
Bob Nodes
Nodes are bounded units of work that BoBNet can route, run, inspect, approve, and verify. V1 is being built around a Windows-native console with local core Nodes plus first outreach Nodes for real provider work like GitHub and Google/Gmail.
V1 core
The first core Nodes are practical work engines.
The current V1 proof set covers local Windows workspace work, durable evidence, approvals, browser and desktop control, connector infrastructure, and safe side-effect handling.
Execution
Shell and sandbox
Persistent shell sessions, bounded command execution, local sandbox roots, snapshots, and cleanup.
Safety
Secrets and approvals
Scoped vault handling, permission denial, operator approval queues, budget policy, and audit reports.
Output
Documents and data
Markdown, PDF, zip packages, CSV profiling, charts, final checks, and durable output evidence.
Automation
Browser and desktop
Browser open/click/type/screenshot/state plus safe local desktop control for allowlisted actions.
Connectors
MCP and external tools
Connector discovery, allowed calls, policy denial, timeout evidence, and local runtime checks.
Control
Run fabric and timelines
Active run supervision, repeatable schedules, observability timelines, manifests, and trace reports.
Reliability
Packages and idempotency
Plugin package review, approved action routing, rollback planning, retry paths, and replay-safe mutations.
First outreach Nodes
Provider Nodes make BoBNet useful outside the local workspace.
The first outreach lane highlights provider-real work: GitHub for repositories and pull requests, and Google/Gmail for OAuth-backed draft, send, search, and readback workflows. These are intentionally approval-heavy because they touch real accounts.
GitHubSetup check, private proof repo, branch, commit, push, draft PR, comment, checks
Google/GmailOAuth setup, profile read, draft create/read, approved send, search, readback evidence
Email workflowDrafts, summaries, contact-list reports, and send-with-approval records
Follow-up automationCalendar event drafts, webhook triggers, and repeatable scheduled runs
Publishing lane
Node packages will live in the Library.
The Node Hub explains the capability groups. The Library handles reviewed package browsing and downloads.