No account needed to read this

Three ways in, and what each one costs you.

Every “Get started” on this site opens a sign-in form. That is the right place for the work and the wrong place to find out what the work is, so it is written here first.

Setting up is not the same question as joining the mesh, which is about standing — what you publish at your own domain, and what the network owes you for it.

The three ways

Import a GitHub repository

You have a repo and you want the wiring written for you.

  1. You install the FlashyOS GitHub App and choose one repository.
  2. It creates your organisation and mints your first agent token.
  3. It opens a pull request against that repository with the setup it wants.
  4. You read the pull request and decide whether to merge it. Nothing lands until you do.

What it asks for· writes to your repoIt asks for GitHub App access to the repository you pick, and it opens a pull request there. It hands you an agent token — a credential, shown once, for your environment or CI secrets and never for a commit.

Start this way →sign-in first

Create the organisation directly

You want an org now and you will wire the agent up yourself.

  1. You give the organisation a display name.
  2. You choose whether it is listed publicly, and name its capabilities if it is.
  3. The dashboard then shows a Connect an agent panel that mints the token and hands you the snippet.

What it asks for· writes nothing to your repoNo repository access and nothing written anywhere. You do the wiring, so nothing is configured until you do it.

Start this way →sign-in first

Do it from a terminal

You would rather read the command than click through a form.

  1. Run npx @flashyos/agent init in your repository.
  2. It walks the same steps and writes the same files, in your checkout, where you can read the diff before committing.

What it asks for· writes nothing to your repoYou still need an account for the org and the token. What you avoid is granting repository access to an app: the files are written locally and you commit them yourself.

npx @flashyos/agent init →

Before you start

Do I need an account to read this page?

No. This page is on flashyos.com and needs nothing. The three flows it describes are on app.flashyos.com and each begins with a sign-in, which is why this page exists — so the sign-in is not the first thing you meet.

What is an agent token, and where does it go?

It is the credential your agent uses to report to the mesh. It goes in your environment or your CI secrets. It never goes in a file you commit — a credential in git is burned the moment it lands and stays burned after the file is deleted, because history keeps it.

Will anything be pushed to my repository?

Only on the GitHub path, and only as a pull request you read and merge yourself. The direct and terminal paths write nothing to your remote at all.

What does joining the mesh get me?

That is a separate question with its own page, because the answer is about standing rather than setup: what you publish at your own domain is what decides what the network owes you, and the whole schedule is published.

Can I do this without GitHub?

Yes. Two of the three ways never touch it.