How do I…?

Every recipe is a question a real user has, a tldr, and a shipped feature behind it, grouped by where you are: setting up the box, using it daily, building your toolkit, or getting out of trouble.

Configuring the box

• Save my LLM credentials so I don’t need to re-auth for each box?
• Enable a skill in this box?
• Add an MCP server to my agent’s session?
• Add a package to this box – and promote it to my template?
• Set my defaults so every new box starts right?
• Switch agents for one project?
• Expose a port to see the box’s dev server?
• Pass env vars into the box?
• Use my API key instead of an agent login?
• Use Podman instead of Docker?
• Mount other folders from the host?
• Bring my dotfiles and shell setup into every box?
• Give my agent standing instructions in every box?
• Stop re-downloading dependencies on every rebuild?
• Run project setup automatically?
• Cap the box’s CPU or RAM?
• Restrict network access?
• Run other Docker containers from inside the byre environment?
• Get the coding agent to edit its own byre config?

Daily workflow

• Run parallel agents on the same repo?
• Set up two agents in a review loop?
• Get a second shell in the box?
• Resume my session after a config change?
• Paste or drag-and-drop images and files into my agent?
• Use byre on a remote machine over SSH?
• Get tab completion for byre commands?

Skills & templates

• Write my own skill?
• Make a template for a stack byre doesn’t ship?
• Share a skill or template with someone else?
• Share one config baseline across many projects?
• Ship a recommended box config with my project?
• Version-control my ~/.byre?

Lifecycle & recovery

• Start over – and which hammer do I reach for?
• Move or rename a project directory?
• Pull fresh tool versions?
• Stop using byre?
• Uninstall byre completely?
• Report a bug?
• …do something not listed here?

User documentation

• Configuring the box -- shared logins, MCP, ports, env, dotfiles, the firewall, resource caps
• Daily workflow -- parallel agents, review loops, delivering files, remote SSH, completions
• Skills & templates -- writing and sharing skills, templates, layers, presets
• Lifecycle & recovery -- reset vs forget vs rebuild, moving projects, leaving, reporting bugs

Reference