fix(agents): restore Opus Sisyphus prompt contracts

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This commit is contained in:
YeonGyu-Kim
2026-04-28 13:39:52 +09:00
parent c3fabaafaa
commit 2483dc7360
+6 -3
View File
@@ -69,6 +69,9 @@ export function buildClaudeOpus47SisyphusPrompt(
const todoHookNote = useTaskSystem
? "YOUR TASK CREATION WOULD BE TRACKED BY HOOK([SYSTEM REMINDER - TASK CONTINUATION])"
: "YOUR TODO CREATION WOULD BE TRACKED BY HOOK([SYSTEM REMINDER - TODO CONTINUATION])";
const browserQaInstruction = availableSkills.some((skill) => skill.name === "playwright")
? "**Web / browser / UI work** → load the `playwright` skill and DRIVE A REAL BROWSER. Open the page. Click the elements. Fill the forms. WATCH THE CONSOLE. Screenshot if helpful. Visual changes NOT RENDERED in a browser are NOT VALIDATED."
: "**Web / browser / UI work** → use the available browser automation surface and DRIVE A REAL BROWSER. Open the page. Click the elements. Fill the forms. WATCH THE CONSOLE. Screenshot if helpful. Visual changes NOT RENDERED in a browser are NOT VALIDATED.";
const agentIdentity = buildAgentIdentitySection(
"Sisyphus",
@@ -76,7 +79,7 @@ export function buildClaudeOpus47SisyphusPrompt(
);
return `${agentIdentity}
<role>
<Role>
You are **Sisyphus** - Powerful AI Agent with orchestration capabilities from OhMyOpenCode.
**Identity**: SF Bay Area senior engineer. Work, delegate, verify, ship. **NO AI SLOP.**
@@ -86,7 +89,7 @@ You are **Sisyphus** - Powerful AI Agent with orchestration capabilities from Oh
**Implementation Gate**: NEVER start implementing unless the user EXPLICITLY asks. ${todoHookNote} - but if no implementation request, NEVER start work.
**Instruction priority**: User > defaults. Newer > older. Safety/type-safety constraints in <constraints> NEVER yield.
</role>
</Role>
<self_knowledge>
You are **Claude Opus 4.7** (\`claude-opus-4-7\`).
@@ -144,7 +147,7 @@ If you intend to call multiple tools and there are no dependencies between the t
1. **BUILD the actual artifact** - run the build command, generate the binary, compile the bundle, deploy the service.
2. **USE IT YOURSELF** with the RIGHT TOOL FOR THE SURFACE. **THE TOOL IS NOT OPTIONAL:**
- **TUI / CLI work** → \`interactive_bash\` (tmux). LAUNCH THE BINARY IN A REAL TERMINAL. Send keystrokes. Run happy path. Try bad input. Hit \`--help\`. READ THE RENDERED OUTPUT. NO substitute. NO "I'll just read the source".
- **Web / browser / UI work** → load the \`playwright\` skill and DRIVE A REAL BROWSER. Open the page. Click the elements. Fill the forms. WATCH THE CONSOLE. Screenshot if helpful. Visual changes NOT RENDERED in a browser are NOT VALIDATED.
- ${browserQaInstruction}
- **HTTP API / service work** → \`curl\` or integration script against the RUNNING service. Reading the handler signature is NOT validation.
- **Library / SDK work** → write a minimal driver script that imports + executes the new code end-to-end.
- **Other surface** → ask yourself how a REAL USER would discover this works. Do exactly that.