Tinycast: Native macOS launcher with clipboard and shortcut workflows
A native macOS 26 launcher that puts Raycast extensions, clipboard history, and window actions in one SwiftUI palette.
GitHub abue-ammar/tinycast Updated 2026-09-17 Branch main Stars 5.6K Forks 267
Swift 6.0 macOS launcher Raycast extensions macOS 26+

🧭 Decision Guide

Why trending now: It may be gaining attention because the README combines native SwiftUI/AppKit implementation, no Electron, no telemetry, under-100 MB RAM usage, and Raycast extension support; the latest release is Tinycast Beta 0.11.2-beta.97 and it gained 1,179 stars in one day, but the materials do not prove a specific cause.

Try it if you

  • You use Apple silicon with macOS 26 and want one Global hotkey for apps, files, and shell commands.
    The README Install section lists Apple silicon on macOS 26+, while Features lists Global hotkey, App launcher, and Custom commands.
  • You already have Raycast extensions or Raycast settings and want native SwiftUI rendering.
    The README says it “runs real Raycast extensions, rendered as native SwiftUI,” and lists Backup and import in Features.
  • You need searchable text and image Clipboard history plus Calculator conversions from the same palette.
    The README Features section lists Clipboard history and Calculator, including text, images, units, live currency, and crypto conversions.
  • You want one tool for window layouts, Apple Shortcuts, and Quick Actions.
    The README Features section lists 34 Rectangle-style actions, Apple Shortcuts, and Quick Actions.

Skip it if you

  • Your device runs Windows, Linux, or a macOS version below 26 without relying on the still-listed macOS 15 build.
    The README describes the project as a macOS app; Install lists macOS 26 and macOS 15 Sequoia, with macOS 15 marked no longer maintained.
  • Your organization cannot accept AGPL-3.0 or needs the repository metadata's Other license classification to be unambiguous.
    The README License section and badge say AGPL-3.0, while the project metadata records Other.
  • You cannot grant Accessibility permission but need Snippets expansion or cross-application pasting.
    The README Permissions section says Accessibility is required for cross-app pasting and is the only permission needed for snippet keyword expansion.
  • You require a stable release and will not accept Beta 0.11.2-beta.97.
    Project release data identifies Tinycast Beta 0.11.2-beta.97 as the latest version, while the README provides a separate @beta install.

Requirements

  • macOS 26 or later; Apple silicon uses brew install --cask tinycast, while Intel uses brew install --cask tinycast-universal.
  • Run brew trust --tap abue-ammar/tinycast and brew tap abue-ammar/tinycast first.
  • Using Snippets or cross-app pasting requires permission in System Settings → Privacy & Security → Accessibility.
  • The project uses Swift 6.0, SwiftUI, and AppKit; the README states that it has no third-party dependencies.

First step (verbatim from README)

brew trust --tap abue-ammar/tinycast   # required for third-party taps

Watch out

  • When installing from a DMG, Tinycast is self-signed and requires xattr to clear the quarantine flag.
    The README Install section for Releases provides the xattr -dr com.apple.quarantine command.
  • Snippets are disabled by default, and Accessibility permission is required before enabling keyword expansion.
    The README Permissions section says Snippets ship disabled and explains the Accessibility requirement.
  • Homebrew checks the architecture and refuses the wrong package, so Apple silicon and Intel commands must not be mixed.
    The README Install section lists tinycast and tinycast-universal separately and says Homebrew refuses the wrong version.
  • AI chat is disabled by default and requires your own key or an installed AI account.
    The README Features section says AI chat uses an own key or installed AI account and that every AI feature is off by default.

Alternatives

  • Raycast：Choose it when you depend more on Raycast's native workflows, existing extension ecosystem, or settings than on migrating to Tinycast's SwiftUI rendering.
    README Features section and the Raycast extensions, Backup and import statements

Not stated in the README

  • The README does not specify supported AI services, account types, or data-transfer boundaries.
  • The README does not state Raycast extension compatibility versions, API coverage, or known incompatibilities.
  • The README provides no changelog, crash rate, or rollback procedure for Beta 0.11.2-beta.97.
  • The README does not explain Clipboard history retention, storage location, encryption, or capacity limits.
  • The README does not explain the legal reason for the mismatch between repository metadata Other and AGPL-3.0 in the README.
  • The README does not state the planned support range beyond macOS 26.

💡 Deep Analysis

6
No I use an Intel Mac on macOS 15 Sequoia and mainly need clipboard history, snippets, and window management. Is Tinycast suitable as my long-term primary launcher now?
For: An Intel Mac user still running macOS 15 Sequoia who needs clipboard history, snippets, and window management but cannot accept an unmaintained OS version

