---
name: Agentlas Auto-Activation
slug: agentlas-auto-activation
category: AI Engineering
description: Agentlas Auto-Activation turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files. Use it when adding or auditing local runtime behavior that activates project continuity.
github: "https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation"
language: Python
stars: 1160
forks: 116
install: "npx degit https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation ~/.claude/skills/agentlas-auto-activation"
installs_to: ~/.claude/skills/agentlas-auto-activation
source_path: skills/agentlas-auto-activation/SKILL.md
collection_size: 25
category_size: 2451
collection_url: "https://dirskills.com/collections/agentlas-ai/Agentlas-OS"
added: 2026-08-20T07:55:52.942Z
last_synced: 2026-08-20T07:55:52.942Z
canonical_url: "https://dirskills.com/skills/agentlas-auto-activation"
---

# Agentlas Auto-Activation

Agentlas Auto-Activation turns a project folder into an Agentlas-aware workspace with .agentlas memory and sitemap files. Use it when adding or auditing local runtime behavior that activates project continuity.

**Install:**

```bash
npx degit https://github.com/agentlas-ai/Agentlas-OS/tree/main/skills/agentlas-auto-activation ~/.claude/skills/agentlas-auto-activation
```

## README

# Agentlas Auto-Activation

Use this skill when a local runtime should activate Agentlas project continuity
for a folder.

## Procedure

1. For explicit activation, call `hephaestus project ensure --project <folder>`
   from Agentlas Core.
2. For automatic activation, require a trusted writable host, an allowed root,
   a workspace marker, and host-side opt-in. Passive search, read-only work,
   and MCP requests do not imply write consent.
3. Never create project state in the user's home directory, filesystem root, or
   outside the host's allowed project roots.
4. Install the managed privacy `.gitignore` block before local memory/indexes.
5. Add missing seed files, ontology/career indexes, and the bounded code map
   without overwriting existing user content.
6. Inject relevant project memory into future agent prompts.
7. Ask workers to emit `## Memory Events` only for durable facts.
8. Route Memory Events through Memory Tickets and Memory Curator.
9. Use sitemap/task-bias state to avoid stale or unvalidated surfaces.

## Minimum Files

- `.agentlas/project-soul-memory.md`
- `.agentlas/sitemap.json`
- `.agentlas/memory-map.json`
- `.agentlas/memory-tickets.jsonl`
- `.agentlas/vault-references.json`
- `.agentlas/skill-registry.json`
- `.agentlas/skill-trials.jsonl`
- `.agentlas/curator-decisions.jsonl`
- `.agentlas/activation.json`
- `.agentlas/code-map/project-map.json`
- `.agentlas/ontology-runtime.json`
- `.agentlas/ontology-runtime.sqlite`
- `.agentlas/career-graph.json`
- `.agentlas/career-graph.sqlite`

## Safety

Never store secrets, raw logs, full transcripts, cookies, private keys, service
accounts, or payment material in `.agentlas`.

Keep MCP auto-bootstrap disabled unless the host separately opts in. Automatic
receipts must not expose absolute project paths or raw filesystem errors.

If private files were already tracked before activation, report them as
`trackedSensitivePaths`; never mutate the user's Git index automatically.

## Reference

See `docs/agentlas-auto-activation.md`.