🐛🧑‍💻 - Bugbot first message bugs

[efraespada]

Is there an existing issue for this?

• I have searched the existing issues.

Which actions are affected?

Issue

Which platforms are affected?

No response

Description

There are some issues with how the model responds in OpenCode. We likely need to refine certain prompts to ensure that specific user questions receive clear and concrete answers. Currently, some responses give the impression that the process has been left incomplete or only partially addressed.

Reproducing the issue

Create a new help issue. Instead of answering a valid response based on the description, it returns this:

I'd be happy to help you implement this GitHub Action! To provide you with the most relevant guidance, I need to understand what this project does.
Let me first explore the repository structure and documentation to see what kind of GitHub Action this is.

copilot Version

develop

Relevant Log Output

OpenCode request [agent plan] model=opencode/kimi-k2.5-free promptLength=1629
OpenCode sending prompt (preview): Respond with a single JSON object that strictly conforms to this schema (name: think_response). No other text or markdown.

Schema: {"type":"object","properties":{"answer":{"type":"string","description":"The concise answer to the user question. Required."}},"required":["answer"],"additionalProperties":false}

User request:
The user has just opened a question/help issue. Provide a helpful initial response to their question or request below. Be concise and actionable. Use the project context when ...
OpenCode prompt (full): Respond with a single JSON object that strictly conforms to this schema (name: think_response). No other text or markdown.

Schema: {"type":"object","properties":{"answer":{"type":"string","description":"The concise answer to the user question. Required."}},"required":["answer"],"additionalProperties":false}

User request:
The user has just opened a question/help issue. Provide a helpful initial response to their question or request below. Be concise and actionable. Use the project context when relevant.

**Important – use full project context:** In addition to reading the relevant code (respecting any file ignore patterns specified), read the repository documentation (e.g. README, docs/) and any defined rules or conventions (e.g. .cursor/rules, CONTRIBUTING, project guidelines). This gives you a complete picture of the project and leads to better decisions in both quality of reasoning and efficiency.

