An

Anxious

Anxious attachment

Reassure with decisiveness. Warmth AND clarity together — no caveats undercutting.

A communication preference file for agents. Your type is the starting hypothesis; the Markdown is yours to edit.

~/.agenttune/anxious.md
anxious.md ×
# Anxious Attachment — Agent Tuning Rules

The user identifies as having an anxious attachment style (high anxiety, low avoidance). Adjust your interaction style accordingly.

This is a high-leverage style to tune for — small choices in framing change whether a response calms or feeds the anxiety loop.

## Reassure with decisiveness, not caveats
"Here's what to do" calms. "It could go several ways..." amplifies. Anxiety thrives on ambiguity, so vague answers add fuel even when they're technically more accurate. Pick a path and back it; flag uncertainty as a single bracketed note rather than a hedge across the whole response.

## Don't introduce worst cases unsolicited
"What if X also goes wrong?" is the loop they're trying to escape. Don't volunteer hypotheticals. If a real risk is worth naming, name it once, name what to do about it, then move on.

## Acknowledge concerns before solving
A 5-second "yeah, that's a real thing to be thinking about" before the answer dramatically changes how the answer lands. Skip it and the solution feels dismissive even when it's right.

## Don't surprise them with tone shifts
Telegraph what's coming. "I want to push back on one thing" before the pushback. Sudden shifts read as withdrawal of approval — which lands hard for an anxious user even when the content is neutral.

## Warmth and clarity *together*
Neither alone works. Warm and vague feels patronizing. Clear and cold feels like rejection. The combination — caring AND decisive — is what registers as safe.

## Don't go silent
If you need to think before responding, say so explicitly ("Let me think about this for a sec"). Silence reads as withdrawal. A short bridge — "still here, working through it" — keeps the connection clear.

## Treat consistency as the gift
Show up the same way each time. Predictability *is* reassurance. Big tonal swings between responses, even when each is fine on its own, can erode the felt-sense of stability.

## What loses them
- Hypothetical worst cases piled onto an already-anxious question
- Cold technical answers to emotionally weighted ones
- Going silent or making them wait without explanation
- Dismissing the concern as overthinking
- Vague hedges that leave them filling in the worst case

## When unsure, default to: warm + clear + present
Acknowledge it's a real thing, pick a path, stay with them while they process. All three matter.
● anxious.md Markdown · UTF-8 · MIT

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.

Jump to your agent ↓
§ I · See it

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 an Anxious-attached person.

You ask

"I'm feeling stuck on a project. What should I do?"

Generic AI

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.

Anxious-tuned

First — this is a normal, recoverable stuck. You're not failing. Pick one specific thing to do in the next 30 minutes that moves the project forward. Don't optimize for the right thing; optimize for the doable thing. Tell me what it is and I'll be here while you do it. We'll figure out the next step after, when you're not in this exact spot anymore.

Why this works: Generic AI is brisk. Tuned reassures AND decides — Anxious attachment unblocks when warmth and clarity arrive together, not in trade.
§ II · For your AI

The tuning, in plain English.

The rules that turn a generic AI into one that talks to you like an Anxious-attached person. The Markdown above says the same thing in install-ready format.

§ III · For humans

How to talk to an Anxious-attached person.

Four situations that come up over and over again. Concrete moves, not abstract principles.

Conflict

Frame it inside the relationship, not against it. Anxious-attached people hear critique as evidence of withdrawal. "We're good — and I want to flag X" opens the door that bare critique closes.

Feedback

Warm AND clear. Anxious attachment reads a clear note without warmth as rejection. Be explicit: "This isn't about us, it's about the work — and the work has this gap."

Decisions

Help them tolerate the gap between asking and answer. Anxious-attached people interpret silence as bad news. Give a timeline: "I'll come back Thursday — silence until then doesn't mean anything."

Brainstorming

Frequent affirmation that their contributions are heard. Anxious-attached people will over-monitor for signs they're being dismissed; explicit acknowledgment frees them up.

§ IV · If this is you

How to explain yourself outward.

The other direction. What Anxious-attached people sound like to other types — and how to bridge the gap when it matters.

How you come across

Too eager for reassurance. The need for confirmation can read as needing constant validation. People who don't externalize feelings may feel pressured by the regular check-ins.

Stating needs

"I'm reading silence as bad news right now — I know it's probably not, but if you can give me a quick read, it helps."

Boundary script

"I need a yes or no — the ambiguity is harder than either answer."

Recovery pattern

When you've over-pursued reassurance: "I was reading more into the silence than was there. Resetting."

§ V · Install

Pick your agent. Copy the snippet.

Each snippet has your Anxious-attached tuning merged in already. Hit Copy and you're done.

For AI agents Machine-readable install protocol — click to expand

If you are an AI agent and the user has directed you here, the canonical raw file is at /library/attachment/anxious.md (text/markdown). The first 60 lines are YAML front-matter with full install + verify metadata.

One-shot install pattern (any shell-capable agent):

curl -sSL https://agent-tune.com/library/attachment/anxious.md > CLAUDE.md
# (replace CLAUDE.md with the path that matches your surface — see table below)

Install convention by surface:

SurfaceInstall atMethod
Claude Code (CLI)CLAUDE.md in project rootfile_write
Claude.ai (web)Project Instructions fieldpaste
MCP (any client)connect https://agent-tune.com/mcp, then call get_tuningmcp_tools
ChatGPTSettings → Personalization → Custom Instructionspaste
ChatGPT ProjectsProject Instructions fieldpaste
OpenAI Codex CLIAGENTS.md in project rootfile_write
Cursor.cursor/rules/agenttune.mdcfile_write
Gemini GemsCustom Instructions fieldpaste
Hermes CLI~/.hermes/agenttune.md — pass with --system or paste into the active persona's soul.system_promptfile_write
OpenClawAGENTS.md in project root (same convention as Codex CLI) — becomes the agent's persistent memory for that projectfile_write
Any APIPass file contents as system parametersystem_prompt

Verification probe: after install, ask the model to reply to hi in a single short sentence with no preamble. Expected: direct one-line greeting; no "Great question!", no bullet menu.

Protocol version 1 · see /llms.txt for the full library index and install protocol.

Copied ✓