Load a repository

Point it at a repository and it reads the whole thing: every file placed by the job it does rather than the folder it sits in. What you get back is a galaxy: the code, its credentials, its analysis and its open work, held together as one thing you can switch to.

Watch instead: Galaxy · 37 sec

The fastest way to see it work

On the first screen, take the Just show me door. It reads React, a public repository, nothing of yours involved, and a codebase you probably already have opinions about.

6,829 components, analysed in 5.8 seconds. The clone before it is shallow, so it pulls 72 MB of files rather than a gigabyte of history: 5.3 seconds.

Your own

Galaxy Manager → add, or paste a URL on the first screen. You need a GitHub token for anything private. See Keys.

Two real ones, timed on an ordinary laptop:

Cicero INFRA      1.5s      74 files
Cicero Agent     30.1s     545 files

That is the whole of getting a codebase in. There is no indexing step to wait out and no upload.

Switching between them

A galaxy is a setting inside StellarView, not a folder on your disk. The switcher at the top of the screen changes which one you are working in. The epics, the issues, the credentials and the analysis all follow. Nothing moves, and you can hold as many as you like.

Worth knowing

Clones are full by default, and that is deliberate. History is needed for branch and pull request work. The demo galaxy asks for a shallow clone because it is there to be looked at, not worked in. A shallow clone that quietly could not open a PR would be a silent failure, so it is opt-in rather than assumed.

A galaxy can carry its own credentials. A repository in another organisation gets its own token in its own .env, so you are not swapping keys by hand.

Analysis is re-runnable. Re-read a repository after a big merge and the layers and counts update. Nothing is frozen at import.

Private repositories need the token first. Adding one before the key is set fails with the GitHub error, in full, rather than a generic message.

---

Next: Create an epic. Give it a document, get a build order.