Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Notion skill available in Dashboard runtime but unavailable in Telegram runtime (“skill bridge isn’t active”) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#69640•Fetched 2026-04-22 07:49:50
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
0ksamyt0ksamyt
Participants
0ksamyt0ksamyt
Timeline (top)
labeled ×2

Version OpenClaw 2026.4.15 (041266a) (also observed on 2026.4.14)

Environment

• Ubuntu 24.04 VPS • Gateway managed via systemd --user • Telegram channel with 2 accounts: • default (news-digest) • time-manager (Stella bot)

Problem Same agent/config works from Dashboard context, but in Telegram runtime the agent reports: “I can’t execute the Notion skill directly from this runtime right now (skill bridge isn’t active here)” I want identical skill/tool behavior between Dashboard and Telegram for the same agent/runtime.

Expected behavior If notion skill is listed as available and API key is configured, the Telegram-routed agent should be able to execute the Notion flow the same way as Dashboard.

Actual behavior

• Dashboard: Notion workflow appears available. • Telegram (accountId=time-manager -> agentId=time-manager): reports no active skill bridge / cannot execute Notion skill.

Relevant checks already done

  1. Routing is correct: • telegram accountId=default -> news-digest • telegram accountId=time-manager -> time-manager
  2. Telegram accounts configured correctly (channels.telegram.accounts).
  3. time-manager agent is active and bound to Stella bot.
  4. Notion skill directory exists: • ~/.npm-global/lib/node_modules/openclaw/skills/notion/SKILL.md
  5. Attempting plugins.entries.notion.enabled=true shows: • plugin not found: notion (stale config entry ignored)
  6. So Notion is present as a skill definition, but runtime execution differs by surface/channel context.

Additional symptom During setup, openclaw agents add can also fail in channel config flow with: TypeError: Cannot read properties of undefined (reading 'trim') (Seen near “undefined account” / “Finished” option in wizard.)

Repro (runtime inconsistency)

  1. Configure Telegram accounts + bindings for time-manager.
  2. Confirm agent and binding: • openclaw agents list --bindings
  3. In Telegram (Stella bot), ask: • “Use skill notion now. Query database ...”
  4. Telegram response: • “skill bridge isn’t active”
  5. In Dashboard context, same Notion-oriented workflow is available.

Request Please unify runtime skill bridge behavior across Dashboard and Telegram surfaces (same agent, same config), or document why surface-specific runtime capability differs and how to force parity.

Root Cause

Version OpenClaw 2026.4.15 (041266a) (also observed on 2026.4.14)

Environment

• Ubuntu 24.04 VPS • Gateway managed via systemd --user • Telegram channel with 2 accounts: • default (news-digest) • time-manager (Stella bot)

Problem Same agent/config works from Dashboard context, but in Telegram runtime the agent reports: “I can’t execute the Notion skill directly from this runtime right now (skill bridge isn’t active here)” I want identical skill/tool behavior between Dashboard and Telegram for the same agent/runtime.

Expected behavior If notion skill is listed as available and API key is configured, the Telegram-routed agent should be able to execute the Notion flow the same way as Dashboard.

Actual behavior

• Dashboard: Notion workflow appears available. • Telegram (accountId=time-manager -> agentId=time-manager): reports no active skill bridge / cannot execute Notion skill.

Relevant checks already done

  1. Routing is correct: • telegram accountId=default -> news-digest • telegram accountId=time-manager -> time-manager
  2. Telegram accounts configured correctly (channels.telegram.accounts).
  3. time-manager agent is active and bound to Stella bot.
  4. Notion skill directory exists: • ~/.npm-global/lib/node_modules/openclaw/skills/notion/SKILL.md
  5. Attempting plugins.entries.notion.enabled=true shows: • plugin not found: notion (stale config entry ignored)
  6. So Notion is present as a skill definition, but runtime execution differs by surface/channel context.

Additional symptom During setup, openclaw agents add can also fail in channel config flow with: TypeError: Cannot read properties of undefined (reading 'trim') (Seen near “undefined account” / “Finished” option in wizard.)

Repro (runtime inconsistency)

  1. Configure Telegram accounts + bindings for time-manager.
  2. Confirm agent and binding: • openclaw agents list --bindings
  3. In Telegram (Stella bot), ask: • “Use skill notion now. Query database ...”
  4. Telegram response: • “skill bridge isn’t active”
  5. In Dashboard context, same Notion-oriented workflow is available.

Request Please unify runtime skill bridge behavior across Dashboard and Telegram surfaces (same agent, same config), or document why surface-specific runtime capability differs and how to force parity.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Version OpenClaw 2026.4.15 (041266a) (also observed on 2026.4.14)

Environment

• Ubuntu 24.04 VPS • Gateway managed via systemd --user • Telegram channel with 2 accounts: • default (news-digest) • time-manager (Stella bot)

