v0.4.0 Remove Cruft (#11)

* cp dines

* cp dines

* cp dines

* 0.4.0

* 0.5.0

* cp dines

Author: dines-rl

CLAUDE_SETUP.md

@@ -5,7 +5,7 @@ This guide will walk you through connecting the Runloop MCP server to Claude Des
 ## Prerequisites
 
 1. Make sure you have Claude Desktop installed
-2. Authenticate with Runloop: `rli auth`
+2. Set your API key: `export RUNLOOP_API_KEY=your_api_key_here`
 3. Make sure `rli` is installed globally and in your PATH
 
 ## Quick Setup (Automatic)
@@ -108,7 +108,7 @@ If not found:
 
 ### "API key not configured"
 
-Run `rli auth` to configure your API key before using the MCP server.
+Set the `RUNLOOP_API_KEY` environment variable before using the MCP server.
 
 ### Claude doesn't show Runloop tools
 

MCP_COMMANDS.md

@@ -148,7 +148,7 @@ If you get "command not found: rli":
 
 ### API key not configured
 
-Run `rli auth` before using the MCP server.
+Set the `RUNLOOP_API_KEY` environment variable before using the MCP server.
 
 ### Port already in use
 

MCP_README.md

@@ -131,14 +131,12 @@ Example for Claude Code or other MCP clients supporting HTTP:
 
 ## Authentication
 
-The MCP server uses the same API key configuration as the CLI. Make sure you've authenticated first:
+The MCP server uses the same API key configuration as the CLI. Set your API key:
 
 ```bash
-rli auth
+export RUNLOOP_API_KEY=your_api_key_here
 ```
 
-The server will automatically use your stored API credentials.
-
 ## Example Usage with Claude
 
 Once configured, you can ask Claude to perform Runloop operations:
@@ -162,7 +160,7 @@ Claude will use the MCP tools to interact with your Runloop account and provide
 
 If the stdio MCP server isn't working:
 
-1. Make sure you've run `rli auth` to configure your API key
+1. Make sure `RUNLOOP_API_KEY` environment variable is set
 2. Check that the `rli` command is in your PATH
 3. Restart Claude Desktop after updating the configuration
 4. Check Claude's logs for any error messages
@@ -171,15 +169,15 @@ If the stdio MCP server isn't working:
 
 If the HTTP MCP server isn't working:
 
-1. Make sure you've run `rli auth` to configure your API key
+1. Make sure `RUNLOOP_API_KEY` environment variable is set
 2. Check that the port isn't already in use
 3. Verify the server is running: `curl http://localhost:3000/sse`
 4. Check your firewall settings if connecting remotely
 5. Look at the server logs for error messages
 
 ### Common Issues
 
-- **"API key not configured"**: Run `rli auth` to set up your credentials
+- **"API key not configured"**: Set `RUNLOOP_API_KEY` environment variable
 - **Port already in use**: Stop other services or use a different port with `--port`
 - **Connection refused**: Make sure the server is running and accessible
 

OUTPUT_FORMAT_SUMMARY.md

@@ -6,7 +6,6 @@ A beautiful, interactive CLI for managing Runloop devboxes built with Ink and Ty
 
 - 🎨 Beautiful terminal UI with colors and gradients
 - ⚡ Fast and responsive with pagination
-- 🔐 Secure API key management
 - 📦 Manage devboxes, snapshots, and blueprints
 - 🚀 Execute commands in devboxes
 - 📤 Upload files to devboxes
@@ -33,90 +32,31 @@ npm link
 
 ## Setup
 
-Configure your API key using either method:
-
-### Option 1: Environment Variable (Recommended for CI/CD)
+Configure your API key:
 
 ```bash
 export RUNLOOP_API_KEY=your_api_key_here
 ```
 
-### Option 2: Interactive Setup
-
-```bash
-rli auth
-```
-
 Get your API key from [https://runloop.ai/settings](https://runloop.ai/settings)
 
 ## Usage
 
-### Authentication
-
-```bash
-# Interactive setup (stores API key locally)
-rli auth
-
-# Or use environment variable
-export RUNLOOP_API_KEY=your_api_key_here
-```
-
-The CLI will automatically use `RUNLOOP_API_KEY` if set, otherwise it will use the stored configuration.
-
 ### Theme Configuration
 
-The CLI supports both light and dark terminal themes with automatic detection:
+The CLI supports both light and dark terminal themes. Set the theme via environment variable:
 
 ```bash
-# Interactive theme selector with live preview
-rli config theme
-
-# Or set theme directly
-rli config theme auto    # Auto-detect terminal background (default)
-rli config theme light   # Force light mode (dark text on light background)
-rli config theme dark    # Force dark mode (light text on dark background)
-
-# Or use environment variable
-export RUNLOOP_THEME=light
+export RUNLOOP_THEME=light   # Force light mode (dark text on light background)
+export RUNLOOP_THEME=dark    # Force dark mode (light text on dark background)
 ```
 
-**Interactive Mode:**
-
-- When you run `rli config theme` without arguments, you get an interactive selector
-- Use arrow keys to navigate between auto/light/dark options
-- See live preview of colors as you navigate
-- Press Enter to save, Esc to cancel
-
 **How it works:**
 
-- **auto** (default): Uses dark mode by default (theme detection is disabled to prevent terminal flashing)
+- **auto** (default): Detects correct theme by default
 - **light**: Optimized for light-themed terminals (uses dark text colors)
 - **dark**: Optimized for dark-themed terminals (uses light text colors)
 
-**Terminal Compatibility:**
-
-- Works with all modern terminals (iTerm2, Terminal.app, VS Code integrated terminal, tmux)
-- The CLI defaults to dark mode for the best experience
-- You can manually set light or dark mode based on your terminal theme
-
-**Note on Auto-Detection:**
-
-- Auto theme detection is **disabled by default** to prevent screen flashing
-- To enable it, set `RUNLOOP_ENABLE_THEME_DETECTION=1`
-- If you use a light terminal, we recommend setting: `rli config theme light`
-- The result is cached, so subsequent runs are instant (no flashing!)
-- If you change your terminal theme, you can re-detect by running:
-
-  ```bash
-  rli config theme auto
-  ```
-- To manually set your theme without detection:
-  ```bash
-  export RUNLOOP_THEME=dark  # or light
-  # Or disable auto-detection entirely:
-  export RUNLOOP_DISABLE_THEME_DETECTION=1
-  ```
-
 ### Devbox Commands
 
 ```bash