Describes Team AI Console 0.4.13 · updated 2026-11-06

4. The home screen

When the app starts you first see, for a few seconds, a small welcome window with the logo, the version and what is loading (the interface and the license check), with a bar and its progress percentage. When everything is ready it closes by itself and the home screen appears; if the license does not respond (for example, offline), the home screen opens anyway after a few seconds. New Window does not show it.

The home screen is the window you see next. It always opens at the same size, fitted to the Projects page, and it does not remember a size you give it. When you open a project the window is maximized; when you return to the home screen or close the project, it goes back to that size and is centered.

On the left there is a bar with:

Projects — your projects and the available teams (default view).
Teams and Roles — on a single screen with two tabs, your own teams and the app’s teams (AI Teams) and the app’s role catalog (Roles) (see Teams and Roles).
Agents — Claude Code and Codex: whether they are installed, their version and your session.
License — the status of your license. It shows a ! if you have no active license.
Privacy & data — the full privacy text.
At the bottom: the installed version of the app, the license status, the ES | EN language selector and the theme button (system → light → dark).
If there is a new version of the app, a notice appears here (see App updates).

The five sections share the same header, which stays at the top while you scroll: the title, below it a sentence that explains the section and, on the right, the search box (only in Projects and in Teams and Roles) and the section’s buttons, with the main one last. In a narrow window, the header wraps onto several rows.

In Home the page itself does not scroll: the sidebar always stays in place and only the content on the right moves. If the sidebar did not fit in a very short window, it would scroll on its own without moving anything else.

Projects section

The section is a single column that scrolls as a whole.

Header (stays at the top while you scroll)

The Projects title and, below it, “Open a recent project or start a new one with a team.”
Search projects and teams: type to filter both the projects (by name or path) and the team cards (by name, category, tagline or description).
Open ▾ — a menu with the ways to open a project:
- Open project folder… — opens a folder that is already a project (shortcut: ⌘O on macOS, Ctrl+O on Windows/Linux). If the folder does not have a team configuration yet, the app helps you prepare it (see Preparing a folder).
- Join a shared project (git)… — shows, below the header, the form to clone a project that someone else shared in a git repository (see Collaboration). If you had scrolled down, the app scrolls up to the form and puts the cursor in the address field.
- Adopt an existing project… — brings into the app a project with code developed outside it (see Adopting an existing project).
+ New project — a shortcut: it does not create anything by itself. It takes you to the teams, puts the focus on the first card and highlights the “Start with a team” section with a colored outline and the notice “Choose a team and click “New project” on its card”. The highlight shows even if the teams are already in view and goes away by itself after 6 seconds or when you choose a team; if “reduce motion” is on in your system, it appears without animations.

Continue where you left off

Your latest recent projects (up to 4), in a list: one row per project, like a file, with a grey folder icon showing the project’s initial, its name and its path below (cut with “…” if long), the project’s team, when you last opened it (“2 hours ago”, “yesterday”…) and its buttons. The row is highlighted on hover; hovering also shows the full path and when you opened it.
The team is shown as a tag in its category color: the category icon in a light circle, the team name and its version (for example, “Lyra v2.2.0”). Hover over it to see the full text. If the project has no identifiable team (no configuration, or a team that is no longer in your list of teams), that column stays empty. In a narrow window the row stays on one line: “… ago” is hidden and the team tag is shortened.
↗ opens the project in a new window; Open opens it; × opens the Remove project window, with its name and full path: Remove from list removes it from the recent list and leaves the folder on disk; Remove and delete from disk… asks again (Delete the folder from disk?) and, with Move to Trash (Recycle Bin on Windows), moves the whole folder, with its code and documents, to the system trash, where you can restore it, and removes the project from the list. If the project is open in another window or its folder no longer exists, the window says so and only lets you remove it from the list. If moving to the trash fails, you see the reason and nothing is deleted. Cancel, Esc or a click outside the window change nothing.
All N projects → (if you have more than 4) shows all of them on the same screen; Show fewer goes back to the latest 4. While you search, every match is shown.

Start a project with one team

