How agents identify context

Most MCP tools take a product_hint parameter. Here's how resolution works.

Resolution order

1. Exact name match - product_hint: "Famnly" matches a product named "Famnly" (case-insensitive)
2. Partial name match - substring match on product names
3. Repo path match via focus areas - if the hint matches a folder name in any focus area's repo paths
4. Current working directory - if the MCP's CWD is inside any focus area's repo paths

This means the agent usually doesn't need to guess perfectly - sending product_hint: "tools" when the CWD is ~/dev/famnly-tools still resolves correctly. Pass workspace_hint if the same product name exists in multiple workspaces.

Focus area resolution

When a tool takes focus_area_hint:

• If provided, matched by name within the resolved product
• If omitted, inferred from the active feature's focus area
• If "none", explicitly means product-level (for backlog items)

Nothing is written into your repo

rememd used to write a CLAUDE.md and an AGENTS.md into the working directory. It no longer writes anything: the routing table is handed to the agent over MCP at initialize, before your first prompt, and the connected target rides along with the greeting on the first tool call.

That is strictly better than the file was. instructions reaches every MCP client, including the ones that never read a file, and it cannot go stale in a folder you have since re-pointed somewhere else.

If a folder still holds a CLAUDE.md or AGENTS.md that rememd generated, connect removes it - but only if rememd wrote it. A hand-written one is yours and is left alone, and the connect output says which files it left.