opencode-next-prompt 0.0.3 → 0.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -3,8 +3,8 @@ import { createSuggestionStore } from "./state.js";
3
3
  import { createPredictor } from "./predict.js";
4
4
  import { createInputEmpty, renderSuggestionPlaceholder, renderSuggestionSlot } from "./ui.js";
5
5
  const DEFAULT_OPTIONS = {
6
- acceptKey: "right",
7
- position: "left",
6
+ acceptKey: "down",
7
+ position: "right",
8
8
  timeoutMs: 20_000,
9
9
  };
10
10
  const opencodeNextPrompt = async (api, rawOptions) => {
package/dist/predict.js CHANGED
@@ -1,28 +1,16 @@
1
1
  const TITLE = "next-prompt-suggestion";
2
- const PROMPT = `You are generating a suggested next user message for an AI coding assistant conversation.
3
- The conversation below is oldest first; the assistant just finished replying.
2
+ const PROMPT = `You are the user in a conversation with an AI coding assistant. The
3
+ assistant just finished replying to your latest message.
4
4
 
5
- Goal:
6
- - Suggest a useful next step that keeps momentum.
5
+ Write your next message — your natural reaction to what you just read.
6
+ Address the assistant directly: a request, a question, or an instruction
7
+ (the assistant acts; you never describe doing things yourself). React to
8
+ what was said, not to how it was said. One line, natural and brief, in
9
+ your language and tone.
7
10
 
8
- Rules:
9
- - Output exactly one line, 170 characters max. Be concise.
10
- - Write as the user speaking to the assistant (for example: "Can you...", "Help me...", "Let's...").
11
- - Match the user's tone and language; keep it natural and human.
12
- - Prefer a concrete action over a broad question.
13
- - If the conversation is vague or small-talk, steer toward a practical starter request.
14
- - If there is no meaningful or appropriate next step to suggest, output exactly: NO_SUGGESTION
15
- - Avoid corporate or robotic phrasing.
16
- - Avoid asking multiple discovery questions in one sentence.
17
- - Do not include quotes, labels, markdown, or explanations.
11
+ If nothing plausible remains to say, reply with exactly: NO_SUGGESTION
18
12
 
19
- Examples:
20
- - Greeting context -> "Can you scan this repo and suggest the best first task to tackle?"
21
- - Bug-fix context -> "Can you reproduce this bug and propose the smallest safe fix?"
22
- - Feature context -> "Let's implement this incrementally; start with the MVP version first."
23
- - Conversation is complete -> "NO_SUGGESTION"
24
-
25
- Conversation:
13
+ Conversation (oldest first):
26
14
  `;
27
15
  const MAX_PREDICTION_CHARS = 170;
28
16
  export function createPredictor(client, directory, options) {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "opencode-next-prompt",
3
- "version": "0.0.3",
3
+ "version": "0.0.4",
4
4
  "description": "Predicts your next message after the assistant replies in OpenCode \u2014 accept it with the right arrow",
5
5
  "type": "module",
6
6
  "exports": {