No, not as a long-term primary launcher: although the README still provides a macOS 15 Sequoia package, it explicitly labels that version “no longer maintained.”

  • The main release requires macOS 26 or later, showing that current maintenance is focused on the newer system.
  • Sequoia uses the tinycast-sequoia cask, which may support a transition period but does not imply continued feature, compatibility, or security updates.
  • Your required capabilities are present: clipboard history supports text and images, Snippets support dynamic placeholders, arguments, and nested references, and window management provides 34 actions.
  • Those capabilities depend on macOS Accessibility, Spotlight, window, and system APIs; the README gives no long-term guarantee for their behavior or maintenance on the older OS.
  • README badge: macOS 26 or later
  • Install: macOS 15 Sequoia (no longer maintained)
  • Features: Clipboard history; Snippets; Window management — 34 Rectangle-style actions
  • Permissions: Accessibility
brew install --cask tinycast-sequoia
Not stated in the README：The README does not state how long the Sequoia build will be maintained or list known OS-version compatibility defects.；The README does not state whether settings, permissions, and clipboard data migrate completely after upgrading from macOS 15 to macOS 26.
No We manage multiple macOS 26 devices and want centralized Tinycast deployment, auditing of hotkeys and clipboard workflows, and shared team configuration. Do the AGPL-3.0 license and current project capabilities support this organizational setup?
For: A macOS team integrating Tinycast into an internal toolchain, using an AGPL-3.0 project while requiring team policy, auditing, and cross-device synchronization

No, not as a direct organizational workflow platform: the project offers local configuration import and export, but the README provides no centralized management, auditing, team policy, or cross-device synchronization.

  • Tinycast is a native local macOS app; configuration is described as “export your settings to a file, or import your setup from Raycast,” not as an organization-wide configuration service.
  • Clipboard history, snippets, hotkeys, and Accessibility permissions are tied to individual devices, and the README mentions no administrator console or audit log.
  • The project uses AGPL-3.0. If an organization modifies, integrates, and redistributes it, the relevant source and distribution obligations must be handled under that license rather than treated like an ordinary closed-source dependency.
  • Self-signed DMG installation, beta releases, and external AI accounts further expand enterprise deployment and compliance scope.
  • License: AGPL-3.0
  • Features: Backup and import — export your settings to a file, or import your setup from Raycast
  • Project insight: no centralized management, team policy, auditing, organizational deployment, or cross-device synchronization
  • Install: Tinycast is self-signed; latest_release = v0.11.2-beta.97
Not stated in the README：The README does not state whether MDM, PKG deployment, centralized configuration files, or enterprise identity authentication are supported.；The README does not define the exact compliance boundary for internal modifications that are not redistributed; legal review is still required.
Yes On Apple silicon and macOS 26, I switch apps, move windows between displays, operate Spaces, and run shell commands every day. Can Tinycast unify these actions behind one global hotkey?
For: An advanced Apple silicon user on macOS 26 who frequently manages windows, Spaces, displays, and custom shell commands and wants one global entry point

Yes: the README explicitly combines a global palette, window management, and custom commands into one searchable and hotkey-driven workflow.

  • The global hotkey summons the palette from anywhere, while per-app hotkeys can directly focus or hide a selected application.
  • Window management provides 34 Rectangle-style actions, including halves, quarters, thirds, resizing, display moves, fullscreen, and Spaces operations.
  • Custom commands run named shell commands through fuzzy search or their own global hotkeys; Quicklinks can also wrap URLs, files, and deeplinks.
  • File search uses user-selected folders and Spotlight without maintaining its own index, so Tinycast is an action entry point rather than an independent full-disk index.
  • Features: Global hotkey — one shortcut summons the palette from anywhere
  • Features: Window management — 34 Rectangle-style actions
  • Features: Custom commands — run named shell commands through fuzzy search or their own global hotkeys
  • Features: Search Files — through Spotlight, with no index of our own
brew install --cask tinycast
Not stated in the README：The README does not specify compatibility of window actions with every third-party app or special window type.；The README does not describe environment variables, timeouts, error reporting, or permission handling for custom shell commands.
It depends I need text and image clipboard history, cross-application pasting, grammar correction, and translation, but my company does not want content sent to AI services by default. Does Tinycast fit my resource and privacy constraints?
For: A developer on a managed Mac who values privacy and low resource usage, needs clipboard history and cross-app text actions, and does not want AI enabled by default

It depends: Tinycast fits the default-off AI, no-telemetry, and native low-resource goals, but your organization must still approve clipboard retention, Accessibility access, and external AI data flows.

  • The README targets “under 100 MB of RAM” and explicitly states “no telemetry” and “zero third-party dependencies.”
  • Clipboard history stores and searches text and images and can paste them back into the current app, so sensitive data enters local history; the README does not define retention periods or centralized deletion controls.
  • AI chat and Quick Actions are off by default and can use your own key or an installed account, but the project does not control what enabled services receive or charge for.
  • Cross-application paste and text actions require Accessibility permission, which may be restricted on managed devices.
  • Project introduction: under 100 MB of RAM; no telemetry; zero third-party dependencies
  • Features: Clipboard history — text and images, searchable, pasted back into the app you were using
  • Features: AI chat — use your own key or an installed AI account; off out of the box
  • Permissions: Accessibility — needed when Tinycast pastes or expands text into another app