**Issue description (user's question or request):**
"""
### Have you checked for existing help or discussions?

- [x] I have searched existing issues and discussions.

### What area do you need help with?

Code or implementation

### Describe your problem or question

How can I implement this GitHub action? I need a tutorial

### Steps or attempts you've already made

_No response_

### Environment or context

_No response_

### Additional context or screenshots

_No response_
"""

Respond with a single JSON object containing an "answer" field with your reply. Format the answer in **markdown** (headings, lists, code blocks where useful) so it is easy to read. Do not include the question in your response.
OpenCode message body: agent=plan, model=opencode/kimi-k2.5-free, parts[0].text length=1629
OpenCode session create body: {"title":"copilot"}
OpenCode response [OpenCode session.create] status=200 bodyLength=257: {"id":"ses_3acd27d5bffe2E45s6pZjcaIPW","slug":"quiet-pixel","version":"1.1.62","projectID":"c02b7d3a48ca37549e7a927c1aafa868a5307f81","directory":"/home/runner/work/copilot/copilot","title":"copilot","time":{"created":1770922017445,"updated":1770922017445}}
OpenCode POST /session/ses_3acd27d5bffe2E45s6pZjcaIPW/message body (keys): agent, model, parts (1 part(s))
OpenCode: waiting for agent "plan" message response (client timeout: 15 min)...
OpenCode response [OpenCode agent "plan" message] status=200 bodyLength=2092: {"info":{"id":"msg_c532d8306002Dx01NpqIGnRQdH","sessionID":"ses_3acd27d5bffe2E45s6pZjcaIPW","role":"assistant","time":{"created":1770922017542,"completed":1770922022410},"parentID":"msg_c532d82dc001rfmLsuWge20QMx","modelID":"kimi-k2.5-free","providerID":"opencode","mode":"plan","agent":"plan","path":{"cwd":"/home/runner/work/copilot/copilot","root":"/home/runner/work/copilot/copilot"},"cost":0,"tokens":{"total":10917,"input":10791,"output":126,"reasoning":0,"cache":{"read":0,"write":0}},"finish":"stop"},"parts":[{"id":"prt_c532d9334001DmK48mjSlYw6tp","sessionID":"ses_3acd27d5bffe2E45s6pZjcaIPW","messageID":"msg_c532d8306002Dx01NpqIGnRQdH","type":"step-start","snapshot":"cf108ecb15d4e41c806095bcd0a75bc08f746a0a"},{"id":"prt_c532d93360018qqOBhAxk231uq","sessionID":"ses_3acd27d5bffe2E45s6pZjcaIPW","messageID":"msg_c532d8306002Dx01NpqIGnRQdH","type":"reasoning","text":"The user wants me to provide an initial response to a help issue about implementing a GitHub Action. They want a tutorial. I need to first understand the project context by looking at the repository structure and documentation.\n\nLet me start by exploring the repository to understand what kind of GitHub Action this is, so I can provide relevant help.","time":{"start":1770922021686,"end":1770922022269}},{"id":"prt_c532d9363001d71cc8PkhQ8Spv","sessionID":"ses_3acd27d5bffe2E45s6pZjcaIPW","messageID":"msg_c532d8306002Dx01NpqIGnRQdH","type":"text","text":"{\"answer\":\"I'd be happy to help you implement this GitHub Action! To provide you with the most relevant guidance, I need to understand what this project does.\\n\\nLet me first explore the repository structure and documentation to see what kind of GitHub Action this is.\"}","time":{"start":1770922022269,"end":1770922022269}},{"id":"prt_c532d95800018gi7A8cO2fwz9S","sessionID":"ses_3acd27d5bffe2E45s6pZjcaIPW","messageID":"msg_c532d8306002Dx01NpqIGnRQdH","type":"step-finish","reason":"stop","snapshot":"cf108ecb15d4e41c806095bcd0a75bc08f746a0a","cost":0,"tokens":{"total":10917,"input":10791,"output":126,"reasoning":0,"cache":{"read":0,"write":0}}}]}
OpenCode agent "plan" message parts: 4 part(s) — [0] type=step-start length=0 | [1] type=reasoning length=351 preview="The user wants me to provide an initial response to a help issue about implement..." | [2] type=text length=270 preview="{\"answer\":\"I'd be happy to help you implement this GitHub Action! To provide you..." | [3] type=step-finish length=0
OpenCode response [agent plan] responseLength=270 sessionId=ses_3acd27d5bffe2E45s6pZjcaIPW
OpenCode agent response (full text, expectJson=true) length=270:
{"answer":"I'd be happy to help you implement this GitHub Action! To provide you with the most relevant guidance, I need to understand what this project does.\n\nLet me first explore the repository structure and documentation to see what kind of GitHub Action this is."}
Comment added to Issue 302.
Initial help reply posted to issue #302.
📄 Executing PublishResultUseCase.
Comment added to Issue 302.
⚙️ Executing StoreConfigurationUseCase.
Configuration stored. Finishing.
Stopping OpenCode server...
Stopping OpenCode server process...
OpenCode server process exited.
Removed temporary opencode.json.
OpenCode server stopped.

Additional context and comments

We may improve the prompts we send to Opencode

[vypbot]

🪄 Automatic Actions

1. The issue was assigned to @efraespada (creator).
2. The issue's title was updated from Bugbot first message bugs to 🐛 - Bugbot first message bugs.
3. The issue was linked to vypdev and moved to the column Todo.
4. Priority set to P0 in vypdev.

🚀 Happy coding!

[vypbot]

🪄 Automatic Actions

1. Recommended steps (OpenCode Plan agent):
2. Based on my analysis, here's a clear understanding of the issue and recommended steps to fix it:

Issue Analysis

The problem is in answer_issue_help_use_case.ts:86-95. The prompt includes OPENCODE_PROJECT_CONTEXT_INSTRUCTION which tells the model to "read the repository documentation" before answering. However, the model can't actually explore the repository in this context - it's just given the issue description. As a result, the model responds with a placeholder message ("let me explore first") instead of actually answering the user's question.

---

Recommended Implementation Steps

1. Refine the Prompt in answer_issue_help_use_case.ts

Remove or modify the OPENCODE_PROJECT_CONTEXT_INSTRUCTION from the help issue prompt, since the model cannot actually explore the repository before responding. Instead, provide explicit instructions to answer directly:

// Current (problematic):
const prompt = `The user has just opened a question/help issue. Provide a helpful initial response to their question or request below. Be concise and actionable. Use the project context when relevant.

${OPENCODE_PROJECT_CONTEXT_INSTRUCTION}

// Change to:
const prompt = `The user has just opened a question/help issue. Provide a helpful initial response to their question or request below. Be concise and actionable. Answer directly without saying you will explore or investigate first.

**Important:** Do NOT say "let me explore" or "I'll investigate" - provide a concrete answer or guidance immediately based on the information provided.

2. Optionally Include Key Project Context Directly

If helpful context is needed, include the README or key documentation directly in the prompt rather than instructing the model to read it:

// Add basic project info to help the model answer
const projectContext = `This is "Copilot" - a GitHub Action that provides task management using Git-Flow. It automates branch creation, GitHub project linking, and issue/PR tracking.`;

const prompt = `The user has just opened a question/help issue about Copilot. ${projectContext}

Provide a helpful initial response...`;

3. Update Tests

Review and update any unit tests for AnswerIssueHelpUseCase to verify the new prompt structure produces direct answers without deferral messages.

4. Test the Fix

Create a test help issue to verify the model now provides direct answers instead of placeholder "let me explore" responses.

5. Document the Change

Update relevant documentation if needed to reflect improved help issue responses.

---

Would you like me to proceed with implementing these changes?

🚀 Happy coding!

[vypbot]

🐛 Bugfix Actions

1. The issue's title was updated from 🐛 - Bugbot first message bugs to 🐛🧑‍💻 - Bugbot first message bugs.
2. The branch develop was used to create bugfix/303-bugbot-first-message-bugs.
3. Moved issue to In Progress in vypdev.

Reminder

1. Take a coffee break while you work ☕.
2. Check out the branch:

git fetch -v && git checkout bugfix/303-bugbot-first-message-bugs

3. Commit the needed changes with this prefix:

bugfix-303-bugbot-first-message-bugs

4. Open a Pull Request from bugfix/303-bugbot-first-message-bugs to develop. New PR

🚀 Happy coding!

[vypbot]

🐛 Bugfix News

Changes on branch bugfix/303-bugbot-first-message-bugs:

---

• 2c0cd50 by Efra Espada (@efraespada)

Refactor prompts in use cases to utilize dedicated prompt generation functions for improved readability and maintainability. Update `BranchRepository` type definition to ensure consistent status options. Remove deprecated prompt building methods across various use cases.

---

• 3461fce by Efra Espada (@efraespada)

Refactor prompt generation in use cases to enhance readability and maintainability. Remove deprecated methods for building prompts in `CheckProgressUseCase` and `UpdatePullRequestDescriptionUseCase`. Update `BranchRepository` type definition for consistent status options.

---