Agents In Use
What’s new todayLast update
160 use cases added today

How to use Claude to package an offline Mac translator

Claude packaged a working offline Mac translator into a DMG. The author reported poorer responsiveness in the packaged app and several unresolved audio and runtime issues.

Source published news.ycombinator.comAgent: Claude
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Package [offline Mac translator project] into a macOS DMG using its existing [WebRTC VAD, whisper.cpp and llama.cpp setup]. Explain the packaging steps and any configuration changes. Provide instructions for comparing the packaged app with the working terminal version.

Evidence at a glance

Sourced account
Source poster / publisher
GlitchyBlep
Original account
Read the source ↗
Published
Source link checked
Reported result
The terminal translator worked and Claude produced a runnable DMG, but the packaged app was less responsive and several runtime issues remained unresolved.
Human involvement
The author ran both versions, observed responsiveness and synchronization problems, and requested outside optimization advice.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. Build an offline translator using WebRTC VAD, whisper.cpp and llama.cpp.
  2. Use an unnamed AI agent to work through CMake flags for Metal support.
  3. Run the translator as a Python script from the terminal.

The author built an offline translator for a Mac using WebRTC VAD, whisper.cpp for audio and a 1.8B model through llama.cpp for translation. The application translated system audio or microphone input and saved timestamped logs. Running the raw Python script from a terminal worked, with latency described as mostly sentence-by-sentence.

Setup was a major obstacle. The author encountered more than 14 compilation errors while trying to install whisper-cpp-python with Metal support. An unnamed AI agent helped work through CMake flags until the installation worked, although the author said they still did not fully understand the fix.

They then used Claude to package the application into a macOS DMG. The packaged application ran, but felt noticeably less smooth and responsive than the terminal version. Other unresolved issues included a possible memory leak, startup audio/text synchronization and occasional buffering that released several translated sentences together. The author open-sourced the code and requested optimization advice.

Who it's for: developers experimenting with local translation tools who can investigate build problems and compare packaged behavior with terminal execution.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Hacker News · GlitchyBlep

Frequently asked questions

Did Claude fix the Metal installation errors?

The author credits an unnamed AI agent with helping adjust CMake flags. Claude is specifically credited with packaging the application into a DMG.

Was the packaged translator fully smooth?

No. It ran, but the author found it less smooth and responsive than the raw Python script and did not know why.

More details

Remaining steps

  1. Use Claude to package the application into a macOS DMG.
  2. Compare packaged responsiveness with terminal execution and share unresolved issues.

About this account

Claude handled DMG packaging; a separate unnamed agent assisted with build configuration troubleshooting.

Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=47538105. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.

Credit: GlitchyBlep on Hacker News

Source published

Added to Agents In Use

Source checked

Tools and topics

Claude · WebRTC VAD · whisper.cpp · llama.cpp · CMake

macOS · Offline translation · Packaging

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.