Can't Connect
-
• Check that your API key is entered correctly in Settings (Ctrl+,)
-
• Ensure you have an active internet connection — Hikari needs to reach the Anthropic API
- • Try setting an explicit working directory rather than leaving it blank
- • Check the Debug Console (Ctrl+`) for error details
Hikari Seems Stuck or Stopped Responding
-
• Press Ctrl+C (when no text is selected) to interrupt the current process
- • If that doesn't work, disconnect and reconnect from the connection bar
-
• Check the Stats panel for context window usage — if it's near 100%, use
Compact Conversation to free up space
API Errors or Rate Limits
- • Verify your API key is valid at console.anthropic.com
- • Check that your account has sufficient API credits
-
• If you hit rate limits frequently, consider switching to a faster/cheaper model in
Settings
- • The Debug Console will show the specific error returned by the API
Tool Permissions Blocking Work
-
• When prompted, you can choose Allow for session to avoid repeated prompts
- • Adjust the permission mode in Settings to auto-approve trusted tools
-
• If a tool call was denied by mistake, simply ask Hikari to try again — she'll prompt you
once more
Missing Features or Greyed-Out Buttons
- • Some features require an active connection — connect to a working directory first
-
• The File Editor (Ctrl+E) is only available when connected
- • The Agent Monitor shows activity only during Task Loop or multi-agent sessions
Workspace Trust Prompt
If you see a trust prompt when connecting, it means Hikari detected hooks, MCP servers, or
slash commands in your working directory. Review them carefully before clicking
Trust & Connect. See the Panels & Tools page for more
details.
Context Window Full
Watch the context bar in the Stats panel. When it approaches 100%:
-
• Use Compact Conversation from the menu to summarise and compress the history
-
• Use Start Fresh with Context to begin a new session that carries over a summary
Reporting Issues
If you encounter a bug or unexpected behaviour, please report it on our
GitHub issues page. Include:
- • What you were doing when the issue occurred
- • Any error messages from the Debug Console
- • The app version (shown in the About panel)
You can also join our Discord community (link in the menu) for real-time support.