Troubleshooting

Solution:

1. Click the puzzle icon (extensions) in the top right of Chrome
2. Find "AutoTrack" in the list
3. Click the pin icon to pin it to the toolbar

Possible causes and solutions:

• Wrong credentials: Check if your email and password are correct
• Account doesn't exist: Try logging in first at app.autotrack.dev
• No internet: Check your internet connection
• Browser cache: Clear cache and try again

Troubleshooting steps:

1. Verify that you're logged in to the extension
2. Refresh your dashboard (F5)
3. Check the browser console for errors:
   • Press F12
   • Go to "Console" tab
   • Look for red error messages
4. Check if your API key is still valid (dashboard → API Key)
5. Try logging out and back in

Solution:

1. Go to chrome://extensions/
2. Find AutoTrack in the list
3. Click "Remove" and reinstall the extension
4. Or click "Reload" (refresh icon) to reload the extension

Solution:

Manually reinstall the git hooks:

npx @svenjens/mcp-autotrack-server postinstall

Verify that the hooks are installed:

ls -la ~/.git-templates/hooks/

You should see a post-commit file.

Troubleshooting checklist:

1. Check if you're in a git repository:
   Copy

   git status

2. Use conventional commit format:
   Copy

   git commit -m "feat: your feature description"

   Commits without prefix (feat:, fix:, etc.) are not logged!
3. Check git hooks in repository:
   Copy

   ls -la .git/hooks/

   You should see a post-commit file.
4. Check status:
   Copy

   npx @svenjens/mcp-autotrack-server status

5. Check hook executable permissions:
   Copy

   chmod +x .git/hooks/post-commit

Check these points:

1. Check auto-submit setting:
   Copy

   echo $WORKLOG_AUTO_SUBMIT

   Should be "true" (or empty, then default is true).
2. Verify authentication:
   Copy

   autotrack init

   Log in again with your credentials.
3. Check internet connection:
   Copy

   ping app.autotrack.dev

4. Refresh dashboard: Press F5 in your browser
5. Check local entries: Entries are stored locally in ~/.autotrack/

Solution:

1. Check npm version:
   Copy

   npm --version

   npm 8.0.0 or higher is required.
2. Update npm:
   Copy

   npm install -g npm@latest

3. Clear npm cache:
   Copy

   npm cache clean --force

4. Try installing again:
   Copy

   npm install -g @svenjens/mcp-autotrack-server

Troubleshooting steps:

1. Check your internet connection
2. Try a different browser
3. Clear browser cache and cookies:
   • Chrome: Settings → Privacy → Clear browsing data
   • Firefox: Settings → Privacy → Clear Data
   • Safari: Safari → Clear History
4. Check system status at status.autotrack.dev (if available)
5. Try incognito/private mode to rule out extension conflicts

Check these points:

1. Refresh the page: Press F5
2. Check filters: You might be filtering out the entries
3. Check that entries were logged:
   • Check Chrome extension popup
   • Check terminal output on git commit
4. Check browser console for errors: F12 → Console tab
5. Verify you're logged in to the correct account

Solution:

1. Check if you're logged in
2. Refresh the page (F5)
3. Check browser console for errors (F12)
4. Try logging out and back in
5. If it keeps failing, contact support

Troubleshooting:

1. Check credentials: Verify email and password
2. Password reset: Use "Forgot Password" link on login page
3. Account verification: Check if your email address is verified
4. Browser issues: Try incognito mode or different browser
5. Cookie settings: Make sure cookies are enabled

Solution:

1. Re-login: Log out and back in
2. API key refresh: Generate new API key
3. Clear tokens:
   Copy

   rm -rf ~/.autotrack/ autotrack init

4. Check API key expiration: API keys don't expire, but can be revoked

Solutions:

• Clear browser cache
• Close other tabs that use a lot of resources
• Use filters to show less data
• Update your browser to the latest version
• Check your internet speed

Possible causes:

• Network latency: The post-commit hook communicates with the API
• Solution 1: Disable auto-submit for faster commits:
  Copy

  export WORKLOG_AUTO_SUBMIT="false"

• Solution 2: Run the hook in background (coming in future version)

Possible causes:

• Multiple git hooks active (check .git/hooks/)
• Manual entry + automatic entry for the same commit
• Network retry after timeout

Solution:

• Delete duplicates manually in dashboard
• Check git hooks configuration

Troubleshooting:

1. Check if they're set:
   Copy

   echo $WORKLOG_AUTO_SUBMIT echo $WORKLOG_DASHBOARD_URL

2. Check your shell config:
   Copy

   cat ~/.bashrc | grep WORKLOG cat ~/.zshrc | grep WORKLOG

3. Reload shell:
   Copy

   source ~/.bashrc  # or ~/.zshrc

4. Restart terminal completely