Settings and Troubleshooting

#Global Settings

Global settings apply to all projects and pipelines.

Setting	Default	Description
CLI Provider	Claude Code	Which CLI tool to use for executing agent work
Default Model	Provider default	Override the default AI model
Max Concurrent Runs	3	Maximum pipelines running simultaneously across all projects
Default Timeout	60 min	Maximum execution time per run
Remote Access	Disabled	Enable web-based remote access

Each project also has a Max Concurrent Pipelines setting (default: 1) that controls how many pipelines in that project can run at the same time.

#Remote Access

Access t0ggles Crew from any device on your network through a web browser.

#Setup

1. Go to Settings in t0ggles Crew
2. Enable Remote Access
3. Set a password (required for security)
4. Note the port (default: 3847)
5. Save settings

#Connecting

Open your browser and navigate to http://{your-machine-ip}:3847. Enter your password when prompted.

The web interface mirrors the desktop app - you can view projects, monitor runs, trigger pipelines, and stream live output.

#Security

• Password is hashed with bcrypt (never stored in plain text)
• Rate limiting: 10 failed login attempts per IP per 15 minutes
• Request body size limited to 1 MB
• Only accessible on your local network (not exposed to the internet by default)

#Troubleshooting

#CLI Provider Not Found

If t0ggles Crew can't find your CLI tool, the issue is usually PATH resolution. On macOS, apps launched from Finder don't inherit your terminal's PATH.

Fix: Make sure the CLI is installed globally with npm and restart t0ggles Crew. The app automatically resolves PATH from your login shell on startup.

#MCP Connection Failed

If an agent can't access your t0ggles board during a run, the issue is with the MCP configuration in the CLI provider (not the Crew app itself):

1. Verify your MCP token is valid in Account Settings
2. Check that the CLI provider has the t0ggles MCP server configured (see CLI Providers)
3. Run the CLI's MCP verification command to test the connection

#Pipeline Stuck in "Running"

If a pipeline appears stuck:

• Check the live output in the Log Viewer for activity
• The pipeline may be waiting for a long AI response
• If truly stuck, cancel the run manually
• Check the timeout setting - increase it if the agent needs more time

#Auto Mode Not Picking Up Tasks

For auto mode to work:

1. The project must be connected to a t0ggles board
2. The agent must have a bot user ID configured
3. Tasks must be assigned to that bot user and not in "Done" status
4. The pipeline must be enabled

The app checks for new tasks every 5 minutes, so there may be a short delay.

#Updates

t0ggles Crew automatically checks for updates on launch. When an update is available, you'll see a notification in the app. Updates are downloaded in the background and installed when you restart the app.