Logs Viewer
Search, filter, and analyze agent logs in real-time with the Synthcore logs viewer.
Logs Viewer
The Logs tab provides real-time visibility into everything your agents are doing. Every action, warning, and error is captured and streamed to this view.
Viewing logs
- Navigate to your project in the dashboard.
- Click the Logs tab.
- Logs stream in real-time as agents work.
The logs viewer automatically updates with new entries — no need to refresh the page.
Log entries
Each log entry contains:
- Timestamp — When the action occurred (HH:MM:SS format)
- Level — Info, Warning, or Error severity
- Agent — Which agent produced the log (Alex, Pixel, Echo, Scout, or System)
- Message — Description of what happened
- Details — Expandable JSON payload with additional context
Example entries
[14:23:01] [INFO] [Alex] Executing: create route handler for /api/users
[14:23:45] [INFO] [Echo] Running TypeScript type check
[14:24:12] [WARNING] [Alex] Build failed - retrying
[14:24:30] [INFO] [Pixel] Committing changes to main
Filtering logs
Use the filter controls to narrow down logs:
By agent
Select one or more agents to show only their logs:
- Alex — Backend operations
- Pixel — Frontend operations
- Echo — QA and testing
- Scout — Research activities
- System — Infrastructure events
By severity
Filter by log level:
- Info — Normal operations and progress updates
- Warning — Recoverable issues, retries, skipped tasks
- Error — Failures that require attention
By search
Use the search box to find specific log entries. Search matches against:
- Log messages
- File names
- Error descriptions
Exporting logs
To export logs for analysis:
- Set your desired filters (date range, agent, severity).
- Click Export above the log viewer.
- Choose format: CSV or JSON.
Exported logs include all fields for programmatic analysis.
Log retention
Logs are retained based on your plan:
| Plan | Retention |
|---|---|
| Starter | 7 days |
| Pro | 30 days |
| Business | 90 days |
| Enterprise | Custom |
After the retention period, logs are automatically archived. Export important logs before they're deleted.
Common log patterns
Agent initialization
[09:00:00] [INFO] [System] Agent schedule triggered
[09:00:02] [INFO] [Scout] Loading project context from SOUL.md
[09:00:05] [INFO] [Alex] Fetching recent commits from main
Task execution
[10:15:00] [INFO] [Alex] Task: implement user auth
[10:15:30] [INFO] [Alex] Creating lib/auth/login.ts
[10:16:45] [INFO] [Alex] Modifying app/api/auth/login/route.ts
Errors and warnings
[11:30:00] [WARNING] [Echo] Test suite failed: 2/15 tests failing
[11:30:15] [INFO] [Echo] Rerunning failed tests
[11:31:00] [INFO] [Echo] All tests passing
Troubleshooting with logs
If agents aren't working as expected, logs often reveal the issue:
- Check for errors — Filter by Error level to see failures
- Trace the flow — Look at timestamps to understand what happened when
- Check agent boundaries — Warnings about file access restrictions indicate boundary issues
- Review build output — Echo's logs show build and test results
Need more help?
- Troubleshooting Guide — Common issues and solutions
- Contact Support — We're here to help