Projects & Context

Gestura does not operate in a vacuum. The current project, working directory, local instruction files, and MCP scope all influence how the assistant behaves.

Project-aware behavior

When project instructions are enabled, Gestura looks for project-level guidance in the current working directory and its parents. That gives the agent local rules, conventions, and constraints without you having to repeat them in every session.

Why scope matters

MCP servers can be scoped for different lifetimes and contexts.

• User scope: available broadly across your work.
• Project scope: tied to a particular codebase or directory.
• Local scope: available only for the current session or temporary context.

How to stay in control

• Keep project instructions short, explicit, and trustworthy.
• Prefer project-scoped MCP tools when a tool should only apply to one repository or workspace.
• Use session boundaries when switching to unrelated work.
• Review permission settings before giving a project access to high-impact tools.

Good habits

• Open Gestura from the project you actually want it to reason about.
• Separate personal and work environments if they need different provider or tool settings.
• Keep globally shared tools minimal; add project-only tools where possible.