ADP — Agentic Developer Platform

What you can do with ADP

Use any coding tool. Scale to hundreds of developers.

Connect Claude Code, Codex, or Kimi Code through one ADP gateway. Developers sign in with GitHub using short-lived, automatically refreshed credentials. As teams grow, organizations can enforce budgets and rate limits at every level.

• Choose your coding tool with one simple setup. Install the ADP CLI once and connect Claude Code, Codex, or Kimi Code to the same ADP gateway. Each tool has a one-time configuration step, then you can use the tool that fits your work through one ADP connection.
• Sign in with GitHub, without long-lived API keys. Use GitHub sign-in instead of managing a separate model API key. ADP gives your machine short-lived credentials and refreshes them automatically, without requiring individual AWS credentials for everyday tool use.
• Enforce spending controls across your organization. Set and enforce budgets and rate limits for hundreds of developers at the organization, department, team, and user levels, with usage and cost visibility at each level.

Run coding agents in the cloud

• Delegate complex, long-running work from GitHub. Mention a cloud-hosted agent in an issue or pull request. ADP runs the task without requiring you to keep a local coding session open.
• Use the right agent persona. Product and PM agents shape and coordinate work; architect, developer, reviewer, and operations agents handle design, implementation, review, and deployment.
• Choose a Claude or Codex agent stack. ADP supports two cloud agent stacks: one built on the Claude Agent SDK and one on the native Codex SDK. Mention @agent-developer or @agent-codex-developer to choose a stack for implementation.
• Watch and control live runs. Stream agent progress in the ADP UI or CLI. For runs that support live controls, pause, resume, steer with new instructions, or abort them while they run.

Deploy and debug across AWS accounts

• Work where your application runs. Connect development AWS accounts to ADP so agents can deploy applications and investigate runtime issues in the target account.
• Use the right account for each developer. Different developers can connect different AWS accounts and select the account an agent should use for a run.
• Govern access with scoped IAM roles. Define the services and resources an agent may access in each account. ADP assumes the authorized role for the run and gives the agent short-lived credentials. See customer AWS setup.

Invoke agents from your workflows

• Connect CI/CD pipelines and applications. Submit authorized agent tasks through the Task API using a registered service identity.
• Follow progress in real time. Read task status and stream progress events, with cursors that let clients reconnect to retained updates.
• Use the results in your workflow. Retrieve task results and artifacts to drive the next pipeline or application step.

Build agents for your own domain

• Define agents for your work. Create personas, skills, and domain tools or workers for workflows beyond coding.
• Reuse ADP's foundations. Run domain agents with the shared agent runtime, model gateway, identity, and integrations.
• Explore the Cyber app. The optional Cyber app shows this approach in practice with malware analysis and URL and domain investigations. It brings its own persona, skills, workers, and sandbox infrastructure.

Built as a SaaS platform

• Serve many organizations from one installation. Manage organizations, departments, teams, users, and memberships in one ADP deployment.
• Keep tenants separate. Tenant-aware identity, roles, and access checks scope each organization's users and activity.
• Administer the platform centrally. Onboard users, manage organization connections, and view agent activity in the admin interface.
• Isolate Bedrock costs by AWS account. Teams can bring their own AWS accounts. Map a team to a verified account so its model requests are billed there and use that account's Bedrock quotas.

Getting started

Deploy ADP in your AWS account

From a clean checkout, choose an AWS profile and a published ADP release. Confirm the target account, then run the single deployment entry point:

aws sts get-caller-identity --profile YOUR_PROFILE \
  --query '{Account:Account,Arn:Arn}' --output table
./deploy.sh --aws-profile YOUR_PROFILE --release ADP_RELEASE

Replace the placeholders with your profile and an existing ADP release tag. deploy.sh installs the platform, gateway, and cloud agent stack. Follow the deployment quickstart for prerequisites, installation, upgrades, and verification. An AI coding agent can follow the agent deployment guide.

After deployment, complete the GitHub App setup and approve developer accounts. To route a team's Bedrock usage to its own AWS account, follow the Bedrock account routing guide.

Run coding agents locally through ADP

If your organization already runs ADP, you can start here. Your coding tool runs on your machine and uses the ADP gateway for model access. The example below uses Codex: you need it installed, an approved ADP account, and a deployment with GitHub sign-in enabled. Replace https://YOUR_ADP_DOMAIN/api with your deployment's gateway URL.

1. Install the ADP CLI from your deployment:

   curl -fsSL https://YOUR_ADP_DOMAIN/api/cli/install.sh -o adp-install.sh
   sh adp-install.sh --gateway-url https://YOUR_ADP_DOMAIN/api

   The installer adds ~/.adp/bin to your shell configuration. Open a new terminal before the next step.

2. Sign in with GitHub:

   adp login

   Confirm that the short code in your terminal matches the browser approval page, then sign in with GitHub and approve the connection.

3. Configure Codex:

   adp codex setup

4. Run Codex through ADP:

   adp codex

The same ADP login works across your coding tools. For Claude Code, run adp claude setup and adp claude after signing in. Kimi Code uses the same login but needs the separately configured ADP Kimi adapter. See CLI Setup in your deployment for tool-specific instructions. If your sign-in session expires, run adp login again.

Run coding agents in the cloud

After an administrator sets up the ADP GitHub App for your organization and grants you access, comment on an issue in a connected repository to start a cloud agent:

@agent-developer please implement this issue.

If your deployment enables the native Codex SDK agent, use @agent-codex-developer instead. Follow the agent's progress in GitHub.

For a deeper view of the platform, see ARCHITECTURE.md and the hosted agent catalogue.

Contributing and license

See CONTRIBUTING.md for the development workflow. ADP is licensed under the Apache License 2.0.