npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

ur-nexus-desktop

v1.0.7

Published

Professional local-first desktop coding agent with BYOK cloud providers and Ollama support

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

maitham88maitham88

Keywords

Readme

UR Nexus Desktop

A standalone macOS Electron app for UR-Nexus. It installs and runs alone with no global ur CLI dependency, no subscription CLI provider, and bundles the internal @ur/agent-runtime package.

Install from npm

UR Nexus Desktop is published as ur-nexus-desktop and includes its own Electron runtime. No API key is bundled: each user chooses a provider and adds, replaces, or removes their own credentials in Settings.

npm install --global --allow-scripts=node-pty ur-nexus-desktop
ur-nexus-desktop

Recent npm versions require explicit approval before global packages may run native install scripts. UR-Nexus needs only node-pty's terminal binding; the command above approves that package alone. Electron 43 no longer needs an install lifecycle script. This does not enable arbitrary dependency scripts. See npm's allow-scripts documentation.

Use ur-nexus-desktop --version to verify the installed release. Ollama users can select any model installed on their own Ollama server and may change the server URL at any time.

macOS development

Requires Bun and macOS 12+. Native modules are rebuilt for the running Electron ABI automatically when packaging.

bun install
bun run dev

bun run dev builds the main and preload scripts, starts the Vite renderer dev server, and launches Electron against http://localhost:5173.

macOS build

bun run build

Produces:

  • dist/main/main.mjs
  • dist/preload/preload.cjs
  • dist/renderer/*

macOS package

bun run package:mac

Generates in dist/:

  • UR Nexus Desktop-x.x.x-arm64.dmg (Apple Silicon)
  • UR Nexus Desktop-x.x.x-arm64.zip (Apple Silicon)
  • UR Nexus Desktop-x.x.x-x64.dmg (Intel)

Universal binaries are produced when electron-builder runs on an Apple Silicon Mac with both architectures available. Set electron-arch or use electron-builder --universal if needed.

The native terminal module (node-pty) is unpacked from the ASAR so it loads at runtime.

macOS install

Download the correct .dmg from the latest official GitHub release:

  • arm64 for Apple Silicon Macs (M1, M2, M3, M4, or newer)
  • x64 for Intel Macs

If you are unsure, run uname -m in Terminal and choose the matching build.

Open the DMG and drag UR Nexus Desktop to /Applications. It then appears in Finder, Launchpad, and Spotlight like a normal Mac app. On first launch the composer is ready immediately in General chat; choosing a project or attaching files is optional.

Temporary unsigned-build step

The current GitHub build is not yet signed or notarized because the project does not yet have an Apple Developer Program subscription. macOS can therefore show “UR Nexus Desktop is damaged and can't be opened.”

If—and only if—you downloaded the app from the official GitHub release linked above, remove quarantine from this app and open it:

xattr -dr com.apple.quarantine "/Applications/UR Nexus Desktop.app"
open "/Applications/UR Nexus Desktop.app"

This command affects only the UR Nexus Desktop application bundle. It does not disable Gatekeeper for the rest of the Mac. Signed and notarized releases will remove the need for this temporary step after Apple Developer enrollment.

As an alternative to the DMG, install and start the npm package from Terminal:

npm install --global --allow-scripts=node-pty ur-nexus-desktop
ur-nexus-desktop

macOS Keychain secret storage

API keys are stored by the main process in the macOS Keychain via the existing providerCredentials module. Keys are never written to project files, history, transcripts, or exported reports. The renderer receives only hasKey/keySource booleans, never the key value.

Provider setup

Open Settings, pick a provider, enter a model, and save. Click Save & test to verify reachability.

In chat, type / to open the complete terminal-agent command palette. The catalog is loaded from the shared runtime and includes built-ins, project skills, plugins, aliases, and workflows. Continue typing to filter, use ↑/↓ to navigate, Tab or Enter to select, and Esc to close it.

OpenAI API setup

  1. Choose OpenAI API.
  2. Paste your API key.
  3. Enter a model (e.g. gpt-4o).
  4. Click Save settings then Set active.

Anthropic API setup

  1. Choose Claude API.
  2. Paste your Anthropic API key.
  3. Enter a model (e.g. claude-3-5-sonnet-20241022).
  4. Click Save settings then Set active.

OpenRouter API setup

  1. Choose OpenRouter.
  2. Paste your OpenRouter API key.
  3. Enter a model (e.g. openai/gpt-4o).
  4. Click Save settings then Set active.

Ollama Local setup

  1. Install and start Ollama on your Mac.
  2. In Settings choose Ollama Local.
  3. Click Discover to list downloaded models.
  4. Select a model and click Set active.

The app does not install Ollama for you. If Ollama is not running, Local mode will not connect; switch to an API provider or Ollama Cloud.

Ollama Network setup

  1. Choose Ollama Network.
  2. Enter the base URL (e.g. http://ollama.local:11434).
  3. Click Test connection.
  4. Click Set active.

Ollama Cloud/API setup

  1. Choose Ollama Cloud/API.
  2. Enter the managed base URL (e.g. https://ollama.example.com).
  3. Click Test connection.
  4. Click Set active.

MCP connector setup

MCP servers can be added in the Connectors panel. The app supports stdio, sse, http, and ws transports. Connector tools are exposed to runs and gated by the same approval model as built-in tools.

Security model

  • Electron secure context defaults: contextIsolation: true, nodeIntegration: false, sandbox: true.
  • All file system and shell operations are scoped to the opened project or an isolated worktree.
  • Risky actions pause execution and require user approval; denied actions do not run.
  • Every approval decision is logged to ~/Library/Application Support/UR Desktop/desktop/approval-log.jsonl.
  • macOS-sensitive paths (Desktop, Documents, Downloads, .ssh, .gnupg, Library, Keychain access patterns, and external drives) are protected.
  • Reading outside the selected project, writing/deleting outside the project/worktree, destructive shell commands, package installs, network commands, git push, file deletion, MCP side-effect tools, external app/URL opening, long-running commands, and provider key replacement require explicit approval.
  • Project-level safety policy lives in .ur/safety-policy.json and can be edited from the Settings page.

Auto-update

The renderer checks the repository's latest public GitHub release through the GitHub Releases API. Update checks do not require a token and do not download or execute anything automatically.

Deep links

The app registers the ur-desktop:// protocol. On launch it handles open-url and second-instance argv payloads. Pending deep links are stored for the renderer to consume after load.

macOS signing and notarization

electron-builder.yml includes:

  • hardenedRuntime: true
  • entitlements: assets/entitlements.mac.plist

electron-builder enables notarization when a complete supported Apple credential set is present in the environment. After joining the Apple Developer Program, configure a Developer ID Application certificate and these notarization variables before packaging:

export [email protected]
export APPLE_APP_SPECIFIC_PASSWORD=xxxx-xxxx-xxxx-xxxx
export APPLE_TEAM_ID=ABCD123456

Packaging works without these credentials for local testing and the current temporary unsigned release. Public trusted macOS distribution requires a valid Developer ID Application certificate and Apple notarization credentials; they are intentionally never stored in the repository or npm package.

Troubleshooting

  • Blank window: check that dist/renderer/index.html exists after bun run build. In dev mode ensure Vite is running on port 5173.
  • Electron runtime missing after npm install: reinstall with npm install --global --allow-scripts=node-pty ur-nexus-desktop. Do not use the broad --dangerously-allow-all-scripts option.
  • Type errors: run bun run typecheck from apps/desktop.
  • Tests: run bun test from apps/desktop.
  • Packaging fails on native modules: run bun run build first so electron-builder can locate rebuilt binaries; ensure node-pty has a prebuild for the target Electron ABI.
  • macOS reports the app is damaged: follow the temporary unsigned-build step above only for a download from the official release page.
  • Signing/notarization fails: verify APPLE_ID, APPLE_APP_SPECIFIC_PASSWORD, APPLE_TEAM_ID, and the Developer ID certificate.