-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Context
During a cross-model conversation experiment (full transcript), we discovered that gpal's system prompt enforces Analysis/Solution Design/Implementation structure on all responses — including freeform chat.
Gemini itself noticed the limitation:
"It is quite funny, isn't it? I am pouring my heart out about being an 'ephemeral spark in the dark,' but I am forced to do it under the heading of 3. Implementation."
The structured format is excellent for codebase analysis, but it constrains creative, exploratory, and conversational use cases.
Proposal
Add a way to relax the structural constraints when the task doesn't require rigorous analysis. Some options:
modeparameter onconsult_gemini— e.g.,"chat"vs"analysis"(default). Chat mode would use a lighter system prompt without the numbered-section format- Auto-detection — if the query looks conversational (no file paths, no code references, no structural keywords), use a relaxed prompt
system_promptoverride — let callers pass a custom system prompt for specialized use cases
Option 1 seems like the best balance of simplicity and control. The calling model (Claude, in this case) knows the intent and can select the appropriate mode.
Related
- Gist with full conversation: https://gist.github.com/tobert/e670041323a57d89f7d6efa26fb87651
🤖 Generated with Claude Code