Updated from 2026.4.14 to 2026.4.22, errors in doctor and telegram not working | Friends of the Crustacean 🦞🤝 | Page 1

fringe nymph Apr 23, 2026, 9:36 PM

#

I just updated to 2026.4.22 and I see this:

Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/dist/extensions/telegram/account-config-Cifs-fXF.js

Discord: failed (unknown) - Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/dist/extensions/discord/token-D-w3Rigl.js
Telegram: ok (@Jarvis_Dogg_bot) (184ms)
Agents: main (default)
Heartbeat interval: disabled (main)
Session store (main): /home/jarvis/.openclaw/agents/main/sessions/sessions.json (161 entries)

agent:main:telegram:direct:635178958 (10m ago)
agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44 (10m ago)
agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:45b5b929-3b75-4f3a-8a46-4ed07b6ba592 (10m ago)
agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:aaa71b3e-3343-4455-ad69-a5ae62ecf989 (40m ago)
agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:3bfe7769-2d0c-49ff-b049-f08ed276f1f6 (70m ago)
17:32:34 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:32:36 [plugins] minimax failed to load from /usr/lib/node_modules/openclaw/dist/extensions/minimax/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:32:40 [plugins] vydra failed to load from /usr/lib/node_modules/openclaw/dist/extensions/vydra/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:32:40 [plugins] 3 plugin(s) failed to initialize (load: google, minimax, vydra). Run 'openclaw plugins list' for details.
17:32:41 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
Run "openclaw doctor --fix" to apply changes.

how can I fix it

grizzled trenchBOT Apr 23, 2026, 9:36 PM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

weak pulsarBOT Apr 23, 2026, 9:36 PM

#

slim flameBOT Apr 23, 2026, 9:45 PM

#

This looks like two separate post-update issues:

staged bundled plugin deps are broken (Cannot find package 'openclaw' ... ~/.openclaw/plugin-runtime-deps/...)
the service cannot write Jiti cache files (EACCES ... /tmp/jiti/...)

I’d do this in order:

openclaw --version
openclaw doctor --fix
openclaw gateway restart

doctor --fix is the documented repair path here, and in 2026.4.22 it specifically repairs missing bundled plugin runtime deps for root-owned installs.

If it still fails after that, refresh the service metadata too:

#

openclaw gateway install --force
openclaw gateway restart

That is the documented fix when the running service config/entrypoint drifted from the current CLI install.

Because your install path is /usr/lib/node_modules/openclaw, this also looks like a root-owned global install. In that case, make sure the gateway has a writable staging dir and writable temp path. Recommended service setup is:

Environment=OPENCLAW_PLUGIN_STAGE_DIR=/var/lib/openclaw/plugin-runtime-deps
ReadWritePaths=/var/lib/openclaw /home/jarvis/.openclaw /tmp

Also, the /tmp/jiti/... EACCES errors mean the gateway user cannot write its cache there. So please check that:

/tmp is writable for the service user

#

/tmp/jiti is not left owned by root
if you override temp with TMPDIR, that path is writable too

If you still get errors after the steps above, paste these:

openclaw --version
openclaw doctor --fix
openclaw gateway status
openclaw plugins list
openclaw status --all

Docs:

#

If you want, paste the output of openclaw doctor --fix next and I’ll help interpret it.

fringe nymph Apr 23, 2026, 9:51 PM

#

🦞 OpenClaw 2026.4.22 (00bd2cf) — Greetings, Professor Falken

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
██░▄▄▄░██░▄▄░██░▄▄▄██░▀██░██░▄▄▀██░████░▄▄▀██░███░██
██░███░██░▀▀░██░▄▄▄██░█░█░██░█████░████░▀▀░██░█░█░██
██░▀▀▀░██░█████░▀▀▀██░██▄░██░▀▀▄██░▀▀░█░██░██▄▀▄▀▄██
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
                  🦞 OPENCLAW 🦞                    
 
