Install Rovara — Rovara Code

Choose your installation path#

Launch in AWS is the recommended path in the Rovara README. It opens a setup page and needs nothing installed on your computer. The terminal path uses the published npm CLI.

Both paths set up GitHub, Slack and your first project. AWS and model usage are billed to you.

Region: us-east-1

The current installation guide supports US East (N. Virginia). The buttons and explicit-region examples here use that region.

Before you start#

An AWS account, ideally dedicated to Rovara, and permission to create IAM roles for installation.
A GitHub organization or personal account to own the GitHub App.
A Slack workspace where you can create and install apps. Your workspace may require admin approval.
Model access: Amazon Bedrock, or an OpenRouter, Anthropic or OpenAI API key.
An email address for setup and alerts.
Terminal path only: Node.js 22.19 or newer; Node 22 LTS is recommended, with an authenticated AWS admin profile.

The installer checks regional capacity, including EC2 vCPUs and two free Elastic IPs. Full prerequisite and quota details →

1. Launch in AWS#

Launch in AWS ↗

On the AWS Create stack page, enter your email, GitHub owner and install name. Review the IAM acknowledgement and create the installer stack.
Look for the temporary-password email (the README estimates about five minutes). The installer stack’s SetupPageUrl output has the same setup-page address.
Sign in, choose a new password and follow the build progress. The installation guide estimates about 20 minutes for the AWS build.
Connect the GitHub App and Slack app on the page, then choose your first repository and Slack channel.
Confirm alerts and mention the bot. The setup ends at its first Slack reply.

After Rovara answers in Slack, you can delete only the agentx-installer stack to remove the installer; Rovara’s environment keeps running. Removing the environment itself is a separate action.

Detailed AWS setup instructions →

2. Install from a terminal#

Check node --version, then use an AWS admin profile authenticated for the target account. Replace both placeholders:

export AWS_PROFILE=<an admin profile for the target account>
npx @preplabsai/rovara-code init --env <name>

This is the command from the README. For an explicit region:

npx @preplabsai/rovara-code --env <name> init --region us-east-1

Use a lower-case install name with letters, digits and hyphens, such as prod or staging. Keep the terminal open and your computer awake until setup finishes.

On your own computer, the installer opens a browser page served only from 127.0.0.1. It shows your choices, the resource plan and estimated cost before creating the environment, then guides GitHub, Slack and project setup.

To stay in the terminal:

npx @preplabsai/rovara-code --env <name> init --region us-east-1 --no-ui

CloudShell and SSH normally use the terminal. CloudShell needs Node 22 first; use the checksum-verified setup instructions in Node 22 in AWS CloudShell. Other installation paths →

3. Give it a first task#

In the project channel, select the installed bot through Slack’s mention picker. Its default name still uses AgentX.

@AgentX Add CSV export to the orders page. Export only selected dates and our company’s orders; viewers must be blocked.

A plain mention is routed first: a question is answered, while a change gets a card suggesting Quick or Full. The requester presses Start, then reviews the proposed plan before code changes. Use chat: to ask the chat agent directly. Inspect the changes and check evidence before merging. Your team decides what gets merged. Follow the Quick tutorial →

Upgrading an existing install?

To save thread replies that do not mention AgentX, the Slack app needs the channels:history and groups:history scopes and the message.channels and message.groups events. Update the app from the manifest agentx init generates, then reinstall it to the workspace.

Prefer an IDE? Connect Claude Code, Codex or Cursor →

Resume or diagnose setup#

If setup stops, run the same init command again. The installer resumes at the first unfinished step. If Slack needs an admin to approve the app, wait for approval and rerun it.

After installation, use operator access to check the environment:

npx @preplabsai/rovara-code --env <name> doctor --region us-east-1

Read the failures and next actions before changing anything. Browser, SSH and recovery details →

Upgrade or remove an environment#

Use the target release’s CLI version for an upgrade; review the changes before accepting:

npx @preplabsai/rovara-code@<version> --env <name> upgrade --region us-east-1

Operations, projects, connectors and upgrades →

Removal deletes the environment’s workspaces, stacks and stored data. It needs admin credentials and explicit environment confirmation. Save anything you need first and read the full teardown guide:

npx @preplabsai/rovara-code --env <name> destroy --region us-east-1

Rovara name, compatible commands#

The product repository is PrepLabsAI/Rovara. The published package is @preplabsai/rovara-code. You can install the CLI once:

npm install -g @preplabsai/rovara-code
rovara --help

The package also provides agentx as a compatibility command. AWS resources, ~/.agentx, MCP server/tool IDs and the default Slack app retain their existing names. Use the examples as written.

Installation commands checked against the README and linked guides on 13 October 2026. Release, licence and documentation status →