Agents

Envlet for Replit

Replit Agent runs in the cloud, so it gets Envlet through one secret rather than a local MCP server: an agent identity token in Replit Secrets.

Install
npm install @envlet/sdk
Run with its own identity
envlet run -- npm start
Say the word
Move us to Envlet.

Set up

  1. 01

    Add the MCP server

    Add ENVLET_TOKEN to Replit Secrets with a token for an agent identity, and call inject() at boot.

  2. 02

    Give it an identity

    Create an agent identity for Replit in the dashboard or let the migrate prompt do it. Its token opens one environment, and production starts fully withheld.

  3. 03

    Run it through Envlet

    Start Replit with envlet run. It sees the values for its identity and nothing else, and every read shows up under its name.

Questions

Can Replit read production secrets?
Not by default. A new agent grant withholds every current and future production variable. You allow specific names when you decide to.
Do agent identities count toward my plan?
No. Agents and CI identities are unlimited on every plan. Only humans are members.

Stop pasting .env files.

One command. The right values for whoever runs it.