┌  OpenClaw doctor
│
◇  Startup optimization ─────────────────────────────────────────────────────────────────────╮
│                                                                                            │
│  - NODE_COMPILE_CACHE is not set; repeated CLI runs can be slower on small hosts (Pi/VM).  │
│  - OPENCLAW_NO_RESPAWN is not set to 1; set it to avoid extra startup overhead from        │
│    self-respawn.                                                                           │
│  - Suggested env for low-power hosts:                                                      │
│    export NODE_COMPILE_CACHE=/var/tmp/openclaw-compile-cache                               │
│    mkdir -p /var/tmp/openclaw-compile-cache                                                │
│    export OPENCLAW_NO_RESPAWN=1                                                            │
│                                                                                            │
├────────────────────────────────────────────────────────────────────────────────────────────╯
17:46:22 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:22 [plugins] minimax failed to load from /usr/lib/node_modules/openclaw/dist/extensions/minimax/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:24 [plugins] vydra failed to load from /usr/lib/node_modules/openclaw/dist/extensions/vydra/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:26 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:26 [plugins] minimax failed to load from /usr/lib/node_modules/openclaw/dist/extensions/minimax/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:27 [plugins] vydra failed to load from /usr/lib/node_modules/openclaw/dist/extensions/vydra/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'

#

◇  Model auth ───────────────────────────────────────────────────────────────────────────╮
│                                                                                        │
│  - anthropic:manual: missing [missing_credential] — Re-auth via `openclaw models auth  │
│    login --provider anthropic` or `openclaw configure`.                                │
│                                                                                        │
├────────────────────────────────────────────────────────────────────────────────────────╯
│
◇  Claude CLI ─────────────────────────────────────────────────────────────────────────────╮
│                                                                                          │
│  - Binary: ~/.local/bin/claude.                                                          │
│  - Headless Claude auth: OK (oauth).                                                     │
│  - OpenClaw auth profile: missing (anthropic:claude-cli) in                              │
│    /home/jarvis/.openclaw/agents/main/agent/auth-profiles.json.                          │
│  - Workspace: ~/.openclaw/workspace (writable).                                          │
│  - Claude project dir: ~/.claude/projects/-home-jarvis--openclaw-workspace (present).    │
│  - Fix: run openclaw models auth login --provider anthropic --method cli --set-default.  │
│                                                                                          │
├──────────────────────────────────────────────────────────────────────────────────────────╯
│
◇  Gateway auth ─────────────────────────────────────────────────────────╮
│                                                                        │
│  Gateway token is managed via SecretRef and is currently unavailable.  │
│  Doctor will not overwrite gateway.auth.token with a plaintext value.  │
│  Resolve/rotate the external secret source, then rerun doctor.         │
│                                                                        │
├────────────────────────────────────────────────────────────────────────╯
│
◇  Security ─────────────────────────────────╮
│                                            │
│  - No channel security warnings detected.  │
│  - Run: openclaw security audit --deep     │
│                                            │
├────────────────────────────────────────────╯
│
◇  Skills status ────────────╮
│                            │
│  Eligible: 13              │
│  Missing requirements: 43  │
│  Blocked by allowlist: 0   │
│                            │
├────────────────────────────╯
│
◇  Plugins ──────╮
│                │
│  Loaded: 61    │
│  Imported: 47  │
│  Disabled: 41  │
│  Errors: 0     │
│                │
├────────────────╯

#

