Skip to main content
Monk’s local companion, monk-agent, serves a dashboard in your browser at http://127.0.0.1:7419. It only listens on your own computer. This is where you review plans, approve privileged actions and enter credentials, so none of that goes through the chat with your coding agent.

​
Opening it

You rarely open it by hand. When Monk needs something from you, such as a plan to approve or a credential to enter, it opens the dashboard at that item. If the browser didn’t open, or you closed the tab, ask your agent:
Monk gives you a working link. If you’re not signed in yet, it gives you the sign-in link first. If port 7419 is taken, monk-agent uses the next free port up to 7429. Use the link your agent gives you.

​
Signing in

The dashboard needs the same Monk sign-in as your agent. A tab without a session shows Dashboard locked with a Sign in to unlock button. After you sign in, it takes you back to the item you were opening.

​
Work

Approvals, requests and tasks from your coding agents. Each item says what it’s for and which project it belongs to:
  • Approvals: deployment plans, cluster creation and deletion, CI/CD and Watcher setup, and other privileged actions. Each one shows what will change. Approve or decline.
  • Credential requests: a form for a cloud or service provider. Depending on the provider you type values, upload a key file or sign in to the provider.
  • Secret requests: single values such as a database password, with a generator for random values where it makes sense.
  • TLS certificates: add a domain’s certificate and key.
When you have several projects open, Work shows items from all of them. You can narrow it to one workspace.

​
Environments

Your app as it runs in each environment, live from its cluster: the services, how they connect and their state.

​
Clusters

Every cluster this computer knows about, with its provider, region and reachability. Open a cluster for its details, peers, a map of what runs on it and the secrets that apply to it. Creating a cluster opens a review of the provider, region, instance type and count, and any GPUs, before anything is provisioned. Deleting one asks for approval.

​
Vault

What this computer holds for your agent, in three groups: cloud accounts, local secrets and cluster secrets. You can see what’s stored and where it applies. Values are never shown, and never handed back to the agent. Locally, values are kept in your OS keychain, or in an encrypted file where there is no keychain. See Credentials.

​
This machine

The local Monk agent itself:
  • Agent: version, how long it has been running, sign-in state and the last error.
  • Monk runtime: the local Monk CLI and daemon.
  • Where things are kept: the secrets store and state Monk uses on this computer.
  • Connected editors: the coding agents that have connected, with their workspace and when they were last seen.
  • Notifications: a system notification, a sound, or bringing the browser forward when an agent needs your approval or a secret.
  • Diagnostics: checks the current workspace’s setup. Run it when a deploy or configure step reports something you don’t understand.
If something is off here, ask your agent /monk check installation status, or see Troubleshooting.

First deployment

Where the dashboard appears in a deployment