Features with their own repos

When a feature lives in a repository of its own, and how the connection follows it there.

By default, a feature inherits its focus area's primary repo. But sometimes a feature needs its own working directory.

The use case

Example: you're in a focus area called "Competitors" whose repo is ~/dev/famnly-competitors-research. Mid-session, you realize the actual integration work (mapping data between two services) belongs in a new standalone repo.

You say: "Let's do this in a new folder at ~/dev/famical-revenuecat"

The agent calls create_feature with:

  • name - the new feature
  • focus_area_hint - which focus area it belongs to
  • prd_content - optional PRD
  • repo_path - the new folder path

The MCP tool:

  1. Creates the folder if it doesn't exist
  2. Runs git init if it's not already a repo
  3. Creates the feature with repoPath set
  4. Leaves the terminal to you - open one there and rememd connect

Inheritance

  • If feature.repoPath is set → sessions launch there
  • If not set → sessions use the focus area's primaryRepoPath

In the feature view, you'll see either:

  • folder.gearshape icon + path → feature has its own repo
  • folder icon + path + "inherited" pill → inheriting from focus area

Related repos

A focus area can have multiple repoPaths. The first is the primary - the one rememd connect resolves to from an unlinked folder. The rest are recorded on the focus area and are there for you to connect a terminal in.

Example: your focus area has ~/dev/app-frontend and ~/dev/app-backend. A feature session launches in the frontend, but the agent knows about the backend and can reference files there.