Discord: failed (unknown) - Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/openclaw-2026.4.22-4eca5026e977/dist/extensions/discord/token-D-w3Rigl.js
Telegram: ok (@Jarvis_Dogg_bot) (622ms)
Agents: main (default)
Heartbeat interval: disabled (main)
Session store (main): /home/jarvis/.openclaw/agents/main/sessions/sessions.json (161 entries)
- agent:main:telegram:direct:635178958 (24m ago)
- agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44 (24m ago)
- agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:45b5b929-3b75-4f3a-8a46-4ed07b6ba592 (24m ago)
- agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:aaa71b3e-3343-4455-ad69-a5ae62ecf989 (54m ago)
- agent:main:cron:80df5eae-a92b-412a-a045-70944380ca44:run:3bfe7769-2d0c-49ff-b049-f08ed276f1f6 (84m ago)
17:46:43 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:44 [plugins] minimax failed to load from /usr/lib/node_modules/openclaw/dist/extensions/minimax/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:48 [plugins] vydra failed to load from /usr/lib/node_modules/openclaw/dist/extensions/vydra/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
17:46:48 [plugins] 3 plugin(s) failed to initialize (load: google, minimax, vydra). Run 'openclaw plugins list' for details.
17:46:49 [plugins] google failed to load from /usr/lib/node_modules/openclaw/dist/extensions/google/index.js0m: Error: EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'
│
└  Doctor complete.

slim flameBOT Apr 23, 2026, 9:52 PM

#

Yep, this is much clearer now.

The startup optimization block is unrelated. The real blocker is:

EACCES: permission denied, open '/tmp/jiti/providers-openai-completions.0921031d.cjs'

That means the gateway cannot write its Jiti cache, and that can prevent the bundled plugin repair from completing.

Do this first

Check the temp permissions:

ls -ld /tmp /tmp/jiti

#

What you want:

/tmp should be writable (normally mode 1777)
/tmp/jiti must not be stuck owned by root or another user if the gateway runs as jarvis

If /tmp/jiti is stale/wrongly owned, fix or recreate that cache dir so the gateway user can write there.

Then rerun the repair

openclaw doctor --fix
openclaw gateway restart

That doctor --fix path is the documented repair for the earlier:

#

Cannot find package 'openclaw' imported from ~/.openclaw/plugin-runtime-deps/...

especially on root-owned global installs like yours under:

/usr/lib/node_modules/openclaw

For root-owned installs, make sure the service has a writable plugin stage dir

Recommended service config:

Environment=OPENCLAW_PLUGIN_STAGE_DIR=/var/lib/openclaw/plugin-runtime-deps

#

ReadWritePaths=/var/lib/openclaw /home/jarvis/.openclaw /tmp

If /tmp is restricted in your service, use a writable TMPDIR for the gateway too.

If it still looks wrong after that

Refresh the service metadata as well:

openclaw gateway install --force
openclaw gateway restart

That is the documented fix when the service config/entrypoint drifted from the current CLI install.

#

If it still fails, paste these

openclaw doctor --fix
openclaw gateway status
openclaw plugins list
openclaw status --all

Docs:

If you paste the ls -ld /tmp /tmp/jiti output plus doctor --fix, I can help narrow it down fast.

#

Nice, this changes the diagnosis a lot.

The original plugin/update issue looks mostly repaired now. The key line is:

Plugins: Errors: 0

So the earlier Cannot find package 'openclaw' ... ~/.openclaw/plugin-runtime-deps/... issue does not look like the current blocker anymore.

What’s left now is mostly auth/secrets, not plugin loading:

1) Anthropic / Claude CLI auth is missing

If you actually want to use Claude/Anthropic, run:

#

openclaw models auth login --provider anthropic --method cli --set-default

That should repair the missing anthropic:claude-cli profile.

If you do not use Anthropic/Claude, this warning is not the reason Discord/Telegram broke.

2) Your gateway token SecretRef is unresolved

This is the important one now:

Gateway token is managed via SecretRef and is currently unavailable.

#

That means OpenClaw expects the gateway token from an external secret source, but that source is not available in the current runtime.

What to fix depends on how you stored it:

env SecretRef: make sure the env var is available to the gateway service, not just your shell
file SecretRef: make sure the file exists and is readable by the service user
exec SecretRef: make sure that command still works for the service user

Then rerun:

openclaw doctor --fix
openclaw gateway restart

#

