Skip to main content

​
Overview

Parsaa folds two kinds of persistent context into the agent at the start of every conversation:
  • Instructions — Markdown files in your project (and globally) that define rules, conventions, and architecture.
  • Memory — short snippets you save in-app for facts the agent should remember.
Both are managed under Settings → Project.

​
Instructions

Instructions are Markdown files detected in your project and folded into the agent’s system prompt. Each detected file has an on/off toggle in Settings → Project → Instructions, and the state is remembered per file.

​
PARSAA.md

Drop a PARSAA.md at your project root. Its contents are always included. Plain Markdown.
A global ~/.parsaa/PARSAA.md holds personal preferences that follow you across every project.

​
Modular rules

For larger setups, drop rule files under .parsaa/rules/. Each may declare a YAML frontmatter block:

​
Other formats Parsaa detects

Parsaa also recognizes instruction files written for other tools, so you don’t have to duplicate them: CLAUDE.md · AGENTS.md (walks up to 3 parent directories for monorepos) · .cursorrules · .cursor/rules/*.mdc · .github/copilot-instructions.md · .github/instructions/*.md · .windsurfrules · GEMINI.md · CODEX.md
Because instructions are plain files, they’re shared with your team through git — everyone working in the repo gets the same conventions.

​
Memory

Memory entries are short notes you save in Settings → Project → Memory that get folded into the agent’s context. Each entry is either project-scoped (tied to the current project) or global (available across all projects). Entries are searchable by title, content, and tags.

​
Memory vs Instructions

Both are folded into the system prompt at the start of a conversation — instructions for declarative, team-shared rules; memory for lightweight, local notes.