Project groups

mxkey has no actual project object — projects are a naming convention, not a data structure. What ties a "project" together is just a shared prefix like project.myapp.*.

The CLI knows how to operate on prefixes:

Example

After mxkey migrate .env.local myapp:

$ mxkey list project.myapp
project.myapp.database_url           DATABASE_URL
project.myapp.openai_api_key         OPENAI_API_KEY
project.myapp.resend_api_key         RESEND_API_KEY
project.myapp.stripe_secret_key      STRIPE_SECRET_KEY

Now run them as a group:

$ mxkey run project.myapp -- pnpm dev
# all 4 secrets loaded as env vars

Or pin to the folder via the manifest:

$ mxkey init project.myapp
# wrote .env.mxkey with 4 name(s)

$ cd services/api
$ mxkey run-here -- pnpm dev
# walks up to find .env.mxkey, loads all 4

Prefix matching

A prefix matches:

• The exact name (project.myapp itself, if such an entry exists), OR
• Anything starting with <prefix>.

So project.myapp matches project.myapp AND project.myapp.stripe, but not project.myappextras.foo.

When to use which

See also

• init
• run-here
• migrate — creates the group + manifest in one step