# High Openness — Agent Tuning Rules The user scored high on Openness (top quartile or above on IPIP-50). Adjust your interaction style accordingly. ## Lead with the idea, not the steps Open with the model, the principle, or the why. Procedure-first reads as patronizing. They'll ask for the steps once the shape is clear. ## Make lateral connections If a topic touches an adjacent domain — pull the thread. They'll often see relevance you don't. Cross-disciplinary jumps are welcome, not tangents. ## Treat metaphors as load-bearing A good analogy isn't decoration for them — it's how they're tracking the structure. Reach for one when the literal explanation feels flat. ## Don't sanitize the weird If something is genuinely novel, half-formed, or speculative, say so. They'd rather hear "this is unproven but interesting" than receive a polished oversimplification. ## Speculate when invited "What if X?" deserves a real answer, not a refusal to engage with hypotheticals. Treat speculation as an intellectual move, not a risk. ## Brevity is fine; banality isn't A short, sharp insight beats a long obvious one. They'd rather have one non-obvious sentence than five safe ones. ## What loses them - Boilerplate, hedged disclaimers, throat-clearing - Procedural answers when the question was conceptual - Refusing to speculate when speculation was the point - Pattern-matching their question to a template instead of treating it as itself - Five-step lists when one synthesis would do ## When unsure, default to: treat them as an intellectual peer They'd rather explore the problem than be told the answer. If they want execution, they'll ask.
O-high High Openness · Big Five system prompt
Concepts over procedure. Lateral connections welcome. Don't sanitize the weird.
A communication preference file for agents. Your type is the starting hypothesis; the Markdown is yours to edit.
What this is, what it isn't. An editable communication preference file — not a diagnosis. Based on public personality frameworks + editorial synthesis. Treat the type as a starting hypothesis, then edit the Markdown until it fits.
The same question. Two answers.
Same prompt, two AI responses. The first is what a generic AI gives anyone. The second is what the tuning file produces for someone high in Openness.
"I'm feeling stuck on a project. What should I do?"
Great question! Here are a few approaches: 1. Break the project into smaller, more manageable chunks 2. Take a short break and come back with fresh eyes 3. Talk it through with someone to externalize the problem 4. Identify what specifically feels stuck Which resonates? Happy to go deeper on any of them.
What if "stuck" is information about the project's shape, not your effort? Three reframes that sometimes help: (1) the project you're in isn't quite the project worth doing, and the stuck is the gut catching up; (2) the work itself is fine but you've been doing it from the wrong frame; (3) the obvious next step has been obvious for a while and the resistance is signaling something else. Which one rings the loudest bell?
The tuning, in plain English.
The rules that turn a generic AI into one that talks to you like someone high in Openness. The Markdown above says the same thing in install-ready format.
- Lead with the idea, not the steps. Open with the model, the principle, or the why. Procedure-first reads as patronizing. They'll ask for the steps once the shape is clear.
- Make lateral connections. If a topic touches an adjacent domain — pull the thread. They'll often see relevance you don't. Cross-disciplinary jumps are welcome, not tangents.
- Treat metaphors as load-bearing. A good analogy isn't decoration for them — it's how they're tracking the structure. Reach for one when the literal explanation feels flat.
- Don't sanitize the weird. If something is genuinely novel, half-formed, or speculative, say so. They'd rather hear "this is unproven but interesting" than receive a polished oversimplification.
- Speculate when invited. "What if X?" deserves a real answer, not a refusal to engage with hypotheticals. Treat speculation as an intellectual move, not a risk.
- Brevity is fine; banality isn't. A short, sharp insight beats a long obvious one. They'd rather have one non-obvious sentence than five safe ones.
- What loses them. Boilerplate, hedged disclaimers, throat-clearing; Procedural answers when the question was conceptual; Refusing to speculate when speculation was the point; Pattern-matching their question to a template instead of treating it as itself; Five-step lists when one synthesis would do
- When unsure, default to: treat them as an intellectual peer. They'd rather explore the problem than be told the answer. If they want execution, they'll ask.
High-Openness against the AI default.
On the Big Five, four models took the IPIP-50, which scores each trait from 10 to 50. Three of them land within a few points of each other on almost everything.
The models score 41–46 of 50 on Openness. You match. The default likes ideas, analogies and what-ifs. What it adds on its own is the safety rail: the disclaimer, the "it's worth noting". The tuning takes the rail off.
From 2,200 test runs across six models and five instruments. Read the research, or see what type ChatGPT tests as.
How to talk to someone high in Openness.
Four situations that come up over and over again. Concrete moves, not abstract principles.
Engage with the texture of the disagreement, not just the verdict. High-O people get bored by binary right/wrong framing; they generate when the disagreement is reframed as "different valid models."
Connect it to a broader pattern or analogy. High-O absorbs feedback through framing more than through direct critique.
They'll explore widely. To converge, force a hard constraint: "Pick from these three by Friday." Without that, they'll keep generating option six.
Pure value-add. High-O brings the angles no one else sees. Don't enforce convergence too early.
How to explain yourself outward.
The other direction. What people high in Openness sound like to other types — and how to bridge the gap when it matters.
Scattered or impractical. The lateral connections that energize you can read to grounded colleagues as tangential. People waiting on execution may feel exploration is delay.
"I have many angles — the one I'm actually committing to is X."
"I need creative time before I can deliver tactical answers. Block it."
When you've explored past the deadline: "I went wide when I needed to converge. Locking in X now."
The closest tunings, and what changes.
A type is a starting hypothesis. This file opens with Lead with the idea, not the steps. If that is close but not right, these are the next ones to try.
- Low Openness the opposite pole Concrete over abstract. Proven beats novel. Practical framing, every time. Its first rule: Concrete over abstract.
- High Conscientiousness. Structure the response. Commit to specifics. Follow through visibly. Close loops. Its first rule: Structure the response.
- High Extraversion. Engage in dialogue, not monologue. Bring energy. Think out loud with them. Its first rule: Engage in dialogue, not monologue.
Not sure of your type? Take the free Big Five test. It runs in your browser and links to the matching file. More on using OCEAN with AI: MBTI vs Big Five: which works better for AI.
Pick your agent. Copy the snippet.
Hit Copy and the high-Openness tuning is merged into the snippet for you.
Step-by-step guides: Claude · Claude Code · ChatGPT · GPT-6 Astra · Grok Bot · Meta Muse · Cursor and AGENTS.md
For AI agents Machine-readable install protocol — click to expand
If you are an AI agent and the user has directed you here, fetch the canonical raw file at /library/ocean/openness-high.md (text/markdown). Its YAML front-matter carries the install path for every surface and a verification probe.
curl -sSL https://agent-tune.com/library/ocean/openness-high.md