Turn one feedback report into a task your coding agent can run. Triage the submission, mention it on the task, and move that task to In Progress. That move starts the configured agent workflow. You can review the result in Human Review before Create PR.
Collect reports for one project
A workspace is one project. Hosted Feedback needs Pro or the 7-day trial. The trial is for first-time Pro Monthly customers, and checkout collects a card. GUI Lifetime does not include hosted feedback dashboards. The desktop app is a free download for macOS 12 or newer and Windows 10 or newer.
Pro at 100,000 events costs $24 a month or $240 a year. See pricing for the higher event tiers.
Open Settings, then API Key, and select Generate Key. Copy the raw key immediately. Store it in the server environment used by the integration. The same key authenticates Feedback and App Logs. Each project name has at most one project key.
Open Settings, then Feedback. Under Forms, configure Issue and Feature Request, then select Save. Use Get code on that page. Get code offers Next.js, React, and Python. Raw HTTP can submit without those generated files. Follow Set up Feedback to install the files.
The default issue form requires a title, email, device, and description. Attachment and URL are optional. The default feature request form requires a title and description. Its attachment and URL are optional too. You can change the fields and which ones are required. Payloads must match the saved schema.
The default device options are macOS - Intel, macOS - M Series, Windows, iPhone, and Android. Generated browser components accept PNG, JPEG, and WebP. They keep five files. The server accepts the first five images on the attachment field.
Submissions for that project key show in workspace Feedback. Open Feedback for the active workspace. Central Feedback combines project-tagged submissions and keeps project context. It does not use a second ingest key.
Triage each report first
You can filter, search, sort, change pages, change status, or delete a report. Start Analyze or Fix It from that list too. The owner list returns at most 1,000 records. Bulk status changes and deletes accept at most 500 IDs. Deleting a report also removes its stored attachments.
Feedback statuses are open, in_progress, human_review, closed, and ignored. The feedback docs do not show a status change creating a task. Create the task yourself when the report should become work.
Chat on a bug report applies the Bug Report Analysis prompt. A feature-request Chat applies the Feature Request Analysis prompt. Fix It on a bug report applies the Bug Fix prompt. A feature request uses the Feature Implementation prompt for Fix It. The issue form is the bug report form in workspace settings. Edit those prompts under Workspace Settings, then Workspace, then Instructions. Changes apply to the active workspace. GUI Lifetime omits the hosted Feedback instruction groups.
Workspace Settings, then Git, includes Run feedback actions in worktree. That toggle uses a fresh worktree for Feedback actions. It is separate from the task run mode.
Start with the title and description. Check the URL field when the submission includes one. Check the attachment when the submission includes images. Those fields describe the report. Your task states the change you want.
Write a task from the report
Tasks have no public collection key and no ingest endpoint. You create them in the app, or you import a CSV. Append adds records to the current board. Replace replaces that board. Open Tasks for the board or the list. Both views show the same records. Board columns are the workflow statuses, and you can drag those columns.
The workspace Tasks page shows the active workspace. Central Tasks combines project-aware records. Each record keeps its project context.
Mention the feedback item on the task. A task can also mention a file, another task, or an agent. It can mention an app log, a workspace, an issue, or a pull request. You can attach files and images to the task.
The detail panel edits comments, subtasks, links, attachments, and mentions. Task chat retains the task context. The timeline records status changes and other activity. A task can store a priority, labels, and a scheduled date and time.
Use subtasks or linked tasks when one report needs more than one change.
This table is a writing pattern. The rows are not extra required fields.
| Task content | What to include |
|---|---|
| Title | Name the behavior and the intended change. |
| Source | Mention the feedback submission. |
| Expected result | State what should be true after the change. |
| Scope | Name the area involved and any open question. |
| Review checks | State how you will check the reported behavior. |
State the outcome you want in the task text. Keep the user's report and that request distinct.
Start the agent from In Progress
Choose Local or Worktree on the task before you move it. Local runs in the workspace checkout. Worktree runs in an isolated Git worktree. The task can override the workspace default. Set the default for new tasks under Project Settings, then Tasks.
Moving the task to In Progress starts its configured agent workflow. That move works in the workspace and in Central. See the task docs for those status moves.
Aiola's agents are Claude Code, Codex, Cursor, Grok CLI, OpenCode, and Antigravity. You use your own subscriptions, and there is no token markup.
Review before the pull request
Tasks use nine statuses. They are Backlog, Todo, Scheduled, In Progress, Blocked, Human Review, Create PR, Complete, and Cancelled. Feedback keeps its own five statuses. Update each record on its own. The docs do not show one status write updating the other record.
Move the task to Human Review when you want to inspect the result first. Compare the result with the report and with the outcome on the task. Move the task to Create PR when pull-request creation should start. That status starts pull-request creation.
Project Settings, then Tasks, controls automatic PR creation after task completion. Auto-create-PR can route a successful run to Create PR instead of Human Review. Without that routing, a successful run goes to Human Review.
When the task work is finished, move the task to Complete. Set the feedback item to open, in_progress, human_review, closed, or ignored.
Try it in Aiola: Download the desktop app, open one project workspace, and pick one feedback submission. Mention it on a task, choose Local or Worktree, and move the task to In Progress.
