FauxAI

Get access
Get access

See how it works

Quick product walkthrough

Learn the main controls first

The preview below shows the basic interaction loop so you can see where the app lives on screen and how the core shortcuts behave.

Scroll on toolbar area to scroll response window.

Take a screenshot using CTRL+Q of the current screen view like a test or code example and receive a solution.

Hold CTRL+V to record audio on your PC.

Press CTRL+H in order to toggle visibility.

The response window is click-through and will not interrupt your work. You can make it more opaque in settings if needed.

Visit settings to adjust the app around your own preferences.

^+HShow/Hide
^+QTake screenshot
^+VHold voice
^+XClose responseCapturing...

Listening...

Tune the app to your needs

The settings window lets you shape how FauxAI behaves on your screen before you use it in a real session.

Adjust opacity plus response width and height so the window fits your screen.

Change the response font size if you want larger text or a denser layout.

Swap theme and colors to match the way you prefer to read the response window.

Rebind hotkeys for screenshot, voice hold, close response, show or hide, and quit.

Pick the model and preferred syntax before a session so the output matches your workflow.

You can also check your active package and remaining credits before longer practice runs.

Use Always on top or Stealth mode depending on how visible you want the app to be.

Keep a few practical things in mind

The app can solve a test for you, but it works best when you stay calm, use the output naturally, and do a quick check before you rely on it.

Be patient if the servers are busy. A reply can sometimes take close to 100 seconds, so stay calm and let it finish. Most tests give you far more time than that.

Use the answer naturally. FauxAI can give you structure and ideas, but you still need to type, explain, and react like yourself.

Give the output a quick sanity check before you use it. AI can still miss context or make a wrong assumption.

When you take a screenshot, try to capture as much relevant text, prompt detail, and input or output examples as possible. Better context usually leads to a better answer.

Let's get started