Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runaegis.co/llms.txt

Use this file to discover all available pages before exploring further.

A room in Aegis is a collaborative workspace tied to a single GitHub repository. It groups together the team members who work with that repository, defines what each role is allowed to do via MCP, and produces the integration URL that connects your AI agent to Aegis governance for that repo. Every repository you want to govern with Aegis gets its own room.

​
When to create a room

Create one room per GitHub repository you want to govern. If your organization uses three repositories, say, a backend service, a frontend application, and an infrastructure monorepo, you would create three rooms. Each room has its own member list, role assignments, tool permissions, and integration URL. If you are joining an existing team’s room, you do not create one yourself; instead you enter an invite code provided by an OWNER or ADMIN.

​
Roles

Rooms have three roles with a strict hierarchy:
RoleLevelCan create invitesCan edit lower roles’ tool permissions
OWNERHighestYesYes (ADMIN and DEVELOPER)
ADMINMiddleYesYes (DEVELOPER only)
DEVELOPERLowestNoNo
The user who creates a room is automatically assigned the OWNER role. OWNERs and ADMINs can invite new members; DEVELOPERs cannot generate invite links. When viewing tool permissions, you can only edit settings for roles at or below your own level.

​
Creating a room

1

Open the Rooms page

Navigate to Dashboard → Rooms.
2

Enter a repository name

In the Create room card, type the repository name (for example, my-org/backend) into the Repository Name field.
3

Create the room

Click Create room. Aegis creates the room, assigns you the OWNER role, and selects the new room automatically in the sidebar. Your integration URL is generated at this point.

​
Joining a room

1

Obtain an invite code

Ask an OWNER or ADMIN of the room to generate an invite link and share the invite code with you.
2

Open the Rooms page

Navigate to Dashboard → Rooms.
3

Enter the invite code

In the Join room card, paste the invite code into the Invite code field and click Join room. The room appears in your room list with the role assigned by the invite.
OWNERs and ADMINs can generate invite codes from within a room’s detail view.
1

Select your room

Click the room in the left sidebar to open its detail view.
2

Set invite options (optional)

In the Generate invite form, you can optionally specify:
  • Max uses, the maximum number of times the invite code can be used before it expires
  • Expires at, a date and time after which the invite code is no longer valid Leave both fields empty to create an invite with unlimited uses and no expiry.
3

Generate the invite

Click Generate invite. The invite code appears in the Invites panel on the right. Click Copy next to the code to copy it to your clipboard and share it with teammates.
Only OWNER and ADMIN roles can see and use the Generate invite form. DEVELOPERs see a read-only notice instead.

​
Tool permissions

Each room has a tool permissions matrix that controls which GitHub MCP tools each role is allowed or denied. Permissions are set per-role and apply to every agent connecting to that room with that role.

​
Tool groups

MCP tools are organized into four groups:
GroupTools
Repositorycreate_or_update_file, get_file_contents, list_repository_files, push_files, search_repositories, get_repository
Issues & PRcreate_issue, get_issue, issue_read:get_comments, issue_read:get_sub_issues, list_issues, create_pull_request, get_pull_request, pull_request_read:get_comments, pull_request_read:get_review_comments, pull_request_read:get_reviews
Searchsearch_code, search_issues
Gitget_latest_commit, list_branches, create_branch

​
Setting tool permissions

1

Select the role to configure

In the Tool policies card, use the View role dropdown to select the role you want to configure. You can only configure roles at or below your own level.
2

Allow or deny each tool

For each tool in every group, click Allow to permit that tool for the selected role, or Deny to block it. Changes are saved to the backend immediately, there is no separate save step for tool permissions.
Tool permissions are enforced in addition to Aegis policies. A tool call that passes tool-permission checks may still be blocked or transformed by a policy. Both layers apply.

​
Integration URL

Every room has an integration URL, an SSE endpoint that your AI agent connects to in order to route its MCP tool calls through Aegis governance for that room. The URL has this structure: 
https://app.runaegis.co/sse?user_id=<user_id>&room_id=<room_id>&access_token=<access_token>&role=<role>
ParameterDescription
user_idYour Aegis user ID
room_idThe unique identifier of this room
access_tokenYour personal access token for authenticating requests
roleThe role the agent will act as in this room
To copy your integration URL:
1

Select your room

Click the room in the sidebar.
2

Copy the URL

In the room’s detail card, click Copy next to the Integration URL field. Configure your agent to use this URL as its MCP server endpoint.
Each room member’s integration URL is unique to them. Do not share your integration URL, share invite codes instead so teammates can generate their own URLs.