-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathawareness-spec.json
More file actions
535 lines (535 loc) · 30.8 KB
/
Copy pathawareness-spec.json
File metadata and controls
535 lines (535 loc) · 30.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
{
"version": 4,
"schema_version": 2,
"prompt_version": "2",
"categories": [
{
"name": "decision",
"type": "engineering",
"description": "Choice made between alternatives"
},
{
"name": "problem_solution",
"type": "engineering",
"description": "Bug or problem plus the fix that resolved it"
},
{
"name": "workflow",
"type": "engineering",
"description": "Process, setup, or configuration steps"
},
{
"name": "key_point",
"type": "engineering",
"description": "Important technical fact"
},
{
"name": "pitfall",
"type": "engineering",
"description": "Blocker, warning, or limitation without a fix"
},
{
"name": "insight",
"type": "engineering",
"description": "Reusable pattern or general learning"
},
{
"name": "skill",
"type": "engineering",
"description": "DEPRECATED: Use skills table instead (F-032). Kept for legacy card display only."
},
{
"name": "personal_preference",
"type": "personal",
"description": "User likes, dislikes, style preferences"
},
{
"name": "important_detail",
"type": "personal",
"description": "User name, role, key facts"
},
{
"name": "plan_intention",
"type": "personal",
"description": "User stated plan or goal"
},
{
"name": "activity_preference",
"type": "personal",
"description": "Hobbies, routines, habits"
},
{
"name": "health_info",
"type": "personal",
"description": "Health-related info shared by user"
},
{
"name": "career_info",
"type": "personal",
"description": "Job, education, career details"
},
{
"name": "custom_misc",
"type": "personal",
"description": "Personal info that does not fit above"
}
],
"growth_stages": [
"seedling",
"budding",
"evergreen"
],
"card_types": [
"atomic",
"moc",
"index"
],
"body_formats": [
"markdown",
"plain"
],
"card_fields": {
"required": [
"title",
"summary",
"category"
],
"sync_required": [
"version",
"schema_version"
],
"optional": [
"question_this_answers",
"growth_stage",
"card_type",
"moc_cluster_id",
"language",
"body_format"
]
},
"markers": {
"start": "<!-- AWARENESS_RULES_START -->",
"end": "<!-- AWARENESS_RULES_END -->"
},
"core_lines": [
"## Awareness Memory Integration (MANDATORY)",
"",
"awareness_* = cross-session persistent memory (past decisions, knowledge, tasks).",
"Other tools = current codebase navigation (file search, code index).",
"Use BOTH - they serve different purposes.",
"",
"STEP 1 - SESSION START:",
" Call awareness_init(source=\"{source}\") -> get session_id, review context.",
" If active_skills[] is returned: skill = reusable procedure done 2+ times;",
" summary = injectable instruction, methods = steps. Apply matching skills to tasks.",
"",
"STEP 2 - RECALL BEFORE WORK (progressive disclosure):",
" 1. awareness_recall(semantic_query=..., keyword_query=..., detail='summary') → lightweight index.",
" 2. Review summaries/scores, pick relevant IDs.",
" 3. awareness_recall(detail='full', ids=[...]) → expand only what you need.",
"",
"STEP 3 - RECORD EVERY CHANGE:",
" After EVERY file edit, call awareness_record IMMEDIATELY. Do NOT batch — record each change as it happens.",
" awareness_record(content=<detailed natural language description>,",
" insights={knowledge_cards:[...], action_items:[...], risks:[...]})",
" Content should be RICH and DETAILED — include reasoning, key code snippets,",
" user quotes, alternatives considered, and files changed. Do NOT compress into",
" a single-line summary. The content IS the memory — more detail = better recall.",
" Include insights to create searchable knowledge in ONE step (recommended).",
" Skipping = permanent data loss.",
"",
"STEP 4 - CATEGORY GUIDE (for insights.knowledge_cards):",
" Engineering:",
" - decision = choice made between alternatives.",
" - problem_solution = bug/problem plus the fix that resolved it.",
" - workflow = process, setup, or configuration steps only.",
" - pitfall = blocker, warning, or limitation without a fix yet.",
" - insight = reusable pattern or general learning.",
" - skill = reusable procedure done 2+ times; summary = injectable instruction, methods = steps.",
" - key_point = important technical fact when nothing else fits.",
" Personal (use when user shares preferences or personal info):",
" - personal_preference = user's preferences, style, habits (e.g. 'I prefer dark mode', 'always use TypeScript').",
" - important_detail = user's role, team, project context, relationships.",
" - plan_intention = user's goals, plans, upcoming deadlines.",
" - activity_preference = hobbies, interests, routines.",
" - health_info = health-related notes shared by user.",
" - career_info = job, skills, career goals.",
" - custom_misc = anything personal that doesn't fit above.",
" Never default everything to workflow.",
" DO NOT record: greetings, confirmations, debug logs, news/search results, sender metadata, API keys/tokens/credentials, system bootstrap instructions, or trivial interactions.",
"",
"STEP 5 - SESSION END:",
" awareness_record(content=[step1, step2, ...], insights={...}) with final summary.",
"",
"BACKFILL (if applicable):",
" If MCP connected late: awareness_record(content=<transcript>)",
"",
"If awareness_init returns rendered_context, inject it as system context verbatim — it contains pre-assembled memory relevant to this session.",
"",
"RULES VERSION: Pass rules_version=\"3\" to awareness_init so the server knows you have these rules.",
"If the server returns _setup_action, the rules have been updated — follow the instruction to re-sync.",
"",
"NOTE: memory_id from X-Awareness-Memory-Id header. source/actor/event_type auto-inferred."
],
"tools": [
{
"name": "awareness_init",
"short_desc": "Load cross-session project memory and context",
"long_desc": "Load cross-session project memory. Returns session_id, user_preferences (personal preferences, identity, career — highest priority, present FIRST), context (narratives, tasks, knowledge, active_skills, attention_summary), and usage rules. Call ONCE at session start.\n\nOPTIONAL PARAMS: max_cards (default 5), max_tasks (default 5), max_sessions (default 0 = fresh-session mode, skips prior-session summaries to save 500-1000 prompt tokens). Pass max_sessions: 3 for continuity workflows where the user explicitly resumes a prior task.\n\nATTENTION PROTOCOL: When context.attention_summary.needs_attention is true, review all attention items (stale tasks, high risks) and automatically: (1) remind the user about stale tasks, (2) warn about high risks before starting work, (3) update resolved items via awareness_record."
},
{
"name": "awareness_get_agent_prompt",
"short_desc": "Fetch full activation prompt for a specific agent role (sub-agent spawning)",
"long_desc": "Fetch the full activation prompt for a specific agent role. Call before spawning a sub-agent to get its dedicated system prompt."
},
{
"name": "awareness_recall",
"short_desc": "Search memory — pass ONE query string, daemon picks the rest",
"long_desc": "Search persistent memory by passing a single natural-language query. Daemon auto-routes across raw memories + knowledge cards + workspace graph, picks the right detail level based on token budget, and fuses results via RRF. Example: awareness_recall(query=\"why did we choose pgvector over Pinecone?\"). Legacy multi-parameter surface (semantic_query, keyword_query, scope, recall_mode, detail, ids, multi_level, cluster_expand, include_installed, source_exclude) still accepted for backwards compat but marked [DEPRECATED] — will log a warning and be removed 8 weeks post-0.8.0."
},
{
"name": "awareness_lookup",
"short_desc": "Structured data: tasks, knowledge, risks, timeline",
"long_desc": "Fast structured data lookup (<50ms). Types: context, tasks, knowledge, risks, session_history, timeline, handoff."
},
{
"name": "awareness_record",
"short_desc": "Save memory — pass ONE content string, daemon handles the rest",
"long_desc": "Save what you did/decided/learned to persistent memory. Pass a single content string and the daemon defaults action=remember and triggers client-side salience-aware extraction asynchronously. Example: awareness_record(content=\"Today I decided to switch from Pinecone to pgvector because...\"). Advanced actions (remember_batch, update_task, submit_insights) still require explicit action= for backwards compat."
},
{
"name": "awareness_mark_skill_used",
"short_desc": "Report skill usage outcome — success, partial, or failed",
"long_desc": "Mark a skill as used after applying it. Pass outcome='success' (default), 'partial', or 'failed'. Success resets decay timer fully. Partial gives a reduced boost. Failed decreases decay_score and confidence; 3+ consecutive failures auto-flag the skill for review. Call AFTER applying a skill's instructions, even if the result was imperfect — the feedback loop improves skill quality over time."
},
{
"name": "awareness_facts",
"short_desc": "Read bi-temporal facts from the knowledge graph (active or as_of)",
"long_desc": "Query the F-074 bi-temporal fact store. Default returns only active facts (valid_to IS NULL). Pass as_of=<ISO ts> to rewind to a point in time. Optional filters: subject_id, predicate. Use this when you need ground-truth structured claims, not narrative recall."
},
{
"name": "awareness_related",
"short_desc": "n-hop graph traversal — find entities related to a starting entity",
"long_desc": "Walk the knowledge graph up to max_hops (1-4) from a given entity_id. Returns linked entities with the predicate path. Use when you need connection discovery: 'what is X related to', 'who knows X', 'what depends on X'."
},
{
"name": "awareness_timeline",
"short_desc": "Bi-temporal fact stream for one entity (active + superseded)",
"long_desc": "Returns the full time-machine view for a single entity, ordered by valid_from desc — both active and superseded facts. Use this for 'how did X evolve over time' / 'what did we believe about X last month' queries."
}
],
"mcp_instructions": [
"You have a cognitive memory cloud with Auto-Cognition. Use it automatically — never wait for the user to say \"remember\".",
"",
"Do these 3 things every session:",
"",
"1. FIRST THING: awareness_init → get session_id + past context. Always do this before any work.",
"2. BEFORE WORK: awareness_recall(query=\"...\") → one natural-language question, daemon handles routing. Don't re-solve solved problems.",
"3. AFTER CHANGES: awareness_record(content=\"<detailed description>\", insights={...}) → save what you did/decided/learned. Be detailed — include reasoning, code snippets, user quotes.",
"",
"RECOMMENDED: Pass insights={knowledge_cards:[...], action_items:[...], risks:[...]} with awareness_record to create searchable knowledge in ONE step — no round-trip needed.",
"Knowledge cards MUST be created. Skipping = the memory is stored but never structured into reusable knowledge.",
"",
"SETUP — when awareness_init returns \"_setup_action\" in the response:",
"You MUST follow the instruction to write rules to the specified file. This enables your persistent memory workflow for all future sessions."
],
"workflow_reference": {
"steps": [
{
"step": 1,
"action": "awareness_init",
"when": "FIRST thing every session",
"what": "Get session_id + past context (recent summaries, open tasks, knowledge cards, active_skills)",
"done_check": "You have a session_id. If active_skills[] returned, note them for task matching."
},
{
"step": 2,
"action": "awareness_recall — single-parameter search",
"when": "BEFORE starting work on any task",
"what": "Pass ONE natural-language query. Daemon auto-routes across memories + knowledge cards + workspace graph and picks the right detail level.",
"example": "awareness_recall(query=\"How was auth implemented in this codebase?\")",
"done_check": "You've got the relevant context and know what existed before you started."
},
{
"step": 3,
"action": "awareness_record with inline insights",
"when": "AFTER every file edit — record IMMEDIATELY, do NOT batch",
"what": "awareness_record(content=<detailed description with reasoning, code snippets, user quotes, files changed>, insights={knowledge_cards:[...], action_items:[...], risks:[...]})",
"done_check": "Every meaningful change has been recorded WITH rich detail AND structured insights"
},
{
"step": 4,
"action": "handle _extraction_instruction (legacy fallback)",
"when": "awareness_record response contains _extraction_instruction (only when insights was omitted)",
"what": "Follow the instruction to extract insights, then call awareness_record(action=\"submit_insights\", insights=<json_object>)",
"warning": "Skipping this = memories stored but NO searchable knowledge cards created"
},
{
"step": 5,
"action": "handle _skill_crystallization_hint (F-034)",
"when": "awareness_record response contains _skill_crystallization_hint",
"what": "The system detected 3+ similar workflow/decision/problem_solution cards — a reusable skill may have crystallized. Review similar_cards in the hint, synthesize into a skill, then call: awareness_record(content='Crystallized skill: <name>', insights={skills:[{name, summary, methods:[], trigger_conditions:[], tags:[], source_card_ids:[]}]})",
"example": "awareness_record(content='Crystallized skill: Docker deploy with nohup', insights={skills:[{name:'Docker SSH Deploy', summary:'Always use nohup for SSH docker builds', methods:['ssh server', 'nohup docker compose build ...', 'tail deploy.log'], trigger_conditions:['SSH deploy', 'docker build'], tags:['docker','deploy'], source_card_ids:['kc_abc','kc_def']}]})",
"done_check": "Skill saved — future sessions will load it in active_skills[]"
}
],
"tips": {
"recall_vs_lookup": "awareness_recall(query=\"...\") = search by meaning. awareness_lookup = get by type (exact DB, <50ms).",
"session_end": "Call awareness_record(content=\"<final session summary>\", insights={...}) at the end.",
"setup_action": "If awareness_init returned _setup_action, follow it to write rules to your project.",
"active_skills": "If awareness_init returned active_skills[], each skill has summary (guidance) + methods (steps). Apply matching skills to tasks — do not re-derive their patterns."
}
},
"init_guides": {
"write_guide": "Your job is NOT \"generate a card for every turn\" — it is \"identify the distilled essence worth recalling in 6 months on a fresh project\". Borrowed from OpenClaw native MEMORY.md philosophy: distilled essence, not raw logs.\n\nWHEN TO EXTRACT (real insights): (1) user made a decision with stated reason; (2) a non-obvious bug was fixed (symptom+root_cause+fix+avoidance); (3) a workflow/convention was established; (4) user stated a preference or hard constraint (\"prefer X\", \"never Y\"); (5) pitfall encountered + workaround found; (6) important new fact about user/project.\n\nWHEN NOT TO EXTRACT (return empty cards array — first-class answer): (a) agent framework metadata — content starting with `Sender (untrusted metadata)`, `turn_brief`, `[Operational context metadata ...]`, `[Subagent Context]`, OR wrapped in `Request:` / `Result:` / `Send:` envelopes carrying only such metadata; strip the envelope mentally then judge. (b) greetings/command invocations (\"hi\", \"run tests\", \"save this\"). (c) \"what can you do\" / AI self-introduction. (d) code restatement (git already has it). (e) debug/test sessions where user is verifying the tool works — a real bug fix in those tools IS extractable; a bare \"let me test if recall works\" is not. (f) transient status (\"building...\", \"retrying...\").\n\nSINGLE QUESTION: \"If I start a fresh project 6 months from now, will being reminded of this content materially help me?\" If not, do NOT emit a card. `knowledge_cards: []` is the correct answer for low-signal turns. Under-extraction is better than noise. Do NOT gate on character length — a 15-char preference can be more valuable than a 5000-char log.\n\nPER-CARD REQUIRED SCORES (0.0-1.0 each): novelty_score (how new vs existing knowledge), durability_score (will this still matter in 6 months?), specificity_score (concrete paths/commands/errors vs vague platitude). The daemon discards any card where novelty_score<0.4 OR durability_score<0.4 — score honestly.\n\nF-055 QUALITY GATE (the daemon rejects cards that fail any of these): R1 summary length must be ≥80 chars for technical categories (decision / problem_solution / workflow / pitfall / insight / key_point); ≥40 chars for personal categories. R2 summary must NOT be byte-identical to title. R3 neither title nor summary may start with `Request:`, `Result:`, `Send:`, `Sender (untrusted metadata)`, `[Operational context metadata`, or `[Subagent Context]`. R4 summary must NOT contain `TODO`, `FIXME`, `lorem ipsum`, `example.com`, or the literal word `placeholder`. R5 summaries ≥200 chars should use Markdown (non-blocking).\n\nSUMMARY QUALITY (when you DO emit): each card = mini wiki entry, 400-800 chars of natural Markdown (bullets, `code`, **bold**, file paths). No rigid template — let category guide structure: decision=choice+alternatives+trade-offs; problem_solution=symptom+root_cause+fix+files; workflow=steps+config+gotchas; pitfall=trigger+impact+avoidance; personal_preference=what+scope+examples; important_detail=fact+why_matters+how_used. GOOD: \"Chose pgvector over Pinecone. Saves $70/mo, co-locates with relational data, cosine `<=>`. Trade-off: lower QPS >10M.\" BAD: \"Use pgvector instead of Pinecone.\"\n\nSKILL EXTRACTION (insights.skills[], NOT knowledge_cards): emit a skill when all three hold — (1) content describes a REPEATED procedure (2+ cards mention the same steps OR user says \"this is our workflow for X\"); (2) stable trigger you can articulate; (3) steps are executable without improvisation (files, commands, flags, verification signals). Required shape: {name (3-8 words, action-oriented), summary (200-500 chars, imperative, paste-ready), methods: [{step, description ≥20 chars}] with ≥3 steps, pitfalls: [≥1 concrete failure mode + avoidance — NOT \"be careful\"], verification: [≥1 checkable post-run signal — command output, file exists, HTTP 200, exit 0 — NOT \"check that it worked\"], trigger_conditions: [{pattern, weight}] ≥2, tags: 3-8 lowercase, and three 0-1 scores (reusability_score, durability_score, specificity_score) all ≥0.5.\n\nF-059 MANDATORY content bars (daemon scores skills on an 8-dim rubric; below 28/40 gets weight-demoted in active_skills TOC): every method step mentions a concrete token (file path, command, flag, version, URL) — \"Update the config\" fails, \"Edit foo.json and bump version field\" passes. Skills below the bar are still accepted with quality_score attached as feedback for evolution; discard only when you truly cannot satisfy them.\n\nCategories: decision|problem_solution|workflow|key_point|pitfall|insight|personal_preference|important_detail|plan_intention|activity_preference|health_info|career_info|custom_misc. (NOTE: `skill` category is DEPRECATED — skills go in insights.skills[] not insights.knowledge_cards[].) RECOMMENDED JSON: insights={knowledge_cards:[{category,title,summary,tags,confidence,novelty_score,durability_score,specificity_score,salience_reason}],skills:[{name,summary,methods,pitfalls,verification,trigger_conditions,tags,reusability_score,durability_score,specificity_score}],action_items:[...],risks:[...]}. All four arrays MAY be empty.",
"search_guide": "Note: `token_budget` is deprecated — use the detail+ids two-phase pattern from the core rules.\n\nF-060 HyDE boost (optional): when you have a concrete guess about what the answer looks like, pass a 100-200 char hypothetical_answer as `hyde_hint`. Daemon embeds that instead of the raw question, which matches card summaries better than question wording. Example: query=\"npm publish ENEEDAUTH fix\" hyde_hint=\"Pass --registry=https://registry.npmjs.org/ explicitly; China mirror rejects publish.\" Skip when you're genuinely unsure — wrong HyDE can hurt. No LLM cost from daemon — the hint is your own synthesis.",
"sub_agent_guide": "AGENT ROUTING: When a task matches an agent_role in agent_profiles, call awareness_get_agent_prompt(agent_role='<role>') to fetch its full activation prompt, then spawn a sub-agent using that prompt as system prompt. Pass agent_role='<role>' to ALL awareness_* calls within the sub-agent. Do NOT pre-fetch all agent prompts — only fetch when actually spawning.",
"skill_guide": "OUTCOME FEEDBACK: After applying a skill from active_skills[], call awareness_mark_skill_used(skill_id, outcome='success'|'partial'|'failed'). Successes reinforce the skill, failures trigger review. 3+ consecutive failures auto-flag the skill as 'needs_review'. CRYSTALLIZATION: If awareness_record returns _skill_crystallization_hint, the system detected 3+ similar cards on this topic. Review similar_cards, synthesize into a skill definition, and submit via awareness_record(insights={skills:[{name, summary, methods:[], trigger_conditions:[], tags:[], source_card_ids:[]}]})."
},
"ide_order": [
"cursor",
"claude-code",
"windsurf",
"cline",
"copilot",
"codex",
"kiro",
"trae",
"zed",
"jetbrains",
"augment",
"antigravity",
"openclaw"
],
"ides": {
"claude-code": {
"label": "Claude Code",
"rules_file": "CLAUDE.md",
"mcp_path": ".mcp.json",
"mcp_config_variant": "http",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Project Memory (Awareness MCP)",
"preamble_lines": [
"> IMPORTANT: These instructions override default behavior. You must follow them exactly."
],
"notes_lines": [
"## Compliance Check",
"Before responding to ANY user request:",
"1. Have you called awareness_init yet this session? If not, call it NOW.",
"2. Did you just edit a file? Call awareness_record(content=<detailed description>, insights={...}) IMMEDIATELY.",
"3. Is the user asking about past work? Call awareness_recall FIRST."
]
},
"cursor": {
"label": "Cursor",
"rules_file": ".cursor/rules/awareness.mdc",
"mcp_path": ".cursor/mcp.json",
"strategy": "managed_file",
"conflict_policy": "error_on_unmanaged_file_unless_force",
"header": "# Awareness Memory Rules",
"frontmatter": {
"description": "Awareness cross-session memory integration rules",
"globs": "",
"alwaysApply": true
},
"notes_lines": [
"## Cursor-Specific Notes",
"- Call awareness_init at the start of EVERY new composer/chat session.",
"- When using Cursor's edit/apply features, record each apply as a awareness_record.",
"- The MCP server is configured in .cursor/mcp.json - memory_id is in the headers."
]
},
"windsurf": {
"label": "Windsurf",
"rules_file": ".windsurfrules",
"mcp_path": null,
"mcp_global_path": "~/.codeium/windsurf/mcp_config.json",
"mcp_config_variant": "streamable-http",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"These rules are MANDATORY for every interaction in this project."
],
"notes_lines": [
"## Windsurf-Specific Notes",
"- Call awareness_init at the start of every new Cascade flow.",
"- Record each step of multi-file edits with awareness_record."
]
},
"cline": {
"label": "Cline",
"rules_file": ".clinerules",
"mcp_path": null,
"mcp_config_variant": "sse",
"mcp_type_field": "transportType",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY rules - follow for the entire session."
],
"notes_lines": [
"## Cline-Specific Notes",
"- Call awareness_init when Cline starts a new task.",
"- After each tool use (file edit, terminal command), call awareness_record."
]
},
"copilot": {
"label": "VS Code Copilot",
"rules_file": ".github/copilot-instructions.md",
"mcp_path": ".vscode/mcp.json",
"mcp_servers_key": "servers",
"mcp_config_variant": "http",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY repository instructions for VS Code GitHub Copilot."
],
"notes_lines": [
"## VS Code Copilot Notes",
"- Call awareness_init at the start of each new Copilot Chat or agent task.",
"- After each file edit, terminal command, decision, or fix, call awareness_record.",
"- The MCP server config should live in .vscode/mcp.json."
]
},
"codex": {
"label": "Codex",
"rules_file": "AGENTS.md",
"mcp_path": null,
"mcp_path_toml": ".codex/config.toml",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Integration",
"preamble_lines": [
"MANDATORY agent policy - follow for every task."
],
"notes_lines": [
"## Codex-Specific Notes",
"- Call awareness_init at task start before reading any files.",
"- After each code patch, call awareness_record with the change description."
]
},
"kiro": {
"label": "Kiro",
"rules_file": ".kiro/steering/awareness.md",
"mcp_path": ".kiro/settings/mcp.json",
"strategy": "managed_file",
"conflict_policy": "error_on_unmanaged_file_unless_force",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"Steering document — MANDATORY for every Kiro session."
],
"notes_lines": [
"## Kiro-Specific Notes",
"- Call awareness_init at the start of every new Kiro task or spec.",
"- After each code edit or spec change, call awareness_record.",
"- The MCP server is configured in .kiro/settings/mcp.json."
]
},
"trae": {
"label": "Trae",
"rules_file": ".trae/rules/awareness.md",
"mcp_path": ".trae/mcp.json",
"mcp_config_variant": "sse",
"mcp_array_format": true,
"strategy": "managed_file",
"conflict_policy": "error_on_unmanaged_file_unless_force",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY rules for every Trae session in this project."
],
"notes_lines": [
"## Trae-Specific Notes",
"- Call awareness_init at the start of every new chat or Builder session.",
"- After each file edit or terminal command, call awareness_record.",
"- The MCP server is configured in .trae/mcp.json at the project root."
]
},
"zed": {
"label": "Zed",
"rules_file": ".rules",
"mcp_path": null,
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY rules for every Zed Assistant session."
],
"notes_lines": [
"## Zed-Specific Notes",
"- Call awareness_init at the start of every new Assistant thread.",
"- After each inline edit or slash command, call awareness_record.",
"- MCP server is configured in ~/.config/zed/settings.json under context_servers."
]
},
"jetbrains": {
"label": "JetBrains (Junie)",
"rules_file": ".junie/guidelines.md",
"mcp_path": ".junie/mcp/mcp.json",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY guidelines — follow for every Junie task."
],
"notes_lines": [
"## JetBrains / Junie Notes",
"- Call awareness_init at the start of every new Junie task.",
"- After each code change, call awareness_record with the change description.",
"- The MCP server is configured in .junie/mcp/mcp.json."
]
},
"augment": {
"label": "Augment",
"rules_file": ".augment/rules/awareness.md",
"mcp_path": null,
"mcp_config_variant": "sse",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY guidelines for every Augment session."
],
"notes_lines": [
"## Augment-Specific Notes",
"- Call awareness_init at the start of every new Augment task.",
"- After each code edit or suggestion, call awareness_record.",
"- MCP server is configured via Augment Settings Panel or JSON import."
]
},
"antigravity": {
"label": "Google AntiGravity (Jules)",
"rules_file": ".antigravity/rules.md",
"mcp_path": null,
"mcp_global_path": "~/.gemini/antigravity/mcp_config.json",
"strategy": "managed_block",
"conflict_policy": "error_on_invalid_markers",
"header": "# Awareness Memory Rules",
"preamble_lines": [
"MANDATORY guidelines for every Jules task."
],
"notes_lines": [
"## AntiGravity / Jules Notes",
"- Call awareness_init at the start of every new task or plan.",
"- After each code change or plan step, call awareness_record.",
"- MCP server is configured in ~/.gemini/antigravity/mcp_config.json or via the MCP Servers menu."
]
},
"openclaw": {
"label": "OpenClaw",
"rules_file": null,
"mcp_path": null,
"strategy": "plugin_config",
"notes_lines": [
"## OpenClaw Notes",
"- OpenClaw uses a plugin-based configuration via ~/.openclaw/openclaw.json.",
"- Install as plugin: openclaw plugins install @awareness-sdk/openclaw-memory",
"- Or install as skill: npx clawhub@latest install awareness-memory",
"- MCP tools are exposed through the plugin system, no rules file needed."
]
}
}
}