Problem Same agent/config works from Dashboard context, but in Telegram runtime the agent reports: “I can’t execute the Notion skill directly from this runtime right now (skill bridge isn’t active here)” I want identical skill/tool behavior between Dashboard and Telegram for the same agent/runtime.

Expected behavior If notion skill is listed as available and API key is configured, the Telegram-routed agent should be able to execute the Notion flow the same way as Dashboard.

Actual behavior

• Dashboard: Notion workflow appears available. • Telegram (accountId=time-manager -> agentId=time-manager): reports no active skill bridge / cannot execute Notion skill.

Relevant checks already done

  1. Routing is correct: • telegram accountId=default -> news-digest • telegram accountId=time-manager -> time-manager
  2. Telegram accounts configured correctly (channels.telegram.accounts).
  3. time-manager agent is active and bound to Stella bot.
  4. Notion skill directory exists: • ~/.npm-global/lib/node_modules/openclaw/skills/notion/SKILL.md
  5. Attempting plugins.entries.notion.enabled=true shows: • plugin not found: notion (stale config entry ignored)
  6. So Notion is present as a skill definition, but runtime execution differs by surface/channel context.

Additional symptom During setup, openclaw agents add can also fail in channel config flow with: TypeError: Cannot read properties of undefined (reading 'trim') (Seen near “undefined account” / “Finished” option in wizard.)

Repro (runtime inconsistency)

  1. Configure Telegram accounts + bindings for time-manager.
  2. Confirm agent and binding: • openclaw agents list --bindings
  3. In Telegram (Stella bot), ask: • “Use skill notion now. Query database ...”
  4. Telegram response: • “skill bridge isn’t active”
  5. In Dashboard context, same Notion-oriented workflow is available.

Request Please unify runtime skill bridge behavior across Dashboard and Telegram surfaces (same agent, same config), or document why surface-specific runtime capability differs and how to force parity.

Steps to reproduce

  1. Install and run OpenClaw (2026.4.15) with gateway managed by systemd --user.
  2. Configure Telegram with two accounts in channels.telegram.accounts: • default • time-manager
  3. Configure agent bindings: • telegram + accountId=default -> agentId=news-digest • telegram + accountId=time-manager -> agentId=time-manager
  4. Verify routing is correct: • openclaw agents list --bindings
  5. In Telegram, open the bot mapped to time-manager and send a Notion request, e.g.: • “Use skill notion now. Query database <id> ...”
  6. Observe response in Telegram: • “I can’t execute the Notion skill directly from this runtime right now (skill bridge isn’t active here).”
  7. Run a similar Notion-oriented request from Dashboard context for the same setup.
  8. Observe mismatch: Dashboard flow is available, Telegram runtime reports no active skill bridge.

Expected behavior

If notion skill is listed as available and API key is configured, the Telegram-routed agent should be able to execute the Notion flow the same way as Dashboard.

Actual behavior

• Dashboard: Notion workflow appears available. • Telegram (accountId=time-manager -> agentId=time-manager): reports no active skill bridge / cannot execute Notion skill.

OpenClaw version

2026.4.15 (041266a)

Operating system

Ubuntu 24.04 VPS

Install method

No response

Model

openai-codex/gpt-5.3-codex (agent default)

Provider / routing chain

No external reverse proxy in front of gateway (loopback bind, local systemd gateway)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The Notion skill bridge inconsistency between Dashboard and Telegram contexts may be resolved by re-examining the skill configuration and ensuring that the Notion skill is properly enabled and configured for the time-manager agent.

Guidance

  • Verify that the Notion skill is correctly configured and enabled for the time-manager agent by checking the plugins.entries.notion.enabled setting and ensuring it is set to true.
  • Check the channels.telegram.accounts configuration to ensure that the time-manager account is properly set up and bound to the correct agent.
  • Review the OpenClaw logs for any errors or warnings related to the Notion skill or the time-manager agent to identify potential issues.
  • Attempt to reproduce the issue with a minimal configuration to isolate the cause of the problem.

Example

No code snippet is provided as the issue seems to be related to configuration and setup rather than code.

Notes

The issue may be related to the way the Notion skill is configured or enabled for the time-manager agent, or it could be a bug in the OpenClaw software. Further investigation and debugging are needed to determine the root cause.

Recommendation

Apply workaround: Re-check and re-configure the Notion skill and time-manager agent settings to ensure consistency between Dashboard and Telegram contexts. This may involve updating the plugins.entries.notion.enabled setting or re-binding the time-manager account to the correct agent.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

If notion skill is listed as available and API key is configured, the Telegram-routed agent should be able to execute the Notion flow the same way as Dashboard.

#api#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix [Bug]: Notion skill available in Dashboard runtime but unavailable in Telegram runtime (“skill bridge isn’t active”) [1 participants]