How debaucheryparty/packets works
Packets is a remote development-workload system: a developer uses the CLI to send project work to a daemon, which schedules execution on remote capacity and returns logs and artifacts. Workspace snapshots support source transfer and persistent caching; separate capabilities cover environments, persistent subspaces, services, transactions, Android workflows, and MCP access. The README and daemon wiring establish the main flow, but sampled excerpts do not expose every CLI RPC or scheduler-to-worker call, so uncertain links are omitted.
Main entry points: scheduler/server.go Job scheduler API · packetsd/main.go Packets daemon · workspace/server.go Workspace API · packets/main.go Packets CLI
Components 24
Client workflows
- Packets CLI
cmd/packets/main.go - Build and exec
internal/cli/build.go - Project sync
internal/cli/sync.go - MCP server
internal/mcp/server.go
Remote execution
- Packets daemon
cmd/packetsd/main.go - Job scheduler API
internal/scheduler/server.go - Job dispatcher
internal/scheduler/dispatch.go - Remote executor
internal/worker/executor.go - Toolchain routing
internal/toolchain/router.go - Job database
internal/storage/sqlite.go
Workspace and artifacts
- Snapshot client
internal/workspace/client.go - Workspace API
internal/workspace/server.go - Object storage
internal/storage/objectstore.go - Artifact handling
internal/workspace/artifact.go
Persistent workspaces
- Subspace API
internal/subspace/server.go - Subspace manager
internal/subspace/manager.go - Workspace transactions
internal/transaction/manager.go - Remote services
internal/service/manager.go
Environment and integrations
- Environment manager
internal/environment/manager.go - Android tooling
internal/android/setup.go - Execution policy
internal/policy/engine.go - Build providers
internal/provider/provider.go
Other components
- Developer
- AI assistant
Connections 28
- Developer → Packets CLI: runs commands
- Packets CLI → Build and exec: selects workflow
- Build and exec → Job scheduler API: submits jobs
- Project sync → Workspace API: uploads snapshots
- Build and exec → Snapshot client: syncs project
- Snapshot client → Workspace API: transfers snapshots
- Workspace API → Object storage: stores chunks
- Packets daemon → Job scheduler API: registers API
- Packets daemon → Job dispatcher: constructs dispatcher
- Packets daemon → Remote executor: constructs executor
- Packets daemon → Workspace API: registers API
- Job scheduler API → Job dispatcher: dispatches jobs
- Job scheduler API → Job database: records jobs
- Job scheduler API → Execution policy: checks approval
- Job scheduler API → Build providers: fetches artifacts
- Remote executor → Toolchain routing: routes commands
- Remote executor → Object storage: reads snapshots
- Job scheduler API → Workspace API: serves artifact data
- Packets CLI → Artifact handling: downloads outputs
- AI assistant → MCP server: invokes tools
- MCP server → Job scheduler API: requests job data
- MCP server → Execution policy: requests approval
- Packets daemon → Subspace manager: constructs manager
- Subspace API → Subspace manager: manages subspaces
- Packets daemon → Workspace transactions: constructs manager
- Packets daemon → Remote services: constructs manager
- Packets CLI → Environment manager: checks environments
- Environment manager → Android tooling: resolves Android