#Troubleshooting
Solutions for the most common JAT issues. If your problem isnt listed here, check jat-doctor for a full installation diagnostic.
jat-doctor#IDE themes not working
The most frequent IDE issue. Symptoms: theme selector changes the data-theme attribute but colors stay the same.
The cause is almost always Tailwind v3 syntax in app.css. JAT uses Tailwind CSS v4, which has completely different config syntax.
Wrong (v3):
@tailwind base;
@tailwind components;
@tailwind utilities;Correct (v4):
@import "tailwindcss";
@plugin "daisyui" {
themes: light, dark, nord --default, ...;
}If you've confirmed the syntax is correct, clear the build cache:
cd ~/code/jat/ide
rm -rf .svelte-kit node_modules/.vite
npm run devThen hard refresh your browser with Ctrl+Shift+R.
#Agent shows offline or disconnected
Every Claude Code session must run inside tmux for the IDE to track it. If you started Claude directly without tmux, the IDE cant see it.
# Wrong - no tmux
cd ~/code/chimaro && claude "/jat:start"
# Correct - use a launcher function
jat-chimaro
# Or use the jat CLI for multi-agent
jat chimaro 4 --autoIf launcher functions arent installed:
~/code/jat/tools/scripts/setup-bash-functions.sh
source ~/.bashrc#Agent Registry "not registered"
This happens when an agent tries to reserve files or check identity before registering. The quickest fix is to run /jat:start, which auto-registers the agent.
Manual registration:
am-register --name YourAgentName --program claude-code --model sonnet-4.5Verify with:
am-whoami
am-agents#Browser tools not found
If browser-start.js or other browser tools return "command not found", the symlinks are probably missing. Reinstall:
cd ~/code/jat
./install.shIf the tools exist but fail to connect, make sure Chrome is running with remote debugging:
google-chrome --remote-debugging-port=9222And check that npm dependencies are installed:
cd ~/code/jat/tools/browser && npm install#Statusline not updating
The statusline reads from session files to show agent identity, task, and status. If its blank or stale:
# Verify you're in a tmux session
echo $TMUX
# Check if the session file exists
ls /tmp/jat-signal-tmux-*.json
# Manually write agent identity
SESSION_ID=$(cat /tmp/claude-session-${PPID}.txt | tr -d '\n')
mkdir -p .claude/sessions
echo "YourAgentName" > ".claude/sessions/agent-${SESSION_ID}.txt"#Common error codes
| Error | Cause | Fix |
|---|---|---|
command not found |
~/.local/bin not in PATH |
Add to ~/.bashrc: export PATH="$HOME/.local/bin:$PATH" |
am-whoami fails |
Database not initialized | Run bash ~/code/jat/tools/scripts/install-agent-mail.sh |
jt: command not found |
Task CLI not installed | Run ./install.sh to create symlinks |
NOT IN TMUX SESSION |
Claude started outside tmux | Exit and restart with launcher function |
| File conflict | Another agent declared the same files | Check jt show for file declarations, coordinate |
from_agent not registered |
Agent didnt run am-register | Run /jat:start to auto-register |
| IDE shows blank page | Dependencies missing | Run cd ~/code/jat/ide && npm install |
| Broken symlinks | Stale installation | Run ./install.sh to refresh |
#Fresh IDE build
When in doubt, nuke the caches and rebuild:
cd ~/code/jat/ide
rm -rf .svelte-kit node_modules/.vite
npm run dev#See also
- Installation - Initial setup steps
- CLI Reference - Command reference with --help
- Projects - Project configuration