Project linking & config

After login, you only need slugs (or friendlier app aliases) to address a project. Linking a directory removes the need to specify it on every command.

App aliases

Register a friendly name for a project slug:

loguro config add prod --slug=my-prod-app
loguro config add staging --slug=my-stg-app

Link a directory

cd ~/work/api-prod
loguro link my-prod-app          # writes ./.loguro: { "slug": "my-prod-app" }
loguro logs -l error             # uses your PAT + the linked slug

If you have an app alias configured, link by alias instead — the file stores { "app": "prod" }:

loguro config add prod --slug=my-prod-app
loguro link prod                 # writes { "app": "prod" }

Walk-up behavior

From any subdirectory, the closest .loguro walking upwards is used. Commit it to git — no secrets are stored, only the slug or app name.

App shortcut

If an app is configured, use its name as the first argument — equivalent to --app=<name>:

loguro prod logs -l error          # = loguro logs --app=prod -l error
loguro prod tail                   # = loguro tail --app=prod
loguro prod                        # = loguro logs --app=prod (last 20)
loguro staging slow                # = loguro slow --app=staging

Unlink

loguro unlink                    # removes ./.loguro from cwd

.loguro file format

{ "slug": "my-prod-app" }

or:

{ "app": "prod" }

Either form is valid. The CLI resolves an app reference through the config store; a slug is used directly.