Skip to content
TuffClassified

Description

I manage several local projects at once, and keeping each one's context separate used to mean juggling tabs, notes, and half-remembered rules for what each project actually needs. Obsidian solved the note-taking side of that years ago, but the gap was connecting that folder structure to an AI agent that actually respects project boundaries instead of mixing everything into one big context.

What changed things for me was setting up an agent that reads folder-level rules — each project gets its own AGENTS.md file defining scope, tone, and what the agent is and isn't allowed to touch. One workspace folder, multiple projects, each with its own rule tree, and the agent picks up the right context depending on where I'm working instead of me re-explaining it every session.

This isn't a theory piece — it's the actual setup I use day to day across different client and personal projects inside one Obsidian vault, with permission modes controlling how much the agent can do on its own versus when it should ask first.

If you're running more than one project out of a single notes vault and want the agent to actually know which rules apply where, this is the pattern that's worked for me.

Details

Views 0
Listing ID #2943334
Website URL https://sonjj.com/blog/obsidian-sonjj-agents-workspace/

Location

Address East 68th Avenue
City Bhubaneswar
State / region Orissa
Country India

Share this listing

Report this listing

Tell us what's wrong. Reports are confidential.

Reason for reporting

Is this your copyright or trade mark? File an infringement complaint

Message seller

You need an account to contact the seller.