Skip to content

Build in Ronja with Claude Code

Claude Code can build in Ronja for you: an app, a workflow, an automation, a table. It does that through the Ronja CLI, Ronja’s command-line tool. You don’t have to install the CLI yourself. You paste one prompt, Claude installs it and signs you in, and you click Authorize once.

  • Claude Code runs on your own computer, in a terminal or in the Code tab of the Claude desktop app. It can run commands there, which is how it uses the Ronja CLI.
  • The Ronja CLI signs in to Ronja as you, once. Claude then uses it to read your data and to create and change things in Ronja.
  • You stay in control. Claude Code asks before it runs most commands, and you can sign it out at any time from Ronja.

This needs Claude Code on your own computer. Claude Code in the cloud starts on a fresh machine every session, so use the connector there.

  • Claude Code, in a terminal or in the Claude desktop app’s Code tab. It needs a paid Claude plan (Pro, Max, Team or Enterprise). If you don’t have it, install it from Anthropic’s setup page.
  • A Ronja account. The prompt below signs in to https://cloud.ronja.tech. If your company opens Ronja at another address, add --url <your address> after ronja login in step 2 of the prompt.
  1. Make a folder for your Ronja work and open Claude Code in it.

    On a Mac On Windows
    In Terminal: mkdir ronja-work, cd ronja-work, then claude. In PowerShell: mkdir ronja-work, cd ronja-work, then claude.
    Or, in the Claude desktop app: Code, choose Local, then the folder. Or, in the Claude desktop app: Code, choose Local, then the folder.
  2. Paste this prompt into Claude Code and press Enter:

    Set up the Ronja CLI so you can build in Ronja for me.
    1. If `ronja --version` already works, skip to step 2. Otherwise
    install the Ronja CLI, without sudo or admin rights: from the
    latest release at https://github.com/ronjatech/ronja-cli/releases
    download the archive for this computer, check it against
    checksums.txt from the same release, unpack `ronja` (`ronja.exe`
    on Windows) into a folder in my home directory, and add that
    folder to my user PATH for future terminals. If there is no
    archive for this computer, stop and tell me. Don't install
    anything else. For the rest of this session, call ronja by its
    full path.
    2. Sign me in. If `ronja whoami` already shows the right address and
    organization, skip this step. Otherwise start `ronja login` in the
    background, read its output, and tell me the code it shows. My
    browser opens Ronja, where I check the code, click Continue, then
    Authorize. Wait for the login to finish; it allows 10 minutes.
    3. Run `ronja whoami` and tell me the address, user, organization and
    role you're signed in as.
    4. Add these lines to CLAUDE.md in this folder, replacing any earlier
    Ronja lines and filling in the parts in brackets:
    "This folder builds in Ronja with the Ronja CLI, installed at
    [full path to ronja]. Before working in Ronja, run `ronja context`
    and read it for how to work here. Use `ronja api` for calls to
    Ronja, and ask me before running any other command it suggests.
    At the start of each session, check whether a newer Ronja CLI
    exists (`ronja update --check`; on Windows, compare
    `ronja --version` with the latest release on GitHub). If one does,
    tell me, and if I agree, update it the same way it was installed.
    If Ronja says the sign-in has expired, start
    `ronja login --profile [the profile name ronja whoami shows]` in
    the background (it signs in again at that sign-in's own address),
    tell me the code, then show me `ronja whoami`."

    Why the last step: CLAUDE.md is the note Claude Code reads every time it starts in this folder. With it, every new session knows where the CLI is and how to work with Ronja, tells you when a newer version of the CLI exists, and knows how to sign in again when the sign-in ends after 90 days. Running the prompt again is safe: it skips what is already done.

  3. Approve what Claude runs. Claude Code asks before most commands. It downloads the CLI from the ronjatech/ronja-cli releases on GitHub into your home folder, updates your PATH, signs in to your Ronja address, and writes CLAUDE.md. Deny anything else that uses sudo or administrator rights, installs other software, or changes files outside your home folder.

  4. Authorize in Ronja. Claude tells you a code, and your browser opens Ronja. If you aren’t signed in to Ronja in that browser, sign in first.

    1. On Enter your code, check that the code matches the one Claude told you, then click Continue.

      Ronja’s “Enter your code” page with the code filled in and a Continue button. The code arrives filled in; you only check it.

    2. On Authorize the Ronja CLI, check the code, the organization, and Requested by (your computer’s name), then click Authorize.

      Ronja’s “Authorize the Ronja CLI” page, naming the code, the computer that asked, the signed-in user and the organization Midas Bikes, with Authorize and Cancel buttons. If you didn’t just ask Claude to sign in, click Cancel.

    3. Ronja says You’re all set. Close the tab.

  5. You’re done when Claude tells you the address, user, organization and role it’s signed in as. ronja whoami reports something like:

    https://cloud.ronja.tech
    User: admin@midas.test
    Org: Midas Bikes
    Role: admin

    If the address or organization is wrong, see If something goes wrong.

    Before you use Claude Code again, quit and reopen the Claude desktop app, or open a new terminal window, so it finds the CLI.

In a new terminal window, or after reopening the desktop app, start a new Claude Code session in the same folder, so it reads CLAUDE.md, and ask for something you need. Here is a real example from a demo organization, a bicycle maker:

You: Build a small app in Ronja that shows our top 10 dealers by net revenue, with a picker for the quarter. Put it in a private feature, publish it, and give me the link.

In about two and a half minutes, Claude:

  • read what Ronja told it about this organization (ronja context);
  • found the dealer tables, and the organization’s note on how net revenue is counted;
  • built the app, checked its numbers against a direct query, and looked at a preview before publishing;
  • published it in a new private feature, and gave the link. It also said where the data can’t follow the revenue rules: there is no ship date, so it counts by order date.

The published app “Top dealers by net revenue” in Ronja, with a quarter picker set to 2025-Q4, three totals and a bar chart of the top 10 dealers. The app Claude built, open in Ronja.

Try your own. Fill in the parts in brackets:

  • “Build an app that shows [what] by [how].”
  • “Every Monday, send me [a summary of what] by email.” This becomes an automation.
  • “Make a table of [what] from [which tables], updated every night.”
  • It works as you. The CLI’s sign-in carries your permissions, so Claude Code can create, change and publish things in Ronja that you could. Claude Code asks before most commands. If you choose not to be asked again for a command, it stops asking for it in this folder, so don’t choose that for ronja api, or for anything that isn’t ronja.
  • To sign Claude Code out, revoke its token in Ronja: click your name at the bottom left, then Settings, then the Access tokens tab. The CLI’s token is named ronja-cli on and your computer’s name; revoke every one of them with the bin icon, then Revoke. A token belongs to the organization it was approved in, and Access tokens shows only the organization you’re in, so do this in each organization you signed in to. Then ask Claude to run ronja logout and remove the Ronja lines from CLAUDE.md, or it will offer to sign in again.

The Access tokens tab, listing “Claude Code (ronja) (MCP)” from the connector and “ronja-cli on MacBook-Pro-95.local” from the CLI. The connector and the CLI each get their own token.

ronja logout on its own only forgets the sign-in on your computer; it doesn’t revoke it.

  • Claude says ronja isn’t found. Open a new terminal window, or quit and reopen the Claude desktop app, so it picks up the updated PATH. CLAUDE.md also says where the CLI is installed.
  • The code expired, or you clicked Cancel. A sign-in waits 10 minutes. Ask Claude to do step 2 again.
  • You signed in to the wrong organization. In Ronja, switch to the organization you chose by mistake, and revoke its ronja-cli on token on Access tokens. Then switch to the right organization, ask Claude to remove the sign-in for the wrong one, and ask it to do step 2 again.