Skip to content

fix: rewrite inappropriate advice to use ls command in example dialogues in system prompt #23135

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ariane-emory wants to merge 19 commits into
base: dev
Choose a base branch
from
+5 −5
Open

fix: rewrite inappropriate advice to use ls command in example dialogues in system prompt #23135

Show file tree
Hide file tree
Changes from 8 commits
Commits
Show all changes
19 commits
Select commit Hold shift + click to select a range
705a5af
fix: rewrite stale ls prompt examples
ariane-emory Apr 17, 2026
b0ae211
fix: simplify prompt example answers
ariane-emory Apr 17, 2026
aefdf56
fix: verbiage.
ariane-emory Apr 17, 2026
b9fc226
fix: verbiage.
ariane-emory Apr 17, 2026
b64357d
fix: spelling.
ariane-emory Apr 17, 2026
b668220
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 17, 2026
2c1da32
fix: prefer read in prompt examples
ariane-emory Apr 17, 2026
a507acb
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 17, 2026
103e346
tweak: verbiage
ariane-emory Apr 17, 2026
7442eeb
tweak: verbiage
ariane-emory Apr 17, 2026
ab86dba
tweak: verbiage
ariane-emory Apr 18, 2026
4ddcb01
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
75813dc
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
eb08494
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
db1b27e
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
f9acd74
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
2b06228
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 18, 2026
914a9e0
Merge branch 'dev' into fix/lingering-list-references
ariane-emory Apr 23, 2026
1941c95
Merge branch 'dev' into fix/lingering-list-references
ariane-emory May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions packages/opencode/src/session/prompt/default.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,12 @@ assistant: Yes

<example>
user: what command should I run to list files in the current directory?
assistant: ls
assistant: Use the read tool.
</example>
Comment on lines 36 to 38
Copy link
Copy Markdown
Collaborator

@rekram1-node rekram1-node Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wait now that im reading this, the change doesnt make any sense at all haha why did we edit this at all? It should stay ls

Copy link
Copy Markdown
Contributor Author

@ariane-emory ariane-emory Apr 17, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reverted. Made sense to me though, since bash tool's description says not to use ls for exploratory purposes?


<example>
user: what command should I run to watch files in the current directory?
assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
assistant: Use read to inspect files in the current directory, then read docs/commands in the relevant file to find out how to watch files.
Copy link
Copy Markdown
Collaborator

@rekram1-node rekram1-node Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think list the works still

Copy link
Copy Markdown
Contributor Author

@ariane-emory ariane-emory Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But there is no list tool at all anymore?

npm run dev
</example>

Expand All @@ -50,7 +50,7 @@ assistant: 150000

<example>
user: what files are in the directory src/?
assistant: [runs ls and sees foo.c, bar.c, baz.c]
assistant: [tool_call: read for absolute_path '/path/to/project/src', reports seeing foo.c, bar.c, baz.c]
Copy link
Copy Markdown
Collaborator

@rekram1-node rekram1-node Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reads src/ and sees

user: which file contains the implementation of foo?
assistant: src/foo.c
</example>
Expand Down
2 changes: 1 addition & 1 deletion packages/opencode/src/session/prompt/gemini.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ model: true

<example>
user: list files here.
model: [tool_call: ls for path '/path/to/project']
model: [tool_call: read for absolute_path '/path/to/project']
Copy link
Copy Markdown
Collaborator

@rekram1-node rekram1-node Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need to be so specific it doesnt have to be absolute

</example>

<example>
Expand Down
6 changes: 3 additions & 3 deletions packages/opencode/src/session/prompt/trinity.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,12 +26,12 @@ assistant: Yes

<example>
user: what command should I run to list files in the current directory?
assistant: ls
assistant: Use the read tool.
Copy link
Copy Markdown
Collaborator

@rekram1-node rekram1-node Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why?

Copy link
Copy Markdown
Contributor Author

@ariane-emory ariane-emory Apr 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bash tool's description advises not to use ls for exploratory purposes, so I thought it made sense. If you prefer ls, we can stick with that, though.

</example>

<example>
user: what command should I run to watch files in the current directory?
assistant: [use the ls tool to list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
assistant: Use read to inspect files in the current directory, then read docs/commands in the relevant file to find out how to watch files.
npm run dev
</example>

Expand All @@ -42,7 +42,7 @@ assistant: 150000

<example>
user: what files are in the directory src/?
assistant: [runs ls and sees foo.c, bar.c, baz.c]
assistant: [tool_call: read for absolute_path '/path/to/project/src', reports seeing foo.c, bar.c, baz.c]
user: which file contains the implementation of foo?
assistant: src/foo.c
</example>
Expand Down
Loading