Bug Report: ParakeetAI Freezing, Not Responding, and Audio Capture Issues During Interview on June 15, 2026

Dear ParakeetAI Support Team,

I am reporting multiple technical issues I experienced while using ParakeetAI during an interview. These issues occurred on June 15, 2026, at around 10:00 AM IST, and they prevented me from using the product properly during the session.

Bug Report

Product: ParakeetAI
Issue Type: Technical Bug / Service Failure
Severity: High
Incident Date: June 15, 2026
Approximate Time: Around 10:00 AM IST
Impact: The tool became unusable during a live interview

Summary

During my interview on June 15, 2026, around 10:00 AM IST, ParakeetAI froze in the middle of the session and stopped responding. In addition, the microphone and internal/system audio listening features were not working properly. The tool was unable to correctly capture or listen to the interview audio, which made it unreliable for the purpose I purchased it for.

I also tried to take screenshots as proof of the issue, but the problem was not clearly visible or captured in the screenshots. Since the issue involved the application freezing, not responding, and failing to detect audio, it was difficult to show the full problem through screenshots alone.

Issues Experienced

1. ParakeetAI froze during the interview

   • The platform became stuck in the middle of the session.

   • It stopped responding and did not continue working as expected.

   • This interrupted my interview workflow.

2. Application became unresponsive

   • After freezing, the tool did not recover properly.

   • I was unable to use it normally during the interview.

3. Microphone was not working properly

   • ParakeetAI did not consistently detect or process microphone input.

   • The tool failed to capture my audio correctly.

4. Internal/system audio listening was not working properly

   • ParakeetAI was not detecting or listening to internal/system audio correctly.

   • It could not properly capture the interviewer’s audio from the device.

   • Because of this, the responses were not useful, delayed, or not generated.

5. Issue was not visible in screenshots

   • I attempted to take screenshots to document the problem.

   • However, the freezing/audio detection issue was not clearly visible in the screenshots.

   • The issue appears to be related to real-time responsiveness and audio capture, which cannot be properly shown through a static screenshot.

Expected Behavior

ParakeetAI should remain stable during the full interview session. It should correctly detect microphone input and internal/system audio so that it can listen to the conversation and respond properly.

Actual Behavior

The platform froze, stopped responding, and failed to correctly capture microphone and internal/system audio during my interview on June 15, 2026, around 10:00 AM IST. As a result, I could not use the tool effectively during the live session.

I also attempted to capture proof using screenshots, but the issue was not visible in the screenshots because the problem involved freezing, unresponsiveness, and audio detection failure.

Steps to Reproduce

1. Start a ParakeetAI session for an interview.

2. Enable microphone access.

3. Enable internal/system audio listening.

4. Continue using the tool during the interview.

5. The tool freezes, becomes unresponsive, or fails to capture microphone/internal audio correctly.

6. Attempt to take screenshots of the issue.

7. The issue is not clearly visible in the screenshots because the main failure is related to real-time audio detection and application responsiveness.

Impact

This issue caused a major disruption during my interview on June 15, 2026, around 10:00 AM IST. Since ParakeetAI froze and the audio features did not work properly, I was unable to use the service for the purpose I purchased it for. The issue also could not be properly documented through screenshots, making it difficult to provide visual proof even though the problem occurred during actual use.

Device: Windows
Browser or app version: Chrome

I attempted to take screenshots, but the technical issue was not visible in the screenshots or in a screenrecording.

Best regards,
Edward