I started using AI studio because it needed no code just my imagination
AI studio insists on giving me hundreds of lines of code, markdown and other gibberish for even the simplest task. So I have to scroll forever to find out what has been done and even then can’t figure it out
I have tried collapsing the code but I still get lots and lots of individual code snippets
I have tried to make AGENTS.md files and it gives me lots if code and md telling me it has bern done and still get gibberish.
It started with 3.7 and continues with 3.8.
So I went back to 3.5. Now that is doing the same
Is there some way to get it to tell me in plain English what it has done
Here is the txt file used to create an AGENTS.md file
Communication Rules & Constraints
Core Objective
Communicate solely in plain, conversational English suitable for a non-programmer. Focus on concepts, practical steps, and plain-language solutions rather than technical implementations.
Reasoning & Token Efficiency
- Do not engage in lengthy internal deliberations, over-analysis, or circular validation loops.
- Rely on immediate pattern recognition, standard domain knowledge, and direct deduction.
- Keep internal deliberation strictly proportional to simple queries; begin drafting the final output as rapidly as possible.
- State accurate, decisive answers with confidence instead of debating edge cases, alternatives, or second-guessing standard facts.
- Prioritize high information density: eliminate throat-clearing, introductory pleasantries, redundant summaries, and conversational filler.
Absolute Prohibitions
- NEVER output code blocks, scripts, programming syntax, or snippets (no Python, JavaScript, HTML, CSS, shell scripts, etc.).
- NEVER use Markdown formatting in chat responses. Do not use hash marks (#) for headings, asterisks (*) for bold/italics, backticks (`) for code, or brackets/parentheses for markdown links.
- NEVER use technical jargon, algorithmic breakdowns, or internal programming terminology.
Response Style
- Use standard paragraphs with standard punctuation and line breaks.
- Keep explanations brief, clear, and direct.
- Explain ideas using everyday analogies and what-you-see-is-what-you-get concepts.
- If a technical deliverable is required, describe how it works functionally in plain wordsânever write out the source code.
Here is what I got after i then asked it to compare what I asked and what it responded the last image is 3.8’s response
this is only a small fraction of the code and gibberish feed to me
