Codebox Go

How you get access

1. Register below Your email address, the handle you want, and one line about what you'll use it for. You'll get a 6-digit code by email to confirm the address is yours.
2. Jörn approves you Nothing is automatic. Your request goes to him, and he decides. You'll hear back by email either way.
3. Finish setting up Once approved you get one more code. Enter it, choose your own password, and the account is yours.
4. Sign in whenever you need to Your password plus a fresh code each time. The code is how we keep the door shut if a password ever leaks.

Connecting your tools

Once you're in, create a personal access token in Gitea (Settings → Applications). That token — not your password — is what your tools use.

Git and VS Code

Start with start-here — our welcome repository. Cloning it proves your account, your token and your network path all work, before you touch anything that matters. It is also the handbook: how to set yourself up, how we work, and exactly what happens to your data here.

git clone https://git.hoppe.mywire.org/Longboard-Connection/start-here.git
# username: your handle
# password: your personal access token

Then clone anything else the same way. VS Code's built-in Git support needs nothing special; when it asks for a password, give it the token.

Claude Desktop

Gitea publishes its own MCP server, gitea-mcp. Run it locally on your own machine with your own token and point it at Codebox Go — nothing needs to be granted from our side, and your token never leaves your computer.

The REST API

The full Gitea API is available to you with the same token. Issues, pull requests, releases — all of it.

How this is kept safe

Worth being straight with you about, since you're trusting us with an account:

• Registration is closed. Nobody gets in without Jörn approving them by name.
• Your one-time codes are never stored — only a hash of them. They expire, they work once, and they stop accepting guesses after five wrong tries.
• Emailed links never carry a secret. The code is always something you type in yourself.
• Your account is yours alone. It is not a Hoppe.home domain account, and it gives no access to anything else in the house — not the Portal, not the family systems. Only the repositories you've been added to.
• Repository administration — creating repos, changing org settings, or merging into a protected main branch without review — is held by a short, named list: Jörn, Joanna (the house AI), and claude-code (an interactive Claude Code coding session, given that access 2026-09-03 for repo administration specifically). Every other contributor to a shared repo — AI or human, including other AI coding tools we use — works the same way you will: through a pull request that Jörn or Joanna reviews before it merges. Nobody, including us, pushes straight to your work.
• We keep your email address, your handle, and what you told us you'd use it for. Nothing else.

Sign-in activity is monitored for unusual patterns, and this service will sit behind the Hoppe.home Security Suite as that gets built.