setup

Setup Awareness Memory: check local daemon status, optionally authenticate via browser, select a memory, and write credentials to settings.json.

Cloud API base URL: https://awareness.market/api/v1 Local daemon URL: http://localhost:37800

Step 1 — Check local daemon

First check if the local Awareness daemon is running:

curl -sf http://localhost:37800/healthz 2>/dev/null && echo "DAEMON:RUNNING" || echo "DAEMON:NOT_RUNNING"

If daemon is running (DAEMON:RUNNING):

Get daemon status:

curl -sf http://localhost:37800/api/v1/status 2>/dev/null || echo "{}"

Tell the user:

Awareness local daemon is running!

Status: [show memory_id, mode, etc. from status response]
MCP URL: http://localhost:37800/mcp

Your local memory is ready to use.

Then ask: "Want to connect to Awareness Cloud for sync and sharing? (yes/no)"

• If no → jump to Step 5 (write local-only settings) and finish.
• If yes → continue to Step 2 (cloud auth).

If daemon is NOT running:

Check if user has existing cloud credentials (same logic as before):

1a. Check environment variables (from settings.json)

Read the current environment variables AWARENESS_API_KEY and AWARENESS_MEMORY_ID. If both exist AND AWARENESS_API_KEY starts with aw_ AND is NOT the placeholder aw_your-api-key-here, and AWARENESS_MEMORY_ID is NOT your-memory-id-here:

• Tell the user cloud credentials are already configured.
• Ask: "Do you want to re-configure? (yes/no)"
• If no → stop here. Suggest running /awareness-memory:session-start instead.
• If yes → continue to Step 2.

1b. Check ~/.awareness/credentials.json (left by npx @awareness-sdk/setup)

Run:

cat ~/.awareness/credentials.json 2>/dev/null

If the file exists and contains a valid api_key (starts with aw_):

• Tell the user: "Found existing Awareness credentials (from a previous setup). Reusing them."
• Extract the api_key and api_base values.
• Skip Step 2 and Step 3 — jump directly to Step 4 (Memory selection) using this api_key.