Next to the title, “One team works on the whole project. Each has its own scope.” and, on the right, All teams →, which takes you to Teams and Roles, AI Teams tab (where the category filter is, and where teams are created, edited and imported).
A 💡 Tip box recommends starting with Asteroid (Ceres), the incubator, if your idea is not clear yet; its See its details link opens the Ceres card.
The teams, in a single grid of compact cards (up to 4 per row; 3, 2 or 1 in a narrower window): the app’s teams first and then your teams (the ones you created, imported or copied; here they are only picked to create a project). One of yours with validation errors is dimmed and can’t be picked, with a link to AI Teams. The header’s search box also filters these cards; if nothing matches you see “No team was found. Check the team-templates folder of the app.”. Importing a team does not create or open any project.
One compact card per team, with:
- at the top, a strip in its category color with its icon and its name in capitals (yours, “COMET” or their own category);
- the team name and its version (for example “v1.5.0”; on hover, “Team version: …”), with 🔒 if your license doesn’t include the team. For the app’s teams that declare no version of their own it is the version of their signature (a date, such as “v2026.10.02”); if there is no known version, none is shown;
- its roles’ faces: a circle per role with its initials, in its area’s color (for example blue for Product and green for Implementation; grey if the app doesn’t recognise the area), overlapping, and the number of roles (for example “4 roles”). Hover to see their names;
- a description of what the team is good for (for an imported team without that description, “Imported ·” and its tagline);
- at the bottom, the New project and Details buttons. The border turns blue on hover. Details expands the card to the full width, with a light background and an accent-colored border: the category and the languages the team exists in (for example “Supernova · ES · EN”; this is information, not a selection), the summary followed by what it does not include, the roles as tags in the category color, which part of the lifecycle it covers (Vision, Definition, Build & test, Deploy & operate) and, for imported teams, their version and origin. Less collapses it again.
A team that your license does not allow looks the same, but with 🔒 New project: clicking it opens a dialog explaining which license feature it needs, what that feature does and which licenses include it, with a See the license button.

Teams and Roles

From this sidebar entry you create and manage your own roles and teams: the role catalog, the AI Teams tab and the editors with the agent. It has its own chapter: Teams and Roles: create your own roles and teams (chapter 5).

Agents section

Shows one card per agent (Claude Code and Codex), a summary strip above them and, at the top right, the Check again button:

Check again looks for the agents and checks their sessions again (the same as when Home opens and when you return to the window). Meanwhile it says Checking…; the cards keep what they showed until it finishes.
Summary strip: how many agents are ready (installed and signed in). In green, “2 of 2 agents ready. They use your plan…”; in red, if one still needs installing or signing in, with its name; in amber, if one uses a pay-per-use API (chats consume credits).
Card header: the agent’s name, a pill with its status — Signed in (green), Not signed in or Not installed (red), Paid API (amber) — and the version.
Path to the executable, in a box (cut with “…” if long; hover to see it whole). If it is not found: the notice “The … executable was not found.” and the Choose path button to enter it manually.
Path chosen manually: Manual path appears above the box. If that path no longer exists (the file was deleted or moved), an amber notice “The saved path no longer exists” shows it; if the app finds the agent on its own, it uses it and shows it below as Detected automatically.
Change or remove the path: Change executable opens the file picker and replaces the path (cancel and nothing changes). Remove path, only when there is a manually chosen path, deletes it without asking and the app looks for the agent in the usual locations again; the card, the summary strip and chats use the result right away, without restarting.
Paste executable path: below the path, each card has an always-visible field where you can type or paste the executable’s path and press Use path (or Enter). Leading and trailing spaces and quotes are ignored and ~ is your home folder; the path must be absolute (start with /, ~ or a drive letter such as C:\), exist, be a file and, on macOS and Linux, be executable. If it isn’t, a message appears below the field and nothing is saved; if it is, “Path saved.” appears and the card shows the path and its version without restarting. The field always shows the manually chosen path (empty if there is none), also after Change executable or Remove path.
At the bottom, from left to right: Remove path and Change executable (depending on the case) and the session action: Sign out, or Sign in when not signed in.
Account details, when signed in and the agent reports them:
- Account — the email address.
- Organization — in Claude Code (“—” if there is none).
- Access — in green, “Claude subscription (claude.ai): uses your plan” or “ChatGPT subscription: uses your plan”; in orange, “Pay-as-you-go API (…): every message is billed separately” if the agent uses an API key or a cloud provider.
- Plan — for example Claude Max, Claude Pro, ChatGPT Plus.
- Active until — in Codex, if the account reports a future date.

Signing in from the app:

Claude Code: the browser opens the Anthropic page; you sign in, authorize Claude Code, the page shows a code, you paste it in the dialog and click Continue.
Codex: the browser opens the OpenAI page; you sign in with your ChatGPT account and authorize Codex. The dialog completes on its own when the browser returns control.

License section

See the Licenses chapter.