hot key doesnt work on mac

[hololeo]

Ctrl+J (or any other combo) is not recognized at all by the app.

I gave the app permissions as well. this did not change anything

is there a log file to look at?

[LSXPrime]

Thanks for reporting this. While I expected there may be issues with macOS like Contextual Awareness or selected text capturing, I never thought it would be something fundamental like the hotkey—that's actually embarrassing, but I'm glad this appeared early.

Could you share the log file? It’s usually located at ~/.config/ProseFlow/logs/, where ~ is your home folder, or fallback to ~/Library/Application Support/ProseFlow/logs/.

And a side question: I know macOS requires a signed app to run. Was running unsigned binaries hard, or requiring developer options or permissions that prevent the average user from running it?

[advaitian]

Just skip the initial setup and open the application. The hot key will work after that. The only issue is during the initial setup steps, which you can skip.

Application works, but it does not log or show any history. Dashboard has everything 0.
Directory ~/.config/ProseFlow/logs/ or ~/Library/Application Support/ProseFlow/logs/ does not exist.

[LSXPrime]

@advaitian

Interesting—Technically, your app should store the database within the AppData folder, alongside the logs in the AppData path to run. Try running this PowerShell command to locate it:

[Environment]::GetFolderPath([Environment+SpecialFolder]::ApplicationData)

Inside that folder, look for a subfolder named "ProseFlow." It should contain both the database file and a "logs" directory. If not, search system-wide for files named proseflow-*.log or proseflow- to confirm the app’s presence.

[advaitian]

OS: macOS Sequoia
There is a log file ~/Library/Application Support/ProseFlow/logs/proseflow-202509.log
Dashboard or history are still shows nothing.

Errors in log:
2025-09-23 10:45:04.670 -07:00 [ERR] Hardware monitoring service failed to initialize.
System.Reflection.TargetInvocationException: Arg_TargetInvocationException
---> System.DllNotFoundException: Unable to load shared library 'MonoPosixHelper' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable:
dlopen(/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper.dylib, 0x0001): tried: '/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper.dylib' (no such file), '/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper.dylib' (no such file)
dlopen(MonoPosixHelper.dylib, 0x0001): tried: 'MonoPosixHelper.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OSMonoPosixHelper.dylib' (no such file), '/usr/lib/MonoPosixHelper.dylib' (no such file, not in dyld cache), 'MonoPosixHelper.dylib' (no such file)
dlopen(/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper.dylib, 0x0001): tried: '/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper.dylib' (fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper.dylib' (no such file), '/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper.dylib' (fat file, but missing compatible architecture (have 'i386,x86_64', need 'arm64e' or 'arm64'))
dlopen(libMonoPosixHelper.dylib, 0x0001): tried: 'libMonoPosixHelper.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibMonoPosixHelper.dylib' (no such file), '/usr/lib/libMonoPosixHelper.dylib' (no such file, not in dyld cache), 'libMonoPosixHelper.dylib' (no such file)
dlopen(/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper, 0x0001): tried: '/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper' (no such file), '/Applications/ProseFlow.app/Contents/MacOS/MonoPosixHelper' (no such file)
dlopen(MonoPosixHelper, 0x0001): tried: 'MonoPosixHelper' (no such file), '/System/Volumes/Preboot/Cryptexes/OSMonoPosixHelper' (no such file), '/usr/lib/MonoPosixHelper' (no such file, not in dyld cache), 'MonoPosixHelper' (no such file)
dlopen(/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper, 0x0001): tried: '/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper' (no such file), '/Applications/ProseFlow.app/Contents/MacOS/libMonoPosixHelper' (no such file)
dlopen(libMonoPosixHelper, 0x0001): tried: 'libMonoPosixHelper' (no such file), '/System/Volumes/Preboot/Cryptexes/OSlibMonoPosixHelper' (no such file), '/usr/lib/libMonoPosixHelper' (no such file, not in dyld cache), 'libMonoPosixHelper' (no such file)

at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InvokeWithManyArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
Exception_EndOfInnerExceptionStack
at System.Reflection.MethodBaseInvoker.InvokeWithManyArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at LibreHardwareMonitor.Hardware.OpCode.Open()
at LibreHardwareMonitor.Hardware.Computer.Open()
at ProseFlow.Infrastructure.Services.Monitoring.HardwareMonitoringService..ctor(ILogger`1 logger)

[LSXPrime]

The log error stems from the hardware monitoring feature attempting to use an Intel-specific component (MonoPosixHelper) on an ARM-based Mac. After investigating, I confirmed that MonoPosixHelper is not supported on the osx-arm64 platform. Until the hardware monitoring library (LibreHardwareMonitor) migrates to Mono.Unix, I'll need to exclude hardware monitoring from ARM64 (such as M1, M2, M3) macOS versions.

Dashboard or history are still shows nothing.

The dashboard data is stored in the database (History Table), not in logs, so as long as there are no database crashes, the data remains intact and logs are not needed.
The dashboard doesn’t update instantly—so to see recent changes, please switch to another screen (like Actions or any other view) and then return to the dashboard to refresh the display.

If the application is saving imported and downloaded models, or external Cloud API configurations, or Actions data, or General Settings, or ensuring that users are not asked to complete onboarding twice, or successfully performing actions (e.g., Proofread, Improve Writing, etc.), it should be recording the history and statistics to the database without any issue.

If no statics appear even after successful operations (e.g. Proofread, Improve Writing, etc.), could you open the database file using an SQLite3 editor such as SQLite Browser and check whether the History table contains any data?

[LSXPrime]

I just pushed a small commit that addresses the hotkey issues during onboarding, disables hardware monitoring on ARM64 macOS systems (with UI updates to reflect this), and fixes hotkey handling on non-US keyboards. If you'd like to test it from source, follow the "Building from Source" instructions in the README but run using dotnet run -f net8.0-macos.

To re-show the onboarding screen for testing, open the database file (~/Library/Application Support/ProseFlow/proseflow.db) in any SQLite3 editor like SQLite Browser, navigate to the General Settings table, set the IsOnboardingCompleted value to 0, and then close the application if it was running and start the app using the previous steps.

[advaitian]

New version having this issue:
Directory ~/.config/ProseFlow/logs/ and ~/Library/Application Support/ProseFlow/logs/ exist, but both are empty.

[LSXPrime]

Good morning,

I apologize for the delayed response — I wanted to ensure robust fallback implementations for the clipboard before finalizing the commit. After significant refactoring, I've now implemented three services (Avalonia → Native Shell → TextCopy) to reliably access the clipboard and retrieve selected text.

Could you please test the latest update, v0.2.0, to verify if the issue persists? You can update directly from the "About" screen within the app.

As a small adjustment, I've added a brief delay of approximately 200ms before copying the selected text, to allow the active window to regain focus after the floating menu window is closed.

And if you have a moment, I’d like to ask a side request that could potentially reduce the macOS binary size by up to 50%. The macOS builds currently include a nested or duplicated application bundle, as shown in the folder structure below.

My request is to download the macOS portable version, extract the nested ProseFlow.app from the base ProseFlow.app folder, and test running both versions independently to see if either works without the other.
While no online documentation mentions duplicated bundles, .NET appears to generate them automatically during the build process.

Thanks for your help!

└───ProseFlow.app
    └───Contents
        │   Info.plist
        │
        ├───MacOS
        │   │   ProseFlow (Main Executable)
        │   │   UpdateMac (Updater Executable)
        │   │   ProseFlow.dll (Main application library)
        │   │   ProseFlow.runtimeconfig.json
        │   │
        │   │   (Many .NET assemblies for Avalonia, Microsoft, etc.)
        │   │   (Many native .dylib libraries for .NET runtime, Skia, etc.)
        │   │
        │   ├───cs, de, es, fr, ... (Folders for localized resources)
        │   │
        │   ├───ProseFlow.app (A nested application bundle)
        │   │   └───Contents
        │   │       │   Info.plist
        │   │       │
        │   │       ├───MacOS
        │   │       │       ProseFlow (Executable)
        │   │       │
        │   │       └───MonoBundle
        │   │           │   (A large collection of .NET assemblies and .dylib files)
        │   │           │
        │   │           └───runtimes
        │   │               └───osx-x64
        │   │                   └───native
        │   │                           (Native libraries for LLamaSharp: libllama.dylib, etc.)
        │   │
        │   └───runtimes
        │       └───osx-x64
        │           └───native
        │                   (Duplicate native libraries for LLamaSharp)
        │
        └───Resources
                logo.icns

[advaitian]

With the updated version, the same issue persists. However, instead of reporting only "Processing..." , it reports for example, saying "Processing 'proofread'".

[LSXPrime]

1. Are you using a local provider? If so, please test with a cloud provider.
2. If you can run it from source, please add breakpoints to the following lines and report the point it reaches before stopping.

ProseFlow/ProseFlow.Infrastructure/Services/Os/Clipboard/ClipboardService.cs

Line 146 in 37e8fd2

return null;

ProseFlow/ProseFlow.Infrastructure/Services/Os/Clipboard/ClipboardService.cs

Line 168 in 37e8fd2

return false;

ProseFlow/ProseFlow.Infrastructure/Services/AiProviders/LocalProvider.cs

Line 35 in 37e8fd2

await _inferenceLock.WaitAsync(cancellationToken);

ProseFlow/ProseFlow.Infrastructure/Services/AiProviders/LocalProvider.cs

Line 49 in 37e8fd2

throw new InvalidOperationException(errorMessage);

ProseFlow/ProseFlow.Infrastructure/Services/AiProviders/LocalProvider.cs

Line 104 in 37e8fd2

stopwatch.Start();

ProseFlow/ProseFlow.Infrastructure/Services/AiProviders/LocalProvider.cs

Line 154 in 37e8fd2

return new AiResponse(

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 130 in 37e8fd2

return;

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 169 in 37e8fd2

_logger.LogInformation("Action '{ActionName}' completed in {ElapsedSeconds:F2}s.", request.ActionToExecute.Name, overallStopwatch.Elapsed.TotalSeconds);

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 184 in 37e8fd2

_trackerService.CompleteAction(trackedAction.Id, ActionStatus.Error, TimeSpan.FromSeconds(2));

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 348 in 37e8fd2

var primaryProvider = await GetProviderAsync(providerOverride, settings.PrimaryServiceType);

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 357 in 37e8fd2

return (response, primaryProvider, stopwatch.Elapsed.TotalMilliseconds);

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 368 in 37e8fd2

_logger.LogInformation("No fallback provider is configured.");

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 381 in 37e8fd2

return (response, fallbackProvider, stopwatch.Elapsed.TotalMilliseconds);

ProseFlow/ProseFlow.Application/Services/ActionOrchestrationService.cs

Line 389 in 37e8fd2

return null;

[advaitian]

Same Error for both Local and Cloud providers.