Skip to main content
Give your app the API keys, passwords and settings it needs. Values go through forms in the local dashboard. They never pass through the conversation.

​
Before you start

​
Ask Monk for a secret

A secret form opens in the local dashboard. Type the value there, or use the generator for a random password. Don’t paste secrets into chat. If you do by accident, rotate the value. See which secrets exist (names only, never values):
Remove one:

​
Where secrets live

Monk pushes a local secret to the cluster when a deploy needs it, or when you ask:
Pushing a secret to a cluster, or adding one there, opens an approval first.

​
Change settings

Non-secret settings, such as environment variables, ports and sizes, live in the MANIFEST. Ask for the change; your coding agent edits the MANIFEST and Monk validates it:

​
What you review

The change shows up in the next deploy plan in the local dashboard, with the services it affects. Running services pick up new settings when they are redeployed, which happens after you approve.

​
What you get

Settings and secrets injected into the services that use them. Connection settings between services (database hosts, URLs, passwords Monk generated) are wired for you.

​
Next