Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: iMessage messages containing only URLs are not delivered to agent [2 comments, 2 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#57305•Fetched 2026-04-08 01:51:16
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
brianeggebrianegge
Participants
brianeggebrianeggevincentkocvincentkoc
Timeline (top)
commented ×2labeled ×2closed ×1locked ×1

When an iMessage contains only a URL (no other text), the message is not delivered to the agent context. Messages before and after are received successfully.

Root Cause

When an iMessage contains only a URL (no other text), the message is not delivered to the agent context. Messages before and after are received successfully.

Fix Action

Fix / Workaround

Workaround: Add " before or after the URL.

Code Example

Test sequence confirmed:
- Sent "1" → Agent acknowledged
- Sent URL alone → Agent received no message
- Sent "3" → Agent acknowledged (no mention of URL message)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

When an iMessage contains only a URL (no other text), the message is not delivered to the agent context. Messages before and after are received successfully.

Steps to reproduce

  1. Configure iMessage channel (BlueBubbles) with OpenClaw
  2. Send message containing just "1"
  3. Send message containing only a URL: https://github.com/bitfocus/companion/issues/4047
  4. Send message containing just "3"
  5. Observe agent receives messages 1 and 3 but not the URL message

Expected behavior

All three messages should be delivered to the agent context in sequential order.

Actual behavior

Message 1: ✅ Received Message 2 (URL only): ❌ NOT received   Message 3: ✅ Received

The URL-only message never appears in the agent's conversation context.

OpenClaw version

v2026.3.x (current)

Operating system

macOS 15.3

Install method

npm global

Model

anthropic/claude-sonnet-4-5

Provider / routing chain

anthropic

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Test sequence confirmed:
- Sent "1" → Agent acknowledged
- Sent URL alone → Agent received no message
- Sent "3" → Agent acknowledged (no mention of URL message)

Impact and severity

  • Affected: All iMessage users who share URLs without additional text
  • Severity: Medium (blocks URL sharing workflow)
  • Frequency: 100% reproducible (3/3 test attempts)
  • Consequence: Users must add explanatory text with every URL share, otherwise the link is silently dropped

Additional information

This affects quick link-sharing workflows common in:

  • GitHub issue/PR references
  • Documentation links
  • Any URL-first communication pattern

Workaround: Add " before or after the URL.

extent analysis

Fix Plan

To fix the issue of messages containing only a URL not being delivered to the agent context, we need to modify the message processing logic to handle URL-only messages.

Step-by-Step Solution

  1. Update the message processing function to check if the message contains only a URL.
  2. Add a condition to handle URL-only messages and ensure they are delivered to the agent context.

Example Code

import re

def process_message(message):
    # Check if message contains only a URL
    if re.match(r'^https?://\S+$', message):
        # Handle URL-only message
        return deliver_url_message(message)
    else:
        # Handle regular message
        return deliver_regular_message(message)

def deliver_url_message(message):
    # Logic to deliver URL-only message to agent context
    # ...
    return True

def deliver_regular_message(message):
    # Logic to deliver regular message to agent context
    # ...
    return True

Verification

To verify the fix, follow these steps:

  1. Send a message containing only a URL.
  2. Check if the message is delivered to the agent context.
  3. If the message is delivered, the fix is successful.

Extra Tips

  • Ensure the regular expression used to match URLs is accurate and covers all possible URL formats.
  • Consider adding additional logging or debugging statements to monitor the message processing flow and identify any potential issues.

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

All three messages should be delivered to the agent context in sequential order.

#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

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

Back to top recommendations

TRENDING