Skip to content

Code

Browser-based VS Code editor wired to an AI coding agent for the homelab repo · https://code.fmm.house

What it's for

Code is a full VS Code editor that runs in your browser (code-server style), so you can work on the homelab repo from any device without installing anything. It has the usual editor, file explorer, and an integrated terminal, plus an AI coding agent you can hand tasks to. It's a developer tool — handy for quick edits, config tweaks, and larger changes alike, from anywhere on the LAN or Tailscale.

Getting in

  • Open: https://code.fmm.house — on the home Wi-Fi/LAN, or from anywhere with Tailscale connected.
  • Sign in: Enter the editor password when prompted. This is an operator/admin tool; the workspace opens straight onto the homelab repo.

How to use it

Edit and save files

  • Use the Explorer (left sidebar, or Ctrl/Cmd+B to toggle) to open files.
  • Ctrl/Cmd+P is the quick file-open; Ctrl/Cmd+Shift+P opens the command palette for everything else.
  • Save with Ctrl/Cmd+S. Changes write directly to the repo on the host, so commit them when you're happy.

Use the integrated terminal

  • Open it with Ctrl+` (or Terminal → New Terminal). It's a real shell on the host, in the repo directory.
  • Run git, docker, deploy scripts, and anything else you'd normally run over SSH — right inside the browser.
  • You can split terminals and keep several open for long-running commands.

Work with the AI coding agent

  • Open the agent's panel/sidebar and describe the change you want in plain language (e.g. "add a healthcheck to the X stack").
  • Review what it proposes before accepting — read the diffs, then apply or reject.
  • Keep tasks scoped and specific; smaller, well-described requests get better results than one giant instruction.

Commit your work

  • Use the Source Control view (Ctrl/Cmd+Shift+G) or the terminal to stage, commit, and push.
  • Pushing goes to Forgejo at git.fmm.house like any other git remote.

Tips

Tip

Changes here touch the live homelab repo. Commit in small, reviewable chunks and push often so nothing is lost if the browser tab closes.

  • The editor state persists on the server, so open files and terminals are usually still there when you come back.
  • Always read the coding agent's diffs before accepting — treat its output as a draft to review, not a finished commit.