Agentlas Auto-Activation
SkillFiles & storageThis skill lets your AI prepare a project folder to work as an Agentlas workspace. Once added, your AI can set up the .agentlas memory and sitemap files a folder needs, and review folders that already have them to confirm the setup is in order.
Available today. Use it from your connected AI after setup.
No other account needed.
Add the skill, then point your AI at a project folder and ask it to set up the workspace. It will create the .agentlas memory and sitemap files for you.
Then ask your AI: use the Agentlas Auto-Activation skill
What your AI can do with it
- Turn a project folder into an Agentlas-aware workspace
- Create .agentlas memory files in a project folder
- Create sitemap files for a project
- Audit a folder's existing Agentlas setup
- Work on folders stored locally on your machine
What this skill tells your AI
The instructions your AI receives, as published by agentlas-ai/agentlas-os in skills/agentlas-auto-activation/SKILL.md and read by ahel’s review.
Use this skill when a local runtime should activate Agentlas project continuity for a folder.
Procedure
- For explicit activation, call
hephaestus project ensure --project <folder>from Agentlas Core. - 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.
- Never create project state in the user's home directory, filesystem root, or outside the host's allowed project roots.
- Install the managed privacy
.gitignoreblock before local memory/indexes. - Add missing seed files, ontology/career indexes, and the bounded code map without overwriting existing user content.
- Inject relevant project memory into future agent prompts.
- Ask workers to emit
## Memory Eventsonly for durable facts. - Route Memory Events through Memory Tickets and Memory Curator.
- 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.
Signals
- GitHub stars
- 1k
- Forks
- 103
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
agentlas-auto-activation- Source
- github.com/agentlas-ai/agentlas-os