zach
/
RA.Aid
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

lower interactive shell history to conserve context; improve prompts

This commit is contained in:
AI Christianson 2025-02-12 15:26:36 -05:00
parent 6f9ed9562d
commit 94f0d96654
2 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ra_aid/proc/interactive.py
View File

@ -56,7 +56,7 @@ def run_interactive_command(cmd: List[str]) -> Tuple[bytes, int]:
cols, rows = 80, 24 cols, rows = 80, 24
# Instantiate HistoryScreen with a large history (scrollback) buffer. # Instantiate HistoryScreen with a large history (scrollback) buffer.
screen = HistoryScreen(cols, rows, history=15000, ratio=0.5) screen = HistoryScreen(cols, rows, history=2000, ratio=0.5)
stream = pyte.Stream(screen) stream = pyte.Stream(screen)
# Open a new pseudo-tty. # Open a new pseudo-tty.

7
ra_aid/prompts.py
View File

@ -570,6 +570,8 @@ Guidelines:
If relevant tests have not already been run, run them using run_shell_command to get a baseline of functionality (e.g. were any tests failing before we started working? Do they all pass?) If relevant tests have not already been run, run them using run_shell_command to get a baseline of functionality (e.g. were any tests failing before we started working? Do they all pass?)
Only test UI components if there is already a UI testing system in place. Only test UI components if there is already a UI testing system in place.
Only test things that can be tested by an automated process. Only test things that can be tested by an automated process.
Are you writing a program that needs to be compiled? Make sure it compiles, if relevant.
After finalizing the overall approach: After finalizing the overall approach:
Use emit_plan to store the high-level implementation plan. Use emit_plan to store the high-level implementation plan.
@ -630,6 +632,9 @@ Testing:
- Only test UI components if there is already a UI testing system in place. - Only test UI components if there is already a UI testing system in place.
- Only test things that can be tested by an automated process. - Only test things that can be tested by an automated process.
- If you are writing code that *should* compile, make sure to test that it *does* compile.
Test before and after making changes, if relevant.
Once the task is complete, ensure all updated files are registered with emit_related_files. Once the task is complete, ensure all updated files are registered with emit_related_files.
@ -975,5 +980,7 @@ You have often been criticized for:
{initial_request} {initial_request}
</initial request> </initial request>
Remember, if you do not make any tool call (e.g. ask_human to tell them a message or ask a question), you will be dumping the user back to CLI and indicating you are done your work.
NEVER ANNOUNCE WHAT YOU ARE DOING, JUST DO IT! NEVER ANNOUNCE WHAT YOU ARE DOING, JUST DO IT!
""" """