Documentation, community, status, and direct support. Find what you need below.
The dashboard shows no data after installing the agent.
Check that the license key was correctly activated: run forg status in your terminal. Verify the agent is running with forg agent status. If the heartbeat is not active, run forg activate <your-license-key>.
My Claude Code statusline isn't showing FORG data.
FORG only stamps the statusline if it's missing or already marked _forg_managed. If you have a custom ~/.claude/statusline.sh, FORG will not overwrite it. This is by design. Check the activation warning output for a notice about this.
Budget rule fired but the session cost was below my limit.
Budget rules use accumulated cost across the configured window, not per-session cost. The rule fired because total accumulated spend crossed the threshold. Check the Budget tab in the dashboard to see the full accumulation.
Cache hit rate is 0% — is the cache broken?
Cache hit rates depend on how your AI tool sends requests. Claude Code caches system prompts; conversational back-and-forth generally does not produce cache hits. A 0% rate is normal for short sessions. Check multi-turn sessions for expected cache behavior.
Response time targets by plan and severity.
| Plan | P1 — Critical | P2 — High | P3 — Normal |
|---|---|---|---|
| Solo | Best effort | Best effort | Best effort |
| Professional | Best effort | Best effort | Best effort |
| Team | 24 hours | 48 hours | 5 days |
| Business | 4 hours | 12 hours | 48 hours |
| Enterprise | 1 hour | 4 hours | 24 hours |
Uptime commitments, SLA credits, and exclusions are documented in the full SLA →
All customers can open a support ticket by emailing hello@forg.pro with your license key in the subject. Team, Business, and Enterprise customers receive SLA-backed responses.
Open a support ticket