Hoppe.home · Codebox Go

Codebox Go

Hoppe.home's own Git forge. If Jörn has invited you to work on something together, this is where the code lives — and this page is where you get an account.

Closed by invitation — every account is approved by Jörn personally

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.
Sign in
Register

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

Clone normally. VS Code's built-in Git support needs nothing special; when it asks for a password, give it the token.

git clone https://git.hoppe.home/<org>/<repo>.git
# username: your handle
# password: your personal access 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:

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

Hoppe.home · Codebox Go
Questions, or something looks wrong? Ask Jörn directly.
Joanna never asks for your one-time code by any other channel.