Run several side projects as an indie hacker
Aiola puts errors, feedback, analytics and GitHub for each side project beside agents in one macOS and Windows desktop app. Ship the next fix on each product without a tool stack per project.
Key facts
Fix the booking app
Open the booking workspace and read a checkout error in App Logs. Choose Fix It so the agent starts with the error context, and run it in a worktree. Review the test and diff before opening a pull request.
Choose the directory's next change
Switch to the directory workspace to read its Analytics and Feedback. A report about missing filters already sits beside the code, so a Codex thread can start from it. Ask for one filter first and check traffic later.
Maintain the open-source CLI
Schedule a weekly dependency review in the CLI workspace. Read the run output and linked thread before accepting changes. Review its GitHub pull requests apart from the other projects.
Follow the workflow
- Add the booking app, directory and CLI as separate workspaces.
- Connect App Logs, Feedback and Analytics per project; these need Pro or a trial.
- Open the booking workspace and choose Fix It on the checkout error.
- Review the booking fix, then send the directory's missing-filter report to an agent.
- Save a weekly dependency-review automation in the CLI workspace; keep the desktop on and awake.
- Check Central for new errors and feedback across the three projects.
What to review at the end
- A booking fix with a test and diff ready for review.
- One directory change you can check against later traffic and feedback.
- A CLI maintenance report you can read before choosing updates.
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.