Profiles

Profiles let you use different thoughts repositories for different projects. For example, you might have a work profile pointing to your company’s thoughts repo and a personal profile for side projects.

Create a Profile

hyprlayer thoughts profile create work

This prompts for:

• Thoughts repository path — Where this profile’s thoughts are stored
• Repos directory name — Subdirectory for project-specific thoughts
• Global directory name — Subdirectory for cross-project thoughts

Or specify everything non-interactively:

hyprlayer thoughts profile create work \
  --repo ~/work-thoughts \
  --repos-dir repos \
  --global-dir global

Use a Profile

When initializing a project, specify the profile:

hyprlayer thoughts init --profile work

The project will be mapped to that profile’s thoughts repository. All subsequent syncs will use the correct repository automatically.

List Profiles

hyprlayer thoughts profile list

hyprlayer thoughts profile list --json

Show Profile Details

hyprlayer thoughts profile show work

hyprlayer thoughts profile show work --json

Delete a Profile

hyprlayer thoughts profile delete work

Use --force to delete even if the profile is in use by mapped repositories.

How Profiles Work

Each project’s repository mapping in the config can optionally reference a profile. When Hyprlayer resolves paths for a project, it checks:

1. Does this project have a profile mapping?
2. If yes, use that profile’s thoughtsRepo, reposDir, and globalDir
3. If no, use the default (top-level) configuration