Skip to main content
A project groups your code, hardware context, and agent runs. Use one project per firmware codebase.
Where: Platform at hideout.rootaccess.ai/ → home page → New project.

​
Create the project

Three steps in the wizard:
1

Name it

Pick a name. You can rename later.
Name step of the new project wizard
2

Connect a repo

Connect a GitHub or GitLab repo.
Repo connect step of the new project wizard
3

Pick a next move

Bring in project requirements, link Jira or Linear projects, or directly talk to Seb about what you want to build.
Next-move step of the new project wizard
To mention Jira or Linear tickets in your messages when launching agents:
  1. Profile → Integrations → Connect Jira or Connect Linear.
  2. Project Settings → Integrations → link a project (Jira) or team (Linear) to this Hideout project.
Once linked, typing an identifier like KAN-42 or ROO-1163 in the New Agent chat pulls the ticket’s title and description in as context. See the Jira and Linear pages for the connection and linking steps.

​
Target a compliance standard (optional)

If your project is held to a formal compliance standard — DO-178C, ISO 26262, IEC 62304 — pick the standards on the Context page and set the traceability policy in Project Settings. Gap analysis uses them to score your codebase.

​
Settings, members, danger zone

Project Settings (/project-settings) covers rename, traceability policy per requirement level, member invites (owner / admin / member), per-project integration links, and project deletion.

​
Next

Guide → 2. Add hardware & context.