How unmet Agent Team requests shape the roadmap

When the Outcome Launcher has no proven match, Customize opens a custom Team with your request already filled in. A zero-result Marketplace search offers the same prefilled action plus Clear search. Neither path adds a survey, waitlist, or extra setup step.

• Custom creation remains one click.
• You can run a safe preview before connecting data or spending anything.
• Codelit does not claim that an unmatched request is already planned.

Classification happens locally and reduces the request to one broad category such as Engineering, Support, Sales, Operations, Knowledge, Marketing, Finance, or Other. Analytics receives that category and the entry surface only.

• No prompt or search text.
• No Team or tool label.
• No URL, repository, account, resource id, connection id, credential, source excerpt, output, or provider response.

When you explicitly try to run and setup is incomplete, the existing blocked-run event records one allowlisted capability such as GitHub, Stripe, a model key, an approval gate, browser control, or the local runtime. The same screen still opens the relevant connection, key, approval, plan, or fallback action.

Admin deduplicates repeated clicks from one browser or account, checks whether the same user completes a run or connects the matching app within seven days, and hides every category until at least three distinct users express the same need. A visible low-recovery need becomes a roadmap candidate for human review, not an automatic product promise.

• One person cannot create a candidate by retrying.
• Only aggregate counts and recovery rates are shown.
• The report makes no model, connector, browser, email, or hosted-run call.

Signed-in demand events use the existing account-linked analytics record and are removed by Delete account & data. Anonymous aggregate events that were never linked to an account cannot be resolved back to that account. No new identifier, profile, or demand collection is created.