# Is composer 1.5 down?

**URL:** <https://forum.cursor.com/t/is-composer-1-5-down/155154>\
**Category:** Bug Reports\
**Tags:** composer, anthropic\
**Created:** [March 18, 2026, 12:13pm UTC](https://forum.cursor.com/t/is-composer-1-5-down/155154 "2026-03-18T12:13:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zeroansh](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/zeroansh/32/39125_2.png) [@zeroansh](https://forum.cursor.com/u/zeroansh)\
**Post date:** [March 18, 2026, 12:13pm UTC](https://forum.cursor.com/t/is-composer-1-5-down/155154/1 "2026-03-18T12:13:50Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Upon selecting Composer 1.5 for implementation of the plan, it keeps on thinking and planning next moves and then message appears “Taking Longer than expected”. Happening since last 30 min, retried few times didn’t work, then selected auto and it started working

### Steps to Reproduce

Create a plan using Sonnet 4.6 and implement it using Composer 1.5

### Expected Behavior

Plan should get implemented

### Screenshots / Screen Recordings

 ![Screenshot 2026-03-18 at 17.42.52.png](https://us1.discourse-cdn.com/cursor1/original/3X/e/3/e3e903cca6df678bbb41f4ca71bd32724fe610ab.png)

### Operating System

MacOS

### Version Information

IDE: Version: 2.6.19

### For AI issues: which model did you use?

Composer 1.5 & Sonnet 4.6

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [March 18, 2026, 1:19pm UTC](https://forum.cursor.com/t/is-composer-1-5-down/155154/4 "2026-03-18T13:19:50Z")

</div>

Hey, this isn’t an outage. Composer 1.5 generally works, but you might see latency spikes, especially on requests with a large context. The “Taking longer than expected” message is a client-side timeout when the model takes too long to send the first token.

The team is aware of this issue. A few things that might help:

1. Try resyncing the codebase index: `Cmd+Shift+J` \> Indexing & Docs, then restart Cursor. This helped a few users with the exact same symptoms.

2. If it happens again, send the Request ID (chat context menu in the top right \> Copy Request ID). This lets us check what was happening on the backend.

Switching to auto as a workaround is a good temporary option.

Related threads: [Stuck in 'planning next moves' then shows 'Taking longer than expected'](https://forum.cursor.com/t/stuck-in-planning-next-moves-then-shows-taking-longer-than-expected/154108), [Taking longer than expected](https://forum.cursor.com/t/taking-longer-than-expected/152616).

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [April 9, 2026, 1:20pm UTC](https://forum.cursor.com/t/is-composer-1-5-down/155154/5 "2026-04-09T13:20:01Z")

</div>

Closed on April 9, 2026, 1:20pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.