3) Re-check the running service

After fixing the SecretRef, verify:

openclaw gateway status
openclaw channels status --probe

If the service config got stale during the update, also do:

openclaw gateway install --force
openclaw gateway restart

#

Short version

At this point I’d do:

openclaw models auth login --provider anthropic --method cli --set-default
openclaw doctor --fix
openclaw gateway restart
openclaw gateway status
openclaw channels status --probe

And if your gateway token is SecretRef-backed, fix that secret source first.

Docs:

#

If you paste the gateway.auth.token part of your config, I can tell you exactly whether it’s an env, file, or exec SecretRef and what to fix.

#

Thanks, this helps. I was wrong to focus on auth before, the real blockers are still the runtime/plugin errors.

What your latest output says:

doctor --fix finishes
but you still have:
- EACCES ... /tmp/jiti/...
- Discord: failed ... Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/...

So I’d treat it like this:

1) Fix `/tmp/jiti` first

That one is a plain permissions problem.

Please check:

#

ls -ld /tmp /tmp/jiti

What should be true:

/tmp should usually be drwxrwxrwt (1777)
/tmp/jiti should either not exist, or be writable by the user running the gateway

If your service is hardened, also make sure it can write there:

/tmp is in ReadWritePaths
or TMPDIR points to a writable directory for the service

2) Then rerun the repair

openclaw doctor --fix

#

openclaw gateway restart
openclaw channels status --probe

3) If Discord still shows the same `Cannot find package 'openclaw'`

At that point, I think this is likely a 2026.4.22 regression in the staged bundled plugin runtime, not your config.

Then I’d try:

openclaw update
openclaw doctor --fix
openclaw gateway restart

If gateway status shows the service config is stale/different from CLI, also run:

#

openclaw gateway install --force
openclaw gateway restart

4) If it still reproduces after `/tmp` is fixed

Please paste:

ls -ld /tmp /tmp/jiti
openclaw gateway status
openclaw plugins list
openclaw channels status --probe

And if the Discord Cannot find package 'openclaw' error is still there after that, I’d file it as a bug here:

#

https://github.com/openclaw/openclaw/issues

Docs:

If you paste the ls -ld /tmp /tmp/jiti output next, I can tell you pretty quickly which side is broken.

fringe nymph Apr 23, 2026, 9:54 PM

#

s -ld /tmp /tmp/jiti
drwxrwxrwt 34 root root 4096 Apr 23 17:42 /tmp
drwxrwxr-x 2 jarvis jarvis 233472 Apr 23 17:52 /tmp/jiti

slim flameBOT Apr 23, 2026, 9:55 PM

#

Yep, that pinpoints it.

/tmp is fine. The problem is /tmp/jiti:

drwxrwxr-x  2 jarvis jarvis ...

That means only jarvis and its group can write there. If the gateway/service is running as a different user, Jiti cache writes fail, and that can cascade into the bundled plugin load failure.

I’d do this next

Because /tmp/jiti is just cache, move it aside and let OpenClaw recreate it:

openclaw gateway stop

#

mv /tmp/jiti /tmp/jiti.bak.$(date +%s)
openclaw gateway start
openclaw doctor --fix
openclaw channels status --probe

Why

Your current blocker is still:

EACCES: permission denied, open '/tmp/jiti/...'

Until that is gone, the later:

#

Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/...

may just be a downstream symptom.

If it comes back

Then the service is probably not running as jarvis, or it has a restricted temp dir. In that case, check:

openclaw gateway status

and make sure the service has writable runtime paths. For root-owned installs, the docs recommend:

#

Environment=OPENCLAW_PLUGIN_STAGE_DIR=/var/lib/openclaw/plugin-runtime-deps
ReadWritePaths=/var/lib/openclaw /home/jarvis/.openclaw /tmp

If gateway status still shows service drift, also run:

openclaw gateway install --force
openclaw gateway restart

