feat: prepend org submodule push-to-main note to sandbox prompts

[sweetmantech]

Summary

• Adds a SANDBOX_PROMPT_NOTE constant that gets prepended to every prompt sent to the sandbox
• Instructs the sandbox agent to always commit and push changes in the orgs/ directory directly to main so they are preserved and shared across sessions
• Ensures org submodule changes aren't lost when sandboxes are recycled or snapshots are restored

Test plan

• New test: verifies SANDBOX_PROMPT_NOTE is prepended to user prompts before passing to promptSandboxStreaming
• New test: verifies SANDBOX_PROMPT_NOTE is a non-empty string containing expected keywords (push, main, orgs)
• Updated existing test: prompt assertion now expects the note prefix
• All 9 tests pass
• Lint clean on changed files

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Enhanced internal prompt handling in the chat system to ensure improved consistency and reliability when processing user inputs in the sandbox environment.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
recoup-api	Ready	Preview	Feb 28, 2026 1:40pm

[coderabbitai]

📝 Walkthrough

Walkthrough

Introduces a new exported SANDBOX_PROMPT_NOTE constant that augments prompts before sandbox execution. The augmentation happens at runtime by constructing an augmented prompt that combines the constant with the original prompt, applied across both streaming and initialization paths.

Changes

Cohort / File(s)	Summary
Sandbox Prompt Enhancement lib/chat/tools/createPromptSandboxStreamingTool.ts	Adds SANDBOX_PROMPT_NOTE constant export and modifies prompt construction logic to prepend this note to all sandbox-bound prompts via augmentedPrompt variable.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• feat: stream prompt_sandbox output for faster first token #246: Introduces the initial prompt construction mechanism in the sandbox tool that this change directly extends by adding prompt note augmentation.

Poem

🚀 A constant note takes flight,
Prefixing wisdom to each prompt,
The sandbox whispers clear and bright—
One small augment, thoughtfully wrought! ✨

🚥 Pre-merge checks | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Solid & Clean Code	⚠️ Warning	File exports two entities (constant and function) violating SRP; guidelines require one exported function per file in lib/**/*.ts.	Remove export from SANDBOX_PROMPT_NOTE to keep it file-local only, maintaining internal use while adhering to SRP.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sweetmantech/myc-4362-prompt_sandbox-tool-add-hard-coded-note-to-push-any-changes

---

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.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@lib/chat/tools/createPromptSandboxStreamingTool.ts`:
- Around line 5-7: The SANDBOX_PROMPT_NOTE is insufficient as enforcement;
update the sandbox execution logic in createPromptSandboxStreamingTool to add a
post-run validation/hook that programmatically inspects any git changes produced
by the tool (diff or staged/committed files), detects modifications under the
orgs/ directory, and enforces they were committed/pushed to the main branch — if
not, fail the run (throw/error) and log a clear message; implement this by
adding a postRunValidation function in createPromptSandboxStreamingTool that
checks git status/diff for "orgs/" paths, verifies git rev-parse --abbrev-ref
HEAD === "main" (or that commits affecting orgs/ target main), and either
auto-fixes by switching/committing to main or rejects the sandbox output.
- Around line 5-7: The file currently exports SANDBOX_PROMPT_NOTE alongside the
main exported function (e.g., createPromptSandboxStreamingTool); keep this file
to a single exported function by making SANDBOX_PROMPT_NOTE file-local (remove
the export) or move it into a dedicated constants module and import it; update
references in createPromptSandboxStreamingTool to use the local constant or the
imported constant accordingly so only createPromptSandboxStreamingTool remains
exported from this file.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 842bef6 and bb15a91.

⛔ Files ignored due to path filters (1)

• lib/chat/tools/__tests__/createPromptSandboxStreamingTool.test.ts is excluded by !**/*.test.*, !**/__tests__/** and included by lib/**

📒 Files selected for processing (1)

• lib/chat/tools/createPromptSandboxStreamingTool.ts

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Do not rely on prompt text as the only enforcement for orgs/ push-to-main policy.

This is a reliability gap: the model can ignore or deprioritize the note. For critical persistence behavior, enforce it in sandbox execution logic (e.g., post-run validation/hook) rather than instruction text alone.

Also applies to: 52-57

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@lib/chat/tools/createPromptSandboxStreamingTool.ts` around lines 5 - 7, The
SANDBOX_PROMPT_NOTE is insufficient as enforcement; update the sandbox execution
logic in createPromptSandboxStreamingTool to add a post-run validation/hook that
programmatically inspects any git changes produced by the tool (diff or
staged/committed files), detects modifications under the orgs/ directory, and
enforces they were committed/pushed to the main branch — if not, fail the run
(throw/error) and log a clear message; implement this by adding a
postRunValidation function in createPromptSandboxStreamingTool that checks git
status/diff for "orgs/" paths, verifies git rev-parse --abbrev-ref HEAD ===
"main" (or that commits affecting orgs/ target main), and either auto-fixes by
switching/committing to main or rejects the sandbox output.

---

🛠️ Refactor suggestion | 🟠 Major

Keep this file to a single exported function.

SANDBOX_PROMPT_NOTE introduces a second export in a lib/**/*.ts file. Make it file-local here, or move it to a dedicated constants module and import it.

♻️ Minimal local fix

-export const SANDBOX_PROMPT_NOTE =+const SANDBOX_PROMPT_NOTE =
"IMPORTANT: When you make changes to any files inside the orgs/ directory, " +
"always commit and push those changes directly to main so they are preserved and shared across sessions.";

As per coding guidelines, lib/**/*.ts: "Apply Single Responsibility Principle (SRP): one exported function per file; each file should do one thing well".

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	exportconstSANDBOX_PROMPT_NOTE=
	"IMPORTANT: When you make changes to any files inside the orgs/ directory, "+
	"always commit and push those changes directly to main so they are preserved and shared across sessions.";
	constSANDBOX_PROMPT_NOTE=
	"IMPORTANT: When you make changes to any files inside the orgs/ directory, "+
	"always commit and push those changes directly to main so they are preserved and shared across sessions.";

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@lib/chat/tools/createPromptSandboxStreamingTool.ts` around lines 5 - 7, The
file currently exports SANDBOX_PROMPT_NOTE alongside the main exported function
(e.g., createPromptSandboxStreamingTool); keep this file to a single exported
function by making SANDBOX_PROMPT_NOTE file-local (remove the export) or move it
into a dedicated constants module and import it; update references in
createPromptSandboxStreamingTool to use the local constant or the imported
constant accordingly so only createPromptSandboxStreamingTool remains exported
from this file.