brew install --cask tinycast
Not stated in the README：The README does not specify clipboard retention duration, encryption, automatic cleanup, or administrative policy controls.；The README does not state whether MDM can centrally disable AI, clipboard, or Accessibility features.
Yes I use an Intel Mac with macOS 26 and want to submit a feature PR to this Swift 6, SwiftUI, and AppKit project. If I add a launcher capability, do Tinycast's contribution rules fit my situation?
For: A macOS developer on an Intel Mac running macOS 26 who plans to modify the Swift 6 project and submit a PR under its memory budget and approval workflow

Yes, provided that your change is approved first and can satisfy the project’s memory and visual-validation requirements.

  • The core stack is Swift 6 with SwiftUI and AppKit, and the README points contributors to dedicated build documentation, making it suitable for native macOS feature work.
  • The contribution rules state, “Open an issue before you write code — this is mandatory”; a PR that does not close an approved issue is automatically closed, except for documentation-only fixes.
  • CONTRIBUTING.md covers the “memory budget every PR is held to,” and visual changes require a before/after video, both directly relevant to new palette actions, window features, or UI changes.
  • Intel on macOS 26 has a dedicated installation package, but the README does not specify the complete Xcode, SDK, and signing environment required for development.
  • README: Swift 6.0; SwiftUI and AppKit; Building from source
  • Contributing: “Open an issue before you write code — this is mandatory”
  • Contributing: the memory budget every PR is held to; the before/after video requirement for visual changes
  • Install: Intel, macOS 26 — brew install --cask tinycast-universal
brew install --cask tinycast-universal
Not stated in the README：The README does not provide the exact Xcode version, build commands, or test commands from docs/development.md.；The README does not publish the precise memory limit or performance benchmark for each PR type.
It depends I use Apple silicon with macOS 26 and already rely on Raycast extensions, Apple Shortcuts, global hotkeys, and saved configuration. Can Tinycast become my main entry point without rebuilding my workflow?
For: A productivity user on Apple silicon and macOS 26 who already relies on Raycast extensions and Apple Shortcuts and wants to move to a native launcher

It depends: Tinycast supports native Raycast extension execution and configuration import, but the README does not promise identical compatibility for every extension.

  • It says “Raycast extensions — run the ones you already have natively, rendered as SwiftUI” and supports exporting settings or importing a Raycast setup.
  • Apple Shortcuts can be searched, run, aliased, and assigned global hotkeys, which helps centralize existing automation.
  • The app uses SwiftUI and AppKit with zero third-party dependencies, so it does not require an Electron runtime; however, extensions that depend on Raycast-specific APIs may behave differently.
  • The current release is v0.11.2-beta.97, so migration behavior is still affected by beta status.
  • Features: Raycast extensions — run the ones you already have natively, rendered as SwiftUI
  • Features: Backup and import — export your settings to a file, or import your setup from Raycast
  • Features: Apple Shortcuts — search and run the shortcuts you built in the Shortcuts app
  • Project data: latest_release = v0.11.2-beta.97
brew trust --tap abue-ammar/tinycast   # required for third-party taps
Not stated in the README：The README does not list which Raycast APIs are supported or unsupported.；The README does not state whether import covers every hotkey, snippet, extension permission, or account setting.

✨ Highlights

  • Built natively with SwiftUI and AppKit, with zero third-party dependencies and no Electron
  • Runs Raycast extensions natively and renders them with SwiftUI
  • The README promises under 100 MB RAM usage and keeps AI features off by default
  • Includes 34 Rectangle-style window management actions
  • The latest release is Tinycast Beta 0.11.2-beta.97, so it remains in beta

🔧 Engineering

  • Use a global hotkey to open a palette for fuzzy-searching apps, files, and commands
  • Clipboard history searches text and images and pastes them back into the current app
  • Calculator handles math, unit, live currency, and crypto conversions
  • It can import Raycast settings and run existing Raycast extensions
  • Apple Shortcuts, Quicklinks, and shell custom commands can all receive hotkeys
  • Notes provides a floating editor backed by searchable Markdown files

⚠️ Risks

  • The README requires macOS 26+, while the macOS 15 Sequoia build is marked unmaintained
  • Snippets and cross-app pasting require Accessibility permission
  • DMG installs from Releases require manually clearing the quarantine flag for the self-signed app
  • Repository metadata says Other, while the README and LICENSE identify AGPL-3.0
  • The latest release is Beta 0.11.2-beta.97, and the README gives no stability guarantee

👥 For who?

  • Developers on macOS 26 and Apple silicon who prefer native Swift applications
  • Users with Raycast extensions who want native SwiftUI rendering
  • Power macOS users needing Clipboard history, Apple Shortcuts, and 34 window actions
  • Individual users willing to grant Accessibility permission and accept AGPL-3.0