-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
Common issues and how to resolve them.
The binary is installed but your shell hasn't loaded the updated $PATH.
Fix:
source ~/.zshrc
lantern --versionRust is not installed or not in your $PATH.
Fix:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source ~/.cargo/env
source ~/.zshrcFix:
brew install temporal-cli
source ~/.zshrcMake sure you have Rust 1.70+:
rustc --versionIf you're below 1.70, update:
rustup updateThen try building again:
cargo build --releaseLantern requires iTerm2 (not Terminal.app).
Fix:
Install iTerm2 from https://iterm2.com/ or:
brew install iterm2Services might already be running or ports are in use.
Fix:
lantern down
sleep 2
lantern up
lantern doctorPort 8243 or 8244 might be in use.
Fix:
lsof -i :8243
lsof -i :8244Kill any process using these ports, then:
lantern restartThe MCP server isn't running or the agent CLI isn't configured.
Fix:
lantern doctor # Check all services
lantern up # Start services if needed
lantern startwork myproject # Try againA squad with that session ID is already active or wasn't cleaned up properly.
Fix:
lantern status # Find the session ID
lantern stopwork myproject-1 # Stop the squad
lantern startwork myproject # Try again with a different slot numberThe agent might be stuck or crashed.
Fix:
lantern recover myproject-1-aiMake sure you're in the correct directory:
pwd
git status
lantern startworkIf the repo name is different, specify it:
lantern startwork my-repo-name 1Make sure all dependencies are up to date:
cargo testIf tests fail with SQLite errors, you may need to set up the offline cache:
SQLX_OFFLINE=true cargo testFormat your code before committing:
cargo fmtCheck that it passes the format check:
cargo fmt --checkRun clippy to see all warnings:
cargo clippyFix any critical warnings before pushing.
lantern logs relaylantern logs temporalRUST_LOG=debug lantern up
RUST_LOG=debug lantern startwork myprojectNot yet. Lantern is macOS-only (iTerm2 dependency). Linux and Windows support are planned for a future release.
No. Temporal is optional and used for workflow logging. Lantern works fine without it.
Yes! Each squad is independent. Use different slot numbers:
lantern startwork project-a 1
lantern startwork project-a 2
lantern startwork project-b 1
lantern status # shows all active squadslantern stopwork myproject-1 --preserve-worktreesThis closes the terminal window but leaves the branches and worktrees in place for manual cleanup.
Yes! Lantern supports:
-
claude(default) -
codex(OpenAI) -
kimi(Kimi/MoonshotAI) -
gemini(Google) -
agy(AGI Lab) -
goose(solo mode)
lantern startwork myproject 2 --agent codexAll data is stored locally at ~/.lantern/:
-
State:
~/.lantern/data/relay/lantern.db(SQLite) -
Temporal data:
~/.lantern/data/temporal/(optional) -
Logs:
~/.lantern/logs/ -
Config:
~/.lantern/config/(rarely used)
Lantern is designed for local development only. No cloud connectivity, no credentials, no secrets. See Security for details.
- Check the Command Reference
- File an issue on GitHub
- Review Installation & Setup for prerequisite setup