# Different hook behavior in regards to CLI vs MCP usage

**URL:** <https://forum.cursor.com/t/different-hook-behavior-in-regards-to-cli-vs-mcp-usage/158620>\
**Category:** Bug Reports\
**Tags:** mcp, agents-window, hooks\
**Created:** [April 21, 2026, 10:14am UTC](https://forum.cursor.com/t/different-hook-behavior-in-regards-to-cli-vs-mcp-usage/158620 "2026-04-21T10:14:56Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [April 21, 2026, 11:09am UTC](https://forum.cursor.com/t/different-hook-behavior-in-regards-to-cli-vs-mcp-usage/158620/7 "2026-04-21T11:09:49Z")

</div>

Hey, thanks for the detailed analysis. The comparison between Agent Chat and Agents View is a really useful data point.

This is a confirmed bug that affects `sessionStart` hook `additional_context` injection.

This was also reported in [this thread](https://forum.cursor.com/t/sessionstart-hook-additional-context-is-never-injected-into-agents-initial-system-context/158452), where our team confirmed the root cause and has filed an internal bug. No ETA on a fix yet, but the timing angle from your report (showing it’s worse in one view than the other) will help scope the fix.

Unfortunately, there’s no workaround right now. The `env` field from the same hook works because it goes through a separate storage path, but it doesn’t cover the `additional_context` use case. If any of your injected content is fairly static, duplicating it into a [`.cursor/rules`](https://cursor.com/docs/context/rules) file is a partial fallback, though I know that doesn’t cover your dynamic CLI reference setup.

I’ll update this thread when the fix ships.

---

_[View the full topic](https://forum.cursor.com/t/different-hook-behavior-in-regards-to-cli-vs-mcp-usage/158620)._