Projects & Services
Logs & Errors
Your agent reads build and runtime logs through MCP to diagnose and fix issues in production
Ink captures logs at every stage of the deployment lifecycle. Your agent reads these logs through MCP to debug issues without you opening a browser.
Build logs
Build logs capture the output of your build process — dependency installation, compilation, and packaging. If a build fails, the error message and stack trace are available immediately.
Your agent reads build logs via:
get_service(name="my-app", deploy_log_lines=200)Runtime logs
Runtime logs capture your application's stdout/stderr output. Up to 500 lines of recent logs are available via MCP.
Your agent reads runtime logs via:
get_service(name="my-app", runtime_log_lines=500)Error messages
When a deployment fails, Ink captures the error and makes it available through get_service. Your agent can:
- Read the error message and stack trace
- Identify the root cause (missing dependency, syntax error, port mismatch)
- Fix the code and redeploy — all without human intervention
Common patterns
| Pattern | Likely cause | Agent action |
|---|---|---|
| Build failures | Missing dependencies, syntax errors | Read build logs, fix code, redeploy |
| Runtime crashes | Unhandled exceptions, missing env vars | Read runtime logs, add error handling |
| Health check failures | App not listening on expected port | Check port config, update service |
| OOM kills | Insufficient memory allocation | Increase memory with update_service |