agnes-the-ai-analyst/cli/skills/corporate-memory.md at e438170ade1cbb5ffee693b72c577fd29bf4e504

ZdenekSrotyr 1563b05f2e refactor(cli): hard-cutover env vars + config dir to AGNES_*

Task 0.5 of clean-analyst-bootstrap. Greenfield rewrite — no fallback,
no aliases. Existing dev environments lose their cached PAT and must
re-authenticate.

Env var renames (hard cutover):
- DA_CONFIG_DIR    -> AGNES_CONFIG_DIR
- DA_SERVER        -> AGNES_SERVER
- DA_SERVER_URL    -> AGNES_SERVER_URL  (test-only stale ref, not in spec)
- DA_NO_UPDATE_CHECK -> AGNES_NO_UPDATE_CHECK
- DA_LOCAL_DIR     -> AGNES_LOCAL_DIR
- DA_TOKEN         -> AGNES_TOKEN
- DA_STREAM_RETRIES -> AGNES_STREAM_RETRIES

Config dir rename: ~/.config/da/ -> ~/.config/agnes/ (across code,
comments, docstrings, error messages, install templates, dev scripts).

Stale `da X` references in CLI source (and adjacent app/, tests/):
swept docstrings, comments, help text, and error messages where the
verb survives the rewrite (init, pull, push, catalog, status, diagnose,
auth, admin, skills, query, schema, describe, explore, disk-info,
snapshot, login, logout, whoami, server, setup) and replaced `da X`
with `agnes X`. Intentionally kept `da sync`, `da fetch`, `da analyst`,
`da metrics` — those verbs are removed in later tasks; the legacy
strings will be detected by `_LEGACY_STRINGS` (added in Task 2).

Test fixes:
- TestCLIVersion now asserts output starts with `agnes ` (was `da `).

Test results: 2675 passed, 25 skipped (full pytest run, excluding 9
pre-existing test_db.py / test_user_management.py / test_e2e_extract.py
/ test_cli_binary_rename.py failures unrelated to this rename).

2026-05-04 16:35:44 +02:00

1.1 KiB

Raw Blame History

What It Is

Corporate memory collects knowledge from all analysts' CLAUDE.local.md files and makes it available to everyone through a curated catalog.

How It Works

Analysts write insights in their CLAUDE.local.md
da sync --upload-only pushes content to server
Server processes with LLM (Haiku) to extract knowledge items
Items go through governance (pending → approved/mandatory)
Approved items are distributed as Claude rules

Governance Flow

pending: New item, awaiting review
approved: Available to all users
mandatory: Force-pushed to all users' rules
rejected: Not distributed

Admin Commands

# View pending items (via web UI or API)
agnes query "SELECT id, title, status FROM system.knowledge_items WHERE status='pending'" --remote

# Approve/reject via API
curl -X PUT http://server:8000/api/memory/<id>/status?new_status=approved -H "Authorization: Bearer $TOKEN"

Voting

Users can upvote/downvote knowledge items to surface the most useful ones.

1.1 KiB Raw Blame History

Corporate Memory — Knowledge sharing and governance