On May 23, 2026, gihyo.jp published VS Code 1.121 Released: Standard Support for Mermaid Diagrams and YAML Front Matter in Markdown Preview, Remote Agent Support ── Preserving Remote Sessions via Agent Host Protocol (AHP). The Agent Host Protocol (AHP) is a new protocol that retains editor-agent sessions on the server side, preserving agent state across network disconnections, device reboots, and location changes. Following the preview of the Agent Window introduced in VS Code 1.120, this marks a turning point toward standardizing a remote-first agent execution model.
From the perspective of supporting mid-sized enterprise engineering organizations through custom development, this signifies a transition from "individual agents confined to local VS Code" to "organization-wide shared hosted agents." The momentum behind hosted agent operations—which we previously explored in Google Managed Agents + Antigravity 2.0 Custom Development—is now aligning with client-side implementations in VS Code. In this article, we examine the architecture and operational design of remote agent platforms built on AHP from a custom development perspective.
Why AHP changes the prerequisites of remote development
| Dimension | Conventional VS Code Remote | VS Code 1.121 + AHP |
|---|---|---|
| Agent execution environment | Client device | Persistent server / container |
| Session persistence | Terminates when editor closes | Persists on server |
| Long-running tasks | Halts on device sleep | Server completes execution |
| Moving between locations | Work interrupted | Seamless resumption |
| Permission boundaries | Personal device permissions | Organization-managed permissions |
| Audit Logging | Local to personal device | Centralized server logs |
| Cost structure | Requires high-spec devices | Consolidated on server |
In essence, AHP shifts the paradigm from "an era where the IDE is self-contained on the device" to "the IDE as a window into remote agents."
Three architectural shifts brought by AHP
Shift 1: From "individual agents" to "organization-wide shared agents"
Until now, tools like Copilot, Cursor, and Codex were agents tied to each individual's device. With AHP, teams can operate "shared hosted agents across the team," running under unified prompt conventions, identical tool permissions, and consistent audit logs. In custom development, we can deliver standard agent specification design alongside team-wide rollouts as an integrated package.
Shift 2: From "local development" to "fleet development"
AHP server-side agents can maintain tens to hundreds of sessions concurrently. In custom development, we can propose operational foundations for agent fleets (parallel execution across multiple agents) combined with our Anthropic Routines / Claude Code custom development offerings.
Shift 3: From "device governance" to "server governance"
Because sessions are centralized on the server, the center of gravity for auditing, permissions, and secret management moves to the server side. In custom development, designs must extend the developer device governance addressed in our GitHub Internal Repo Breach + VSCode Extension Custom Development coverage all the way to server-side governance.
Five phases to implement a VS Code AHP remote agent platform
Phase 1: Current state assessment (2 weeks)
- Inventorying existing VS Code Remote / Codespaces usage
- Assessing device specs, network topology, and VPN configurations
- Auditing active AI coding tools (Copilot / Cursor / Codex)
- Defining security requirements (code exfiltration / client data)
- Confirming engineering organization scale (team count / headcount)
Phase 2: AHP host platform design (2–3 weeks)
- Execution platform: Kubernetes / VM pools / Codespaces
- Authentication: OIDC + organizational IdP federation
- Permission isolation: Project-level namespaces
- Secret management: Vault / Secrets Manager integration
- Audit logging: OpenTelemetry → SIEM
- Networking: VPN / private endpoints
Phase 3: Phased rollout (3–4 weeks)
- 2-week operation with a pilot team (5–10 members)
- Measuring performance, latency, and costs
- Standardizing prompt conventions and tool permissions
- Testing session reconnection and failover
- Formulating company-wide rollout plan based on pilot results
Phase 4: Organizational adoption (2–3 weeks)
- Role definitions (agent operators / users / auditors)
- Creating onboarding materials
- Incident response runbooks
- Monthly reviews / KPI dashboard
- Migration procedures from legacy IDE environments
Phase 5: Monthly operational reviews (ongoing)
- Session utilization rate / concurrency counts
- Average task completion time / token consumption
- Audit anomaly detection count
- License and infrastructure cost trends
- Tracking VS Code / AHP specification updates
Standard technology stack set for custom development
| Layer | Recommended technology | Alternative |
|---|---|---|
| Editor | VS Code 1.121+ | Codespaces / Cursor |
| Execution platform | Kubernetes（EKS / GKE） | Nomad / ECS |
| Agent | Claude Code / Codex / Copilot | Cursor Composer |
| Authentication | Auth0 / Okta + OIDC | Microsoft Entra ID |
| Secrets | HashiCorp Vault | AWS Secrets Manager |
| Audit Logging | OpenTelemetry → SIEM | Datadog Logs |
| Network | Tailscale / Cloudflare Tunnel | AWS PrivateLink |
| Visualization | Grafana / Kibana | Datadog |
Which projects need this and which do not
| Projects requiring this | Projects not requiring this |
|---|---|
| Organizations with 20+ developers | Freelancers / 5 or fewer members |
| Handling client data / regulated industries | Self-contained OSS projects |
| Frequent long-running tasks (large refactors, etc.) | Primarily short PoCs |
| Mixed office and remote presence | Stationed at a single physical location |
| AI coding standardization is an executive priority | Individual optimization is sufficient |
Six clauses to include in client contracts
| Clause | Details | What the client should verify |
|---|---|---|
| Session data ownership | Server retention period / handover upon offboarding | Legal / IP agreements |
| Model selection accountability | Approval process for adopted LLMs | Segregation by confidentiality level |
| Permission boundaries | Project / team / individual | Existing IdP roles |
| Availability SLA | Uptime / RTO / RPO | Tolerable development downtime |
| License assignment | By agent / model | Commercial use terms |
| Handover Upon Project Completion | Configurations + audit logs + prompt assets | Internal operational continuity |
Client-side ROI estimate (assuming 80 developers / concurrent AI coding)
| Item | Individual agent operation | AHP remote platform | Difference |
|---|---|---|---|
| Device spec upgrades (annual) | ¥16,000,000 | 4 million yen | -12 million yen |
| License redundancy (annual) | 7.2 million JPY | 4.8M JPY | -¥2,400,000 |
| Long-running task re-run loss (annual) | 800h | 120h | -680h |
| Audit support workload (annual) | 280h | 90h | -190h |
| Annual incident data leak risk loss | ¥12,000,000 | ¥3,000,000 | -9 million yen |
| Annual benefit | — | — | Approx. ¥28,000,000 equivalent + improved developer experience |
Even calculated at an hourly rate of ¥8,000, this yields an estimated annual benefit exceeding ¥24,000,000. While the table above is an estimate based on certain assumptions, organizations with significant overlap in device specs and licensing will find it easier to recoup their platform investment.
Five common pitfalls
Pitfall 1: Assuming "Codespaces is sufficient" without validation
Codespaces assumes a GitHub environment. For internal IdPs, on-premises Git, or regulated industries, AHP combined with a self-hosted platform becomes necessary. Start with a hybrid design based on specific use cases.
Pitfall 2: Failing to govern models and prompts
Even if consolidated on the server, having uncontrolled models and prompts mixed across teams fragments output quality. Establish prompt conventions and a model approval process early on.
Pitfall 3: Passing secrets directly to agents
Agents routinely leak sensitive credentials into logs. Mandate dynamic tokens via Vault or Secrets Manager and prohibit passing plain-text secrets.
Pitfall 4: Collecting audit logs without analyzing them
Merely streaming logs into OpenTelemetry or a SIEM provides no detection value. Define anomalous prompts and irregular tool invocations during the initial phase.
Pitfall 5: Executing migration via an all-at-once cutover
An all-at-once cutover from VS Code Remote to AHP carries a severe risk of halting development. Mandate a phased migration segmented by team or project.
90-day action plan
| Week | Action |
|---|---|
| Week 1〜2 | Current state audit (Remote / Codespaces / AI products / IdP) |
| Week 3〜4 | AHP host platform design + pilot PoC |
| Week 5〜6 | Prompt conventions / permission boundaries / audit design |
| Week 7〜8 | Pilot team 2-week operation + evaluation |
| Week 9 | Training content + migration runbook preparation |
| Week 10〜13 | Phased team rollout + launch of monthly reviews |
Conclusion — An era where "IDEs become a window into remote agents"
VS Code 1.121's Agent Host Protocol repositions the IDE from "an editor confined to a local device" into "a console for remote agents." For those supporting mid-sized enterprise development organizations through custom development, constructing AHP host infrastructure design, prompt/model governance, audit governance, and monthly reviews as a cohesive whole will undoubtedly become the standard approach going forward.
Challenges like "skyrocketing hardware upgrade costs for personal PCs," "fragmented AI coding tools across departments," and "long-running tasks halting when devices sleep" require vastly different solutions depending on organizational size and existing IdP or network architectures. We provide customized estimates for designing and migrating to an AHP-based remote agent platform tailored to your situation, so please feel free to reach out through our contact form.
Sources
- VS Code 1.121 Release ── Agent Host Protocol (gihyo.jp)
- VS Code 1.120 Agents Window Preview (gihyo.jp)
- Google Managed Agents + Antigravity 2.0 Custom Development (GH Media)
- Anthropic Routines / Claude Code Custom Development (GH Media)
- GitHub Internal Repo Breach + VSCode Extension Governance Custom Development (GH Media)
