profiles / workspaces / config
Manage profiles, save targets, load limits, read/proof modes, roles, and runtime config.
profile
engram profile status
engram profile create personal --global-path ~/Documents/engram-personal --use
engram profile use company --workspace
engram profile merge personal company --dry-run
Profile resolution order is explicit --profile or ENGRAM_PROFILE, then the workspace default_profile, then the active user profile. If workspace W is pinned to profile B while the user default remains profile A, every normal load, MCP load, and agent-hook injection for W reads profile B global memory and never profile A. An explicit profile different from the workspace default uses that profile's global memory and disables workspace memory for that command.
set-save-target
engram set-save-target status
engram set-save-target workspace
engram set-save-target global
engram set-save-target both
set-load-limit
engram set-load-limit 1..32
engram set-load-limit status
engram set-load-limit reset
set-read
engram set-read startup|auto|always|manual|off
engram set-read status
set-proof
engram set-proof off|compact
engram set-proof status
set-role
engram set-role frontend
engram set-role backend security
engram set-role
When engram set-role ... or engram set-rule-variant ... succeeds, the CLI returns an Agent action: line. Engram-aware slash adapters and MCP hosts should immediately rerun engram load "<current task/request>".
set-rule-variant
engram set-rule-variant strict|balanced|light|off|status
config
engram config view
engram config set <key> <value>
Key settings reference
| Key | Description | Default | Range / Options |
|---|---|---|---|
memory.rule_line_target | Recommended line count target for rule memories | 70 | 50 to 200 |
memory.rule_line_hard_limit | Maximum allowed line count for rule memories | 100 | 50 to 200 |
load.limit | Max memories returned by normal load | 8 | 1 to 32 |
rule_variants.enabled | Enable or disable rule variants generation | false | true, false |
rule_variants.active | Active rule variant mode | balanced | light, balanced, strict |
graph.enabled | Enable or disable graph-aware routing | true | true, false |
graph.max_related | Max related memories to fetch from graph edges | 4 | 1 to 20 |
graph.min_related_score | Min similarity score to add graph edges | 0.22 | 0.0 to 1.0 |
vector.enabled | Enable or disable vector search fallback | true | true, false |
live_sync.enabled | Sync generated agent context files on save | false | true, false |
global_git.enabled | Enable global Git repo sync automation | true | true, false |
global_git.remote | Git remote name for global sync | origin | String |
global_git.branch | Git branch name for global sync | main | String |
These settings are also manageable visually under the Construct tab in engram entry.
Next steps
Git author identity
Engram can store a global author and an optional workspace override. Resolution is workspace, global, then read-only Git fallback. Settings affect future memories only; a workspace override never changes global Git configuration. Use explicit plan and confirmation for global Git sync or legacy-memory migration.
engram author show
engram author set --name "Jane Doe" --email "jane@example.com"
engram author unset --scope workspace
engram author sync-git-global --plan
engram author sync-git-global --confirm
engram author migrate-memories --plan
engram author migrate-memories --confirm
Read the complete Git author settings guide.