hosted-agents

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

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/ludotype/game-adventurertown --skill hosted-agents-ludotype
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hosted-agents
Source: https://github.com/ludotype/game-adventurertown/tree/main/.agent/skills/hosted-agents
Command: npx skills add https://github.com/ludotype/game-adventurertown --skill hosted-agents-ludotype

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 and Client Layer: Isolate state per session with SQLite or Durable Objects, stream events over WebSockets, and ship clients for Slack, web, and Chrome extensions. - Multiplayer and Self-Spawning Agents: Attribute commits to the prompting user, support shared sessions, and let agents spawn sub-sessions for parallel work. - Use Case: A platform team wants a background coding agent that opens PRs from Slack prompts. Use this Skill to design the image build pipeline, warm pool strategy, GitHub token flow, and session state model. ## Quick Start Ask the agent to design a hosted background coding agent architecture with sandboxed execution, warm pools, and Slack integration for your repositories.

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 predictively when the user begins typing, not when they submit the prompt.

How do background agents commit code as the user instead of a bot?▼

Set git config user.name and user.email explicitly in the sandbox for each prompt, and create PRs using the prompting user's GitHub OAuth token rather than the app identity. Use GitHub App installation tokens only for repository cloning during image builds.

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

Yes, allow file reads immediately while blocking only writes until synchronization finishes. In large repositories, prompts rarely touch files changed in the last 30 minutes, so read-time staleness is safe while write conflicts are not.

What sandbox providers work for hosted agent infrastructure?▼

The reference implementation uses Modal sandboxes with filesystem snapshots and near-instant startup. Cloudflare Durable Objects handle per-session state with WebSocket hibernation, and the patterns adapt to other providers like Fly.io.

Why do sandboxed agent sessions lose completed work?▼

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 indicate a hosted coding agent is successful?▼

Track sessions resulting in merged PRs as the primary success metric, along with time from session start to first model token, PR approval and revision rates, and the percentage of agent-written code across repositories.