Support

Email support@aiagentledger.dev. We aim to reply within one business day.

What to include

• Your Snowflake account's region, and the app's name if it isn't AGENTLEDGER.
• What you expected and what happened, with a screenshot of the dashboard's Setup view if it's a setup problem.
• For a developer machine: the output of agentledger status, and the log at ~/.cache/agentledger/<agent>-hook.log.

Please don't send prompts, source code or credentials unless we ask for them to fix your issue.

Common issues

Recent Cortex Code sessions are missing

Snowflake can take up to a few hours to deliver traces and ACCOUNT_USAGE rows, and the app refreshes every 30 minutes. If nothing appears at all, check that the app has been granted SNOWFLAKE.AI_OBSERVABILITY_READER (see Grant trace access).

Claude Code, Cursor or Gemini CLI sessions are missing

Run agentledger status on the developer's machine. It checks the connection to the app and which agents are hooked. The developer's role needs APP_REPORTER. Hooks load when an agent starts, so restart any agent that was open during install.

Pull requests don't appear

In Snowsight, open the app, choose Configure, and check that both the API access and the token are bound for GitHub or GitLab. Private repositories need a token that can read them. Trial accounts can't use external access. Use the push script instead (see Sync pull requests).

A pull request shows no agent cost

Pull requests are matched to sessions by branch. For Cortex Code, that needs the developer plugin. For other agents, it needs the CLI. Sessions recorded before either was installed are attributed to the agent but not to a branch.

A model shows as unpriced

New models can appear before the app's price list includes them. Add the price under Model prices on the Setup view, and costs update on the next refresh.

Security reports

If you find a security issue, email support@aiagentledger.dev with "Security" in the subject. We'll acknowledge it within two business days.