---
title: Troubleshooting
description: Fixes for the problems people run into most.
url: https://docs-v3-preview.elastic.dev/troubleshooting
---

# Troubleshooting
## gh is not signed in

The first-run screen and the Inbox say so. Run `gh auth login` in any terminal; Heed notices without a restart.

## git or gh is "not found"

Heed searches your login shell's PATH and the usual install locations. If it still picks the wrong one, or none, set
it: `[tools] git = "/opt/homebrew/bin/git"`. `heed tools` in a terminal shows what Heed finds and why. See
[Finding git and gh](https://docs-v3-preview.elastic.dev/configuration/tools).

## Some pull requests or issues are missing

Items in orgs your `gh` token is not authorized for (SAML single sign-on) are counted in the title bar ("· 49 hidden")
instead of shown. `gh auth refresh`, or authorizing the GitHub CLI for that org on GitHub, brings them in.

## An agent's state is wrong or missing

Check the agent is started by Heed (its pane's command line includes Heed's hooks; see [Hooks](https://docs-v3-preview.elastic.dev/agents/hooks)). States
it cannot report are guessed from its screen, drawn with a dotted ring; add patterns for your agent under
`[agents.<name>.patterns]` ([Reading the screen](https://docs-v3-preview.elastic.dev/agents/screen-reading)).

## The Start work panel closes right away, or tiles

A tiling window manager is managing it. Add a rule for the window titled `Heed Start Work`; see
[From anywhere](https://docs-v3-preview.elastic.dev/start-work/from-anywhere).

## A key does nothing

The status bar says what Heed made of it ("gq is not bound"). Check `config.toml` for a binding that was refused (the
reason is in the status bar), and `?` for what every key does now.

## Closing the window stopped my agents

With the menu bar item off, closing the window quits Heed. Turn it on (`[ui] menu_bar = true`) and closing the window
keeps Heed and its agents running.