Replit Agent

Plan

1. SupportsWork planning: Supports

   Work planning, supports. Plan mode turns a request into an ordered task list before any code changes, and Core and Pro add a shared Kanban board; planning stays in the team's tracker.

Build

1. Codebase context: Supports

   Codebase context, supports. Agent works from the project it built or imported, with workspace instructions and skills. It does not index the wider set of repositories a team owns.

2. Replit AgentCoreCoding: Core

   Coding, core. This is half of Replit Agent's primary role, writing and changing a full-stack app's code from a plain-language request, in Free, Power, or Max mode.

3. Agent runtime: Core

   Agent runtime, core. The Replit Project Editor and mobile app are where builders chat with Agent, watch the app run, and accept, roll back, or apply its work from background tasks.

4. Tool execution: Supports

   Tool execution, supports. Agent runs commands in its workspace, connects to services through connectors and MCP, and can use Replit-managed AI integrations without separate API keys.

Validate

1. Debugging: Supports

   Debugging, supports. Errors and logs from the running app feed Agent's proposed fixes, and checkpoints let a builder roll back when a fix makes things worse.

2. Testing: Supports

   Testing, supports. App Testing has Agent click through the app in a real browser in Power and Max modes, but it does not replace a team's automated test suite.

3. TouchesCode review: Touches

   Code review, touches. Agent reviews its own code as it builds, but Replit offers no pull request review, so review ownership stays with the team.

4. Application security: Supports

   Application security, supports. The Security Center scans dependencies for known CVEs, and Enterprise can require scans and block publishing by severity, but a clean scan does not cover the app's own code. Replit patches base images and language tooling itself, and some fixes reach a live app only on republish. In its Oct 22, 2026 advisory, Replit says it applied the eMudhra certificate fix to 95% of published apps automatically. It asked owners to republish Python and Node.js apps, and PHP apps where used.

Ship

1. Source control: Supports

   Source control, supports. Every Agent checkpoint is a Git commit that can sync to GitHub, and Enterprise can require a Git remote before publishing, but GitHub stays the system of record.

2. CI/CD: Core

   CI/CD, core. This is the other half of the primary role, publishing Agent-built apps to Replit's Autoscale or Reserved VM deployments, with a separate production database created at publish.

Operate

1. Observability: Supports

   Observability, supports. Published apps include logs, basic analytics, and App Monitoring health checks and alerts, and Enterprise reports usage and audit logs. Since Oct 22, 2026, Monitoring Agent can read production logs and metrics, investigate an alert, validate a fix, and deploy it when the owner turns on auto-publish in Publishing settings. Incident management stays in the team's own tools.