Skip to content

Documentation

Project settings

Give a project its environment values, its instructions and its links to your other projects.

Updated October 13, 2026

1

Open the settings of a project

Open the project and select Settings. The settings have these parts: General, Agent defaults, AGENTS.md, Skills, Preview, Releases, and More settings.

General has the display name, the address of the Git repository and the Default Branch. Sessions start from the default branch, and pull requests go into it.

2

Give environment variables

Most apps need values to start: a database address, an API key for a test account, a secret for cookies. Open More settings → Connections & environment → Environment Variables.

During setup, Rondar reads .env.example, .env.sample or .env.template from the repository and lists the variables that it finds. A badge shows how many variables have no value. You can also add a variable by its name.

  • Values are encrypted when they are stored.
  • Restart a session after a change, so that the session gets the new values.
  • Use values for development and test accounts. Do not give production credentials to a session or to a preview.

Agent environment is a separate list of KEY=VALUE lines that each new agent invocation gets.

3

Give project instructions

AGENTS.md holds the instructions that each agent gets when it works on this project: how to run the tests, the style of the code, the files that it must not change. Rondar adds them after your account instructions and the instructions of the mode.

Agent instructions describes the levels of instructions.

4

Add skills

A skill is a set of instructions and files for one kind of task. Under Skills, select Add project skill to import a skill from skills.sh or from GitHub, or to upload a ZIP archive. Agents that work on the project can then use it.

5

Set the model for the project

Agent defaults sets the agent and the model for Regular mode and for Plan mode in this project. Without a project value, the project uses the defaults of your account. A session that exists keeps its model.

6

Connect projects

Some work needs two repositories, for example an API and its mobile app. Under More settings → Connections & environment → Connected Projects, choose a second project and select Connect Project.

The agents of each project can then read the committed source of the other project. The access has these limits:

  • It is read-only. An agent cannot change or run the code of a connected project.
  • It is direct. If A is connected to B and B to C, A cannot read C.
  • It is for committed files. Files that are not in Git, and files with credentials or environment values, stay out.

Select Disconnect to end the access.

7

Set tenant routing for previews

An app that serves each customer on its own subdomain needs to know which customer a preview shows. Under Preview, turn on Tenant routing and give the Default Tenant. The preview of a session then sends that tenant as the host of each request.

8

Set notifications and archiving

General also has the Session notifications of the project, which can differ from the setting of your account, and the option Auto-archive sessions after their release is completed.

Request an invite →

Reconnecting… Buttons are off until this page is connected again. Reload