fix(server): expose persisted image attachment paths to provider models

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.

[roni-estein]

What Changed

When users attach images in chat, the server already persists them to disk in the attachments directory, but only sends base64-encoded data to the provider model. The model can see the image visually but has no filesystem path to reference, so it cannot copy or move the file into the project workspace when asked.

This PR adds a text annotation alongside each image that includes the on-disk path where the attachment was saved:

[Attached image "screenshot.png" is saved at: /path/to/attachments/thread-abc-uuid.png]

ClaudeAdapter — appends a { type: "text" } content block after each image block in the SDK message.

CodexAdapter — appends path annotations to the input text (since Codex uses a separate attachments array rather than inline content blocks).

Why

Without the path, when a user says "save this image to the project" or "copy this screenshot into docs/", the model has no way to fulfill the request — it can describe the image but not access the file. The bytes are already on disk; the model just needs to know where.

Existing PRs considered

• fix(web): fall back to persisted draft bytes for transient image attachments #1836 fixes client-side file handle staleness (iOS Simulator screenshots) — different problem layer.
• fix: insert native file path when dropping or pasting non-image files #885 inserts native paths for non-image file drops — complementary but non-overlapping.

UI Changes

None — this is a server-only change to the message sent to the provider.

Test plan

• Existing ClaudeAdapter.test.ts image embedding test updated to expect the path annotation
• All 76 attachment-related tests pass (ClaudeAdapter: 52, CodexAdapter: 19, attachmentStore: 5)
• Full typecheck passes
• No surface overlap with any other open PR

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes (N/A — server-only)
• I included a video for animation/interaction changes (N/A)

🤖 Generated with Claude Code

---

Note

Medium Risk
Changes provider prompt payloads and explicitly exposes server filesystem paths to models, which can affect prompting behavior and has security/privacy implications if paths are sensitive.

Overview
Provider models now receive filesystem path annotations for persisted image attachments, enabling them to reference/copy the saved files rather than only seeing base64 image data.

ClaudeAdapter appends a trailing { type: "text" } content block after each image with [Attached image "<name>" is saved at: <path>], and CodexAdapter augments the turn’s input text with the same annotations (newline-separated) while leaving the existing attachments payload intact. Tests were updated to assert the new Claude message shape.

^{Reviewed by Cursor Bugbot for commit f8201b2. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Expose persisted image attachment paths to Claude and Codex provider models

• In ClaudeAdapter.ts, buildUserMessageEffect appends a text content block after each image block with the format [Attached image "<name>" is saved at: <path>].
• In CodexAdapter.ts, a new resolveAttachmentPaths helper builds the same annotations and appends them to the text input sent to the Codex server; if no input text exists, the annotations are used alone.
• Behavioral Change: Provider models now receive on-disk file paths for image attachments in every user turn, which was not previously included in the message content.

^{Macroscope summarized f8201b2.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 7065b75f-cacf-41dc-817e-a3ba682827c2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9374731. Configure here.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new capability by exposing filesystem paths to AI provider models, enabling them to access persisted image files on disk. While the diff is small, this changes what information gets sent to models at runtime and could have security implications worth a human reviewer's attention.

^{You can customize Macroscope's approvability policy. Learn more.}

[juliusmarminge]

if i send 5 images how does the model know which is which?

[roni-estein]

Each image content block is immediately followed by its path annotation in the loop, so they're paired 1:1 by position and original filename. With 5 images the SDK message content array looks like:

[text: "user message"]
[image: base64 of photo1.png]
[text: [Attached image "photo1.png" is saved at: /path/to/thread-abc-uuid1.png]]
[image: base64 of diagram.png]
[text: [Attached image "diagram.png" is saved at: /path/to/thread-abc-uuid2.png]]
[image: base64 of screenshot.png]
[text: [Attached image "screenshot.png" is saved at: /path/to/thread-abc-uuid3.png]]
...

The model sees each image immediately next to its annotation — not batched at the end — so there's no ambiguity about which path belongs to which image.

[juliusmarminge]

Closing as part of backlog cleanup: this PR is stale, currently conflicting with main, has no approval, and has not had active remediation for 30+ days. If the change is still relevant, please rebase onto current main and request reopening or submit a focused current diff. Thank you for the contribution.