Troubleshooting

Why Tools Suddenly Disappeared?

If your agent was using web search, files, or commands yesterday and now says “I can’t do that,” this is usually a session/scope issue — not a broken account.

⏱ 4 minute read · Beginner

📑 In this guide

What this error usually means
2-minute fast check
Most common root causes
Advanced mismatch cases
Known-good recovery flow
Escalation packet

What this error usually means

In Heyron/OpenClaw, tools are contextual. A tool being available in one place does not guarantee it’s available in every session, channel, or execution mode.

Quick mental model

Tool access is decided by where you're talking to the agent, which session it's in, and what policy/config applies there.

2-minute fast check

Start a fresh message and ask: List tools available right now in this session.
If this is Discord, test in DM and one server channel separately.
If behavior changed after config edits, restart gateway and retest.
Try the same request in dashboard chat to compare.

Most common root causes

1) Surface mismatch (dashboard vs Discord vs Telegram)

You switched surfaces and expected the same capabilities/context instantly. Different surfaces can run with different session history and policy context.

2) New session, old assumptions

After /new or moving to a different thread/channel, your prior context is gone unless saved to files. The agent may stop using tools you expected because your prior setup instructions are no longer in that session.

3) Policy/config changed

If AGENTS.md, channel policy, or gateway settings changed recently, tools may be restricted until settings are reapplied and the runtime is restarted.

4) Approval state confusion

Some actions require approval each time (or when command shape changes). Users often interpret a blocked command as “tool disappeared.”

Advanced mismatch cases (high-friction)

5) Main session vs isolated/cron runs

A tool can be available in your live chat session but missing in a scheduled or isolated run (or vice versa). If the problem only happens in reminders/cron jobs, include that run context in your report.

6) Thread mismatch in Discord

If you test in one thread/channel and expect the same behavior in another, you can see different capability outcomes due to per-channel policy and session binding.

7) "It worked yesterday" after environment reset

After restarts, account switching, or workspace/session resets, stale assumptions from old conversations can survive in your expectations but not in current runtime state. Always re-run a tiny probe in the exact surface you are using now.

Known-good recovery flow

Use this exact order

Don’t skip steps — most loops happen when people jump straight to reinstalling everything.

Confirm current surface: dashboard chat, Discord DM, or server channel.
Run a tiny capability probe: ask for available tools in the current session.
Open a clean session: start fresh and repeat the same probe.
If recently edited config: apply + restart gateway, then retest.
If command is blocked: review the exact approval prompt and approve/deny intentionally.
If still failing: collect evidence packet below and post in #help.

Support escalation packet (copy/paste)

Copy this into #help

Issue: Tools available before, now missing or denied.

Surface: (dashboard / Discord DM / Discord channel / Telegram)

Session context: (new session? old thread? after /new?)

Recent changes: (config edits, SOUL/AGENTS edits, gateway restart Y/N)

Probe result: paste agent response to “list tools available right now”

Approval prompt seen: Y/N (paste exact text if yes)

Expected vs actual: one sentence each

Bottom line

When tools “disappear,” it’s usually context/surface/policy drift — not random failure. Verify the current session, run a tiny probe, then restart/retest before escalating.