Turn a production error into a fix
Aiola puts production errors and GitHub beside coding agents in one macOS and Windows desktop app. Fix It carries the error context into an agent thread, and you review the patch.
Key facts
Find the error that needs attention
App Logs captures uncaught exceptions, rejected promises, console errors and failed HTTP requests. It groups matching events into one issue. Filter by status, environment, browser, device or HTTP status.
Hand the error to an agent without copy-paste
The error tracker and the coding agent live in the same workspace. Fix It starts a thread with the group's error context, so you do not paste stack traces. Git settings can run App Logs actions in a fresh worktree.
Check the proposed fix
Ask the agent to reproduce the failure and add a regression test. Read the diff and the test result in the thread's Review panel. Open a pull request when the work is ready.
Follow the workflow
- Add the App Logs SDK or raw HTTP ingest; hosted App Logs needs Pro or a trial.
- Upload source maps under the same release your app sends.
- Open a grouped error and read its stack trace and breadcrumbs.
- Choose Fix It and ask the agent to reproduce the failure first.
- Ask for a regression test, then run the checks and inspect the diff.
- Set the group to closed after the fix ships.
What to review at the end
- An error group connected to a thread in the right repository.
- A proposed fix with a test and checks for you to inspect.
- A pull request you review before it reaches users.
See all workflows and guides.
Common questions
Build, ship and fix in one app
Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app. Every issue becomes a task an agent can take.