Write brief Markdown conventions explaining the workspace’s purpose, terminology to preserve, and checks the assistant or an external agent should make.
Save shared conventions
Portable assistant guidance lives in .tano/rules/assistant.md. Tano also reads an existing root AGENTS.md, which remains a user-managed file. Tano does not automatically rewrite existing rules. Each rules file is limited to 32 KB.
For example:
Preserve product names and original citations.
Read target documents before editing; check existing tasks before creating action items.
Submit edits as proposals for me to review before saving.
Useful guidance names the workspace purpose, content format, important folders, checks to make before editing, and how to verify finished work. Keep rules short, testable, and consistent with actual file and tool permissions.
Guidance and permissions
Rules set style and workflow and can narrow permissions. They cannot expand assistant access, authorize direct saving, execute terminal commands, or change service addresses. The client, OS, and tools determine access. Ordinary documents and tool responses are data, not a source of new authorization.
Local MCP Gateway uses its startup configuration to scope file, object, table, and relation queries and pending proposals. Legacy direct Markdown writes require explicit write access. An agent using its own filesystem or terminal tools may have broader access. See MCP integration and Access control.