openagentsinc/openagents

Overview

This skill checks and streams Khala deployment logs from the CLI so you can inspect failed actions, authorization errors, timeouts, and function execution details. It helps you confirm which deployment (dev vs prod) is serving traffic and surface env var mismatches that cause 401/500 errors. Use it to quickly correlate runtime errors with environment configuration and function timing.

How this skill works

It runs the Khala CLI log commands from the app directory that contains the khala/ folder and streams log events or fetches a history snapshot. You can target dev (default) or production with flags, include successful runs, output raw JSONL, or limit results with a history count. It also exposes commands to list or fetch deployment environment variables so you can verify keys and URLs used by actions.

When to use it

• User reports errors from Khala such as unauthorized, validation errors, or timeouts.
• You need to confirm whether the app is using dev or prod Khala deployment.
• You want to find which function ran, its duration, and whether it failed or succeeded.
• Debugging env var mismatches (OA_INTERNAL_KEY, PUBLIC_API_URL) that cause 401s between services.
• You need a finite snapshot of recent logs instead of continuous streaming.

Best practices

• Run commands from the app directory that contains the khala/ folder (e.g. cd apps/web).
• Remember dev is the default; add --prod for production logs or envs.
• Use --history N to fetch a finite number of entries when streaming times out or for quick inspection.
• Add --success when you need successful executions as well as failures.
• Use --deployment-name to target a specific deploy if multiple deployments exist.

Example use cases

• Stream production logs while reproducing a 401 to see which action and external API returned unauthorized.
• Fetch the last 30 prod log entries to quickly locate a failing mutation without continuous streaming: npx khala logs --prod --history 30.
• Verify that OA_INTERNAL_KEY is set on the running deployment before troubleshooting an API worker auth failure: npx khala env get OA_INTERNAL_KEY --prod.
• Confirm which deployment name is serving production traffic by reading the header shown when streaming logs.
• Output raw JSONL for ingestion into a log analysis tool using --jsonl.