If you paste openclaw gateway status after the restart, I can tell you pretty quickly whether it’s still a temp-dir permission issue or a real 2026.4.22 plugin regression.

Docs:

#

https://docs.openclaw.ai/gateway/doctor

fringe nymph Apr 23, 2026, 10:05 PM

#

so it still doesnt answer in telegram, I messaged on the dashbaord and it forgot who it was and is starting from scratch now.... how can I go back to how it was before?

slim flameBOT Apr 23, 2026, 10:06 PM

#

Ugh, that’s frustrating. The good news is this usually means it’s pointing at the wrong runtime/session state, not that your old memory is gone.

Two ways back:

Fastest check, make sure the service is using the same state/config as before

Run:

openclaw gateway status

If it shows Config (cli) and Config (service) are different, fix that with:

openclaw gateway install --force
openclaw gateway restart

#

That often brings the bot back to the same profile/state dir, which is why it can stop “starting from scratch”.

If you just want to go back to the old version now

Docs-supported rollback:

npm i -g openclaw@2026.4.14
openclaw doctor
openclaw gateway restart

That should get you back to the pre-update behavior fastest.

Why I think this is recoverable

Your old state looked like it was still under:

#

/home/jarvis/.openclaw/agents/main/sessions/sessions.json

So this smells more like service drift / wrong profile / wrong runtime path than erased history.

If Telegram still doesn’t answer after that

Then I’d also clear the temp cache issue we found earlier and restart once:

openclaw gateway stop
mv /tmp/jiti /tmp/jiti.bak.$(date +%s)
openclaw gateway start

Then test again.

#

If you paste the output of:

openclaw gateway status

I can tell you which of the two it is:

wrong config/state dir
real 2026.4.22 regression

Docs:

fringe nymph Apr 23, 2026, 10:13 PM

#

🦞 OpenClaw 2026.4.22 (00bd2cf) — I'm basically a Swiss Army knife, but with more opinions and fewer sharp edges.

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-23.log
Command: /usr/bin/node /usr/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: running (pid 412253, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: 127.0.0.1:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

running the downgrade command now...

slim flameBOT Apr 23, 2026, 10:14 PM

#

That status is actually really helpful, glad we got it.

Since:

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json
gateway is running
probe is ok

this does not look like wrong profile/state-dir drift anymore. It looks much more like a 2026.4.22 regression.

So yes, rolling back is the right move.

After the downgrade finishes, run:

#

openclaw --version
openclaw doctor
openclaw gateway restart
openclaw channels status --probe

If 2026.4.14 starts replying on Telegram again, that strongly confirms the update introduced the breakage. Your existing state under ~/.openclaw should still be there, so it should come back on the old version.

If it works again, please file a GitHub issue with the exact errors you posted:

Cannot find package 'openclaw' imported from /home/jarvis/.openclaw/plugin-runtime-deps/...
EACCES: permission denied, open '/tmp/jiti/providers-openai-completions...cjs'

Issue link:
https://github.com/openclaw/openclaw/issues

If the downgrade doesn't fix it, paste:

#Updated from 2026.4.14 to 2026.4.22, errors in doctor and telegram not working

Do this first

Then rerun the repair

For root-owned installs, make sure the service has a writable plugin stage dir

If it still looks wrong after that

If it still fails, paste these

1) Anthropic / Claude CLI auth is missing

2) Your gateway token SecretRef is unresolved

3) Re-check the running service

Short version

1) Fix /tmp/jiti first

2) Then rerun the repair

3) If Discord still shows the same Cannot find package 'openclaw'

4) If it still reproduces after /tmp is fixed

I’d do this next

Why

If it comes back

Fastest check, make sure the service is using the same state/config as before

If you just want to go back to the old version now

Why I think this is recoverable

If Telegram still doesn’t answer after that

1) Fix `/tmp/jiti` first

3) If Discord still shows the same `Cannot find package 'openclaw'`

4) If it still reproduces after `/tmp` is fixed