# What features do you wish existed but don't?

**URL:** <https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319>\
**Category:** Discussions\
**Created:** [December 31, 2024, 10:11am UTC](https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319 "2024-12-31T10:11:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![namanyayg](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/namanyayg/32/17553_2.png) [@namanyayg](https://forum.cursor.com/u/namanyayg)\
**Post date:** [December 31, 2024, 10:11am UTC](https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319/1 "2024-12-31T10:11:34Z")

</div>

Using Cursor daily and while it’s great for many things, I keep running into limitations.

What features would make your workflow 10x better?

---

<div class="post-metadata">

**Author:** ![Bin\_Zhou1](https://avatars.discourse-cdn.com/v4/letter/b/7993a0/32.png) [@Bin\_Zhou1](https://forum.cursor.com/u/Bin_Zhou1)\
**Post date:** [April 2, 2026, 6:03pm UTC](https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319/2 "2026-04-02T18:03:19Z")

</div>

**Title:** Show elapsed time indicator while agent is working

**Problem:**

When using Agent mode for complex tasks (CI monitoring, multi-file refactoring, codebase exploration), responses can take anywhere from 30 seconds to several minutes depending on the number of tool calls. There’s currently no way to see how long the current response has been running. I often lose track of time and can’t tell if the agent is making progress or stuck.

After a response completes, the elapsed time is shown – but that’s too late to be useful for time management during a session.

**Proposed solution:**

Display a live elapsed timer (e.g. `0:42`) next to the “Stop” button or the thinking/tool-call indicator while the agent is actively generating a response. The timer should:

- Start when the request is submitted
- Update every second
- Remain visible as the final elapsed time after the response completes (this already exists)

**Why this matters:**

- Helps gauge whether a task is progressing normally or taking unusually long
- Makes it easier to decide when to stop and redirect the agent
- Useful for estimating cost/time of recurring workflows (e.g. “this type of query usually takes ~2 min”)
- Low-effort UI addition – the infrastructure already exists since elapsed time is shown post-completion

**Mockup:**

```auto
[Thinking...] ⏱ 1:23 [■ Stop]

```

or integrated into the existing progress indicator area.

---

<div class="post-metadata">

**Author:** ![ketrinnnnnnnnn](https://avatars.discourse-cdn.com/v4/letter/k/bb73d2/32.png) [@ketrinnnnnnnnn](https://forum.cursor.com/u/ketrinnnnnnnnn)\
**Post date:** [April 2, 2026, 11:35pm UTC](https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319/3 "2026-04-02T23:35:15Z")

</div>

> [@namanyayg](#):
>
> Using Cursor daily and while it’s great for many things, I keep running into limitations.
> 
> What features would make your workflow 10x better?

**Better debugging flow**. Instead of just suggesting fixes, it would be great if it could systematically narrow down issues, like checking assumptions step by step rather than jumping to conclusions.

---

<div class="post-metadata">

**Author:** ![Peter\_Cox](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/peter_cox/32/100910_2.png) [@Peter\_Cox](https://forum.cursor.com/u/Peter_Cox)\
**Post date:** [April 3, 2026, 4:25pm UTC](https://forum.cursor.com/t/what-features-do-you-wish-existed-but-dont/38319/4 "2026-04-03T16:25:21Z")

</div>

A chrome extension so I can speak to agents without having to leave Chrome. Am currently building something like this for myself