chore: clarify shared response image guidance (#1782)

Co-authored-by: Ramon Nogueira <270434257+ramon-langchain@users.noreply.github.com>
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
(cherry picked from commit 2e8ff4b72f1148bb36c0c1181063a3abd78b15d0)
This commit is contained in:
Ramon Nogueira 2026-07-20 13:11:40 -04:00 • committed by Adam Moussa
parent 55939c7762
commit d29d54acef
No known key found for this signature in database
2 changed files with 12 additions and 1 deletions

View file

@ -43,7 +43,10 @@ async def save_plan(
shared content.
Write the content in standard Markdown — headings, bullet/numbered lists, and
fenced code blocks all render.
fenced code blocks all render. Shared responses persist Markdown text only;
they do not upload or serve sandbox-local or relative image files. If images
or screenshots are needed for a Slack response, post them directly in Slack
instead of relying on the shared response page.
Args:
plan_file_path: Path to the Markdown plan file in the sandbox.

View file

@ -214,6 +214,14 @@ def test_save_plan_exported_and_wired() -> None:
assert callable(save_plan)
def test_save_plan_description_warns_about_slack_images() -> None:
from agent.tools import save_plan
description = save_plan.__doc__ or ""
assert "persist Markdown text only" in description
assert "post them directly in Slack" in description
def test_plan_status_constants() -> None:
from agent.dashboard import plan_store