Skip to content
    monk.io
    Get startedStart

    Install Monk.

    One command sets it up in the coding agents on your computer. Then open your app and ask for a plan.

    Install Monk

    In a terminal, on the computer you code on

    Run this in a terminal. It finds the coding agents on this computer, shows what it will change, and asks before changing anything. It offers to sign you in at the end.

    1. 1Finds your agents
    2. 2Shows the plan
    3. 3Asks, then signs you in
    What it does
    • Installs Monk, or updates it. Every download is checked against a list signed with Monk's release key.
    • Sets up each agent it finds: the Monk plugin in Claude Code, Codex, Devin and Antigravity; a monk server entry in the others. Config files are backed up first.
    • Run it again to update. Add --dry-run to see the plan without changing anything.
    More about the installer

    Then, in your coding agent.

    Read the getting started guide

    1. Sign in

      The installer offers to sign you in at the end. Otherwise your agent opens a browser sign-in the first time it uses Monk.

      Create account or sign in

    2. Ask for a plan

      Open the app’s repository in your agent and paste this. It works for a new app and for one that’s already running.

      Monk reads the repository and shows you the plan and its cost. Nothing is created until you approve it.

    3. Review and approve

      Add cloud credentials in Monk’s local form, not in chat. Review the changes, warnings and estimated cost, then approve and follow the deploy.

      You can decline and ask for changes before anything is created. If a deploy fails, check its status and logs before retrying.

    If setup needs attention.

    Monk does not appear in my agent

    Run the installer again and check the plan it shows. If you set the agent up by hand, follow every step in its tab, restart the agent, then check that the monk MCP server is enabled. The setup docs for each agent cover the details.

    The plugin asks me to authenticate again

    Website sign-in and the plugin’s MCP authorization are separate steps. Complete the browser sign-in opened by your coding agent. Do not paste tokens or cloud credentials into the conversation.

    My stack or provider is not supported

    Ask for the unsupported dependencies and the proposed alternatives before approving a deployment. Contact support@monk.io with the component names and error message, leaving secrets out.

    A credential or approval is missing

    Return to the local Monk approval or credential form linked by the agent. Supply the requested information there, or decline and revise the plan. Review the status before starting another deployment.