hosted-agents

Build sandboxed remote infrastructure for background coding agents with warm pools and multiplayer sessions.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill hosted-agents-lgj-jonathan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hosted-agents
Source: https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills/tree/main/context-engineering/skills/hosted-agents
Command: npx skills add https://github.com/LGJ-Jonathan/Jonathan_Global_Claude_Skills --skill hosted-agents-lgj-jonathan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Running coding agents on local machines limits concurrency, creates inconsistent environments, and blocks collaboration. This Skill provides the architecture and patterns for hosting agents in remote sandboxed environments with near-zero perceived startup latency. ## Core Features & Use Cases - Sandbox Infrastructure: Pre-built environment images on a 30-minute cadence, warm pools, predictive warm-up on keystroke, and filesystem snapshots for instant session restore. - API and Client Layer: Per-session state isolation with SQLite, real-time WebSocket streaming, and multi-client sync across Slack, web, and Chrome extension interfaces. - Multiplayer and Self-Spawning Agents: Sessions shared across team members with per-user commit attribution, plus primitives for agents to spawn and monitor sub-sessions. - Use Case: A platform team wants engineers to trigger background coding agents from Slack that open PRs under the requester's identity. This Skill guides the sandbox lifecycle, GitHub token flow, and repository classification needed to ship that system. ## Quick Start Ask the agent to design a hosted background coding agent system with pre-warmed sandboxes, per-session state, 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 so sandbox startup only requires a fast git delta sync. Maintain warm pools of ready sandboxes and start warming predictively when the user begins typing, not on submit.

How do background agents commit code under the user's identity?

Set git config user.name and user.email explicitly in the sandbox for each prompt, since background agents are not tied to a user during image builds. Create PRs through the API layer using the prompting user's GitHub OAuth token, not the app identity.

What sandbox providers work for hosted agent infrastructure?

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

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

Yes, file reads are safe before sync completes because prompts in large repositories rarely touch files changed in the last 30 minutes. Block only writes until synchronization finishes to prevent conflicts, queueing pending writes in the meantime.

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 agent product is working?

Track sessions resulting in merged PRs as the primary success metric, along with time from session start to first model token, PR approval rate, and agent-written code percentage per repository. Avoid vanity metrics like raw session counts.