3 ms·

Just tried it. really cool, and a fun tech demo with rcli. I filed a bug report; not everything is loading properly when installed via homebrew. Quick request:

Just tried it. really cool, and a fun tech demo with rcli. I filed a bug report; not everything is loading properly when installed via homebrew. Quick request: unsloth quants; bit per bit usually better. Or more generally UI for huggingface model selections. I understand you won't be able to serve everything, but I want to mix and match! Also - grounding: "open safari" (safari opens, voice says: "I opened safari") "navigate to google.com in safari" (nothing happens, voice says: "I navigated to google.com") Anyway, really fun.

Tacite 8mo ago
How did you try it? You said on github it doesn't work.
- deleted 8mo ago
  [deleted]
- wlesieutre 8mo ago
  They said it didn't work installed from homebrew, so I assume they went back and did the curl | bash install option
  - Tacite 8mo ago
    This option didn't work either. I tried it. Also, the install script… installs Brew. So at the end, it's the same?
    - RayVR 8mo ago
      That’s hilarious
    - emmelaich 8mo ago
      Oh dear. if ! command -v brew &>/dev/null; then info "Installing Homebrew..." /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" eval "$(/opt/homebrew/bin/brew shellenv)" fi
      - sanchitmonga22 8mo ago
        Fair point. The install script shouldn't silently install Homebrew without explicit consent. We'll update it to detect when Homebrew is missing and prompt the user before installing anything beyond RCLI itself. In the meantime, if you already have Homebrew, you can install directly: brew tap RunanywhereAI/rcli https://github.com/RunanywhereAI/RCLI.git https://github.com/RunanywhereAI/RCLI.git brew install rcli rcli setup Or build from source if you prefer not to use either method: https://github.com/RunanywhereAI/RCLI#build-from-source https://github.com/RunanywhereAI/RCLI#build-from-source
- vessenes 8mo ago
  It loads after those errors. Tap space and talk to it.
blks 8mo ago
> "open safari" (safari opens, voice says: "I opened safari") "navigate to google.com in safari" (nothing happens, voice says: "I navigated to google.com") So you’re describing a core broken feature. Application breaking at easiest test.
- sanchitmonga22 8mo ago
  Fair criticism. The action executed on the LLM side but didn't translate to the correct macOS action, the model hallucinated success instead of routing to the open_url tool. This is a known limitation with small LLMs (0.6B-1.2B) doing tool calling. They sometimes confuse "I know what you want" with "I did it." Upgrading to a larger model improves tool-calling accuracy significantly. We're also working on verification, having the pipeline confirm the action actually succeeded before reporting back. Thats a fair expectation and we should meet it.
  - elpakal 8mo ago
    > This is a known limitation with small LLMs (0.6B-1.2B) doing tool calling. To me this is this nut to crack, wrt tool calling and locally running inference. This seems like a really cool project and I'm going to dive around a little later but if it's hallucinating for something as basic as this makes me think it's more of POC stage right now (to echo other sentiment here).
    - sanchitmonga22 8mo ago
      That's a fair read. Tool calling reliability with sub-4B models is genuinely the hardest unsolved problem in on-device AI right now. The inference engine (MetalRT) is production-grade, the pipeline architecture is solid, but the models at this size are still the weak link for complex tool routing. Larger model support (where tool calling is much more reliable) is next on the roadmap. Please stay tuned!
      - elpakal 8mo ago
        Sorry, I scrolled through some of the rest of the comments on this thread and can’t stay tuned.
sanchitmonga22 8mo ago
Thanks for trying it and for filing the bug, we're looking into the homebrew install issue. On unsloth quants: agreed, they're consistently better bit-for-bit. Adding broader quantization format support (including unsloth's approach) is on the roadmap. Right now MetalRT works with MLX 4-bit files and GGUF Q4_K_M, we want to expand that. On the grounding issue ("navigate to google.com" not actually navigating): you're right, that's a gap. The "open_url" action exists but the LLM doesn't always route to it correctly, especially with compound commands. Small models (0.6B-1.2B) have limited tool-calling accuracy, upgrading to Qwen3.5 4B via rcli upgrade-llm helps significantly. We're also improving the action routing prompts. Appreciate the detailed feedback, this is exactly what we need.

Tacite 8mo ago

How did you try it? You said on github it doesn't work.

deleted 8mo ago
[deleted]
wlesieutre 8mo ago
They said it didn't work installed from homebrew, so I assume they went back and did the curl | bash install option
- Tacite 8mo ago
  This option didn't work either. I tried it. Also, the install script… installs Brew. So at the end, it's the same?
  - RayVR 8mo ago
    That’s hilarious
  - emmelaich 8mo ago
    Oh dear. if ! command -v brew &>/dev/null; then info "Installing Homebrew..." /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" eval "$(/opt/homebrew/bin/brew shellenv)" fi
    - sanchitmonga22 8mo ago
      Fair point. The install script shouldn't silently install Homebrew without explicit consent. We'll update it to detect when Homebrew is missing and prompt the user before installing anything beyond RCLI itself. In the meantime, if you already have Homebrew, you can install directly: brew tap RunanywhereAI/rcli https://github.com/RunanywhereAI/RCLI.git https://github.com/RunanywhereAI/RCLI.git brew install rcli rcli setup Or build from source if you prefer not to use either method: https://github.com/RunanywhereAI/RCLI#build-from-source https://github.com/RunanywhereAI/RCLI#build-from-source
vessenes 8mo ago
It loads after those errors. Tap space and talk to it.

blks 8mo ago

> "open safari" (safari opens, voice says: "I opened safari") "navigate to google.com in safari" (nothing happens, voice says: "I navigated to google.com") So you’re describing a core broken feature. Application breaking at easiest test.

sanchitmonga22 8mo ago
Fair criticism. The action executed on the LLM side but didn't translate to the correct macOS action, the model hallucinated success instead of routing to the open_url tool. This is a known limitation with small LLMs (0.6B-1.2B) doing tool calling. They sometimes confuse "I know what you want" with "I did it." Upgrading to a larger model improves tool-calling accuracy significantly. We're also working on verification, having the pipeline confirm the action actually succeeded before reporting back. Thats a fair expectation and we should meet it.
- elpakal 8mo ago
  > This is a known limitation with small LLMs (0.6B-1.2B) doing tool calling. To me this is this nut to crack, wrt tool calling and locally running inference. This seems like a really cool project and I'm going to dive around a little later but if it's hallucinating for something as basic as this makes me think it's more of POC stage right now (to echo other sentiment here).
  - sanchitmonga22 8mo ago
    That's a fair read. Tool calling reliability with sub-4B models is genuinely the hardest unsolved problem in on-device AI right now. The inference engine (MetalRT) is production-grade, the pipeline architecture is solid, but the models at this size are still the weak link for complex tool routing. Larger model support (where tool calling is much more reliable) is next on the roadmap. Please stay tuned!
    - elpakal 8mo ago
      Sorry, I scrolled through some of the rest of the comments on this thread and can’t stay tuned.

sanchitmonga22 8mo ago

Thanks for trying it and for filing the bug, we're looking into the homebrew install issue. On unsloth quants: agreed, they're consistently better bit-for-bit. Adding broader quantization format support (including unsloth's approach) is on the roadmap. Right now MetalRT works with MLX 4-bit files and GGUF Q4_K_M, we want to expand that. On the grounding issue ("navigate to google.com" not actually navigating): you're right, that's a gap. The "open_url" action exists but the LLM doesn't always route to it correctly, especially with compound commands. Small models (0.6B-1.2B) have limited tool-calling accuracy, upgrading to Qwen3.5 4B via rcli upgrade-llm helps significantly. We're also improving the action routing prompts. Appreciate the detailed feedback, this is exactly what we need.