hosted-agents

Build sandboxed background coding agents with pre-built images, warm pools, and multiplayer sessions.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/NT-boop-star/BRMV-tract --skill hosted-agents-nt-boop-star
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hosted-agents
Source: https://github.com/NT-boop-star/BRMV-tract/tree/main/antigravity/skills/hosted-agents
Command: npx skills add https://github.com/NT-boop-star/BRMV-tract --skill hosted-agents-nt-boop-star

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Running coding agents on local machines creates resource contention, inconsistent environments, and single-user constraints. This Skill provides the architecture and patterns for moving agent execution to remote sandboxed environments with fast startup, per-session isolation, and multi-client support. ## Core Features & Use Cases - Sandbox Infrastructure: Pre-build environment images on a 30-minute cadence, maintain warm pools, and use filesystem snapshots to eliminate cold-start latency. - API Layer and Multiplayer: Isolate state per session with SQLite or Durable Objects, stream events over WebSockets, and attribute commits to the prompting user via GitHub tokens. - Client Integrations: Implement Slack bots with repository classification, web interfaces with hosted VS Code, and Chrome extensions that extract DOM and React internals. - Use Case: A platform team wants to ship a background coding agent that opens PRs from Slack prompts. Use this Skill to design the image build pipeline, warm pool strategy, predictive warm-up on keystroke, and user-attributed PR creation flow. ## Quick Start Use the hosted-agents skill to design a sandboxed background coding agent with warm pools and Slack integration for my team.

Frequently Asked Questions about hosted-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce cold start latency for sandboxed coding agents?

Pre-build environment images on a 30-minute cadence with dependencies installed and caches warmed, then maintain a pool of pre-warmed sandboxes per repository. Start warming a sandbox as soon as the user begins typing so it is ready before they submit.

How do background agents create PRs as the user instead of a bot?

Use GitHub App installation tokens for cloning inside the sandbox, then set git config user.name and user.email to the prompting user's identity. The API layer uses the user's OAuth token to open the PR, so it appears authored by the human.

What sandbox providers work for hosted agent infrastructure?

The reference implementation uses Modal Sandboxes for near-instant startup and filesystem snapshots, paired with Cloudflare Durable Objects for per-session SQLite state and WebSocket hibernation. The patterns adapt to other providers with equivalent isolation models.

Can agents read files before git sync completes in a sandbox?

Yes, allow file reads immediately because recently changed files rarely overlap with the agent's research targets. Block only writes until synchronization finishes, queuing pending writes and flushing them once sync completes.

Why do sandboxed agent sessions lose work, and how do I prevent it?

Work is lost when sandboxes are recycled or time out before results are extracted. Always snapshot the filesystem before termination and build explicit extraction steps, such as pushing branches and creating PRs, into the session teardown flow.

What metrics should I track for a background coding agent?

Track sessions resulting in merged PRs as the primary success metric, plus time from session start to first model response, PR approval rate, and agent-written code percentage per repository. These indicate real value rather than vanity usage counts.