laravel/telescope

Telescope breaks SSE stream

Open

#1,717 opened on Feb 10, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)PHP (5,187 stars) (654 forks)user submission
help wanted

Description

Telescope's ClientRequestWatcher calls $response->body() on every HTTP response, which fully consumes non-seekable SSE stream bodies before Prism can read them.

This breaks the stream capability.

My current workaround to overcome this, add this before you instantiate the Agent:

if (class_exists(Telescope::class)) {
    Telescope::stopRecording();
}

Note: of course this will disable all telescope logging and monitoring for the agent requests.

Contributor guide

Tech stack
phplaravel
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic Laravel knowledgeunderstand SSE streams
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the `ClientRequestWatcher` class in Laravel Telescope. The issue is that `$response >body()` is called on every HTTP response, consuming non seekable SSE streams. Look for where `body()` is invoked on the response object and consider adding a check to skip streamed responses. The workaround described (calling `Telescope::stopRecording()`) can serve as a clue for the fix location. No linked PRs or maintainer comments are present, so the fix is open for contribution.
Telescope breaks SSE stream · laravel/telescope#1717 | Good First Issue