Using konnos

Repositories

A repository is a home for one project's code and its history. Here's how to create one, look around inside it, and remove it safely.

Create a repository

  1. 1

    Open the dashboard

    Go to your dashboard and click New repository.

  2. 2

    Name it and choose visibility

    Give it a short name (letters, numbers, dashes). It's private by default — leave it that way unless you deliberately want it public.

  3. 3

    Create

    konnos seeds a README so the repo is browsable straight away instead of empty. You land on the repo with its clone URL ready to copy — head to Getting started to push your code into it.

Prefer to do it from code?

An agent or script can create a repository too — see the MCP phone line (konnos_create_repo) and the REST API.

Browse files and commits

Open any repository to look around without cloning it:

  • Files— click through folders and open a file to read it in the browser, on the repo's default branch.
  • Commits — the Commitstab lists the history newest-first, with each commit's message, author, and time.

A freshly created repo with nothing pushed yet shows an empty state with its clone URL, so you always know what to do next.

Delete a repository

Deleting a repository is permanent — it removes the code and its whole history. Because of that, konnos guards the action so it can never happen by accident.

  • In the dashboard— the delete control lives in the repository's Settings, in a clearly marked danger zone, and asks you to confirm before it acts.
  • From the MCP — the delete_repo tool is gated: you must pass a confirm value equal to the exact owner/repo string, or it refuses and deletes nothing.

There's no undo

Once a repository is deleted, konnos can't bring it back. If you just want to hide it, keep it private instead.