Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src-tauri/Info.plist
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@
entirely and falls back to the .icns.
-->
<dict>
<key>NSMicrophoneUsageDescription</key>
<string>Allow command-line tools you run in VMark's integrated terminal to record audio from your microphone or other audio input devices.</string>
<key>CFBundleVersion</key>
<string></string>
<key>CFBundleIconName</key>
Expand Down
3 changes: 3 additions & 0 deletions src-tauri/sidecar-entitlements.plist
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<!-- Also used by the app bundle: terminal tools need Core Audio input access. -->
<key>com.apple.security.device.audio-input</key>
<true/>
<!-- Allow JIT compilation (required for V8/Node.js) -->
<key>com.apple.security.cs.allow-jit</key>
<true/>
Expand Down
15 changes: 15 additions & 0 deletions website/guide/terminal.md
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,21 @@ Standard shell shortcuts like `Ctrl+R` (reverse history search in zsh/bash) work

When the workspace root changes after the terminal is already running, idle sessions automatically `cd` to the new root. A session busy with a command (say, `vim` or `less`) is not interrupted: it changes directory once the command finishes, which needs [shell integration](#shell-integration) to detect. With the [workspace rail](/guide/workspace-rail) on, sessions that belong to a workspace keep their own directory.

## Audio input on macOS

Recording tools running in the integrated terminal may request microphone
permission under VMark's name. Allow access when macOS asks. If VMark is listed in
**System Settings → Privacy & Security → Microphone**, you can manage its access
there. If no prompt or entry appears, collect the recording tool's output and
macOS permission logs when reporting the issue. Permission is requested when a
tool accesses audio input, not simply when you open the terminal.

For virtual audio inputs such as BlackHole, permission alone does not establish
audio routing. Select the intended input in your recording tool, route audio to it, and verify
a short recording before a longer session. A growing audio file alone does not
confirm that sound was captured. VMark does not include a recorder or transcriber;
those commands are provided by tools you install separately.

## Not yet implemented

These are tracked but do **not** ship today. They are listed here because
Expand Down