Skip to main content
A UIPP (User Input Parsing Policy) tells the Desktop App how to extract a user’s input from captured traffic for a specific target URL (an internal chat UI, a SaaS LLM, etc.). Each UIPP also determines the InputType (TEXT / IMAGE / FILE) automatically.

Who registers UIPPs

UIPPs are registered by AIM Intelligence System Administrators, not by Company admins. The registration surface lives in a separate AIM-only admin portal and is not customer-configurable. As a Company admin you do not need to author UIPPs — the Desktop App ships with UIPPs for every supported agent (VSCode, Cursor, Web Agent, and others). If one of your target URLs is already supported, it is automatically covered.

When to request coverage

Submit a request when:
  • Your organization uses an AI tool whose target URL is not yet supported.
  • An existing UIPP mis-parses a target URL (e.g., missing attachments, wrong InputType).
  • A tool’s API changes and coverage regresses.

How to request

1

Identify the target URL

Record the exact origin and path, and describe the flow (chat prompt, file upload, image generation, etc.).
2

Capture an example

If possible, attach a HAR file or request transcript showing what input needs to be extracted.
3

Email AIM Intelligence

Send the request to contact@aim-intelligence.com with the target URL, example payload, and expected InputType.
Once AIM registers the UIPP, it propagates to Desktop Agents on the next configuration refresh — no redeploy required.

How the Desktop App works

Where UIPPs fit in the Desktop App request flow.