Download the PHP package the-shit/music without Composer

On this page you can find all versions of the php package the-shit/music. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package music

Your codebase has a soundtrack

Every commit in this repo carries the Spotify track that was playing when the code was written. A git hook injects it. CI enforces it. No music, no merge.

The byproduct is the vibes page — an auto-generated, living soundtrack of the entire codebase. Every song that was playing when every line was written, regenerated on every push to master.

Docs · Vibes · Commands · MCP

How the soundtrack happens

  1. You listen — Spotify plays while you code, like it already does.
  2. The hook captures — a pre-commit hook asks the CLI what's playing and appends the track URL to your commit message.
  3. CI enforces — the Vibe Check gate scans every commit for a Spotify URL. No music, no merge.
  4. The vibes page regenerates — every push to master rebuilds the soundtrack of the whole repo.

It's enforced by the same pipeline as PHPStan and test coverage. Music is a CI gate here, not a gimmick.

On the Omarchy bar

Chip on the bar: now-playing, play/pause. Popup: skip, chill / flow / hype. Not a second Spotify client — it shells out to the spotify binary you already installed.

the-shit/omarchy-music. Requires this CLI on PATH plus spotify login. Stock omarchy.media stays.

Quick Start

That's it. The hook and CI gate are wired up per-repo — see CONTRIBUTING.md.

The Premium Player

spotify player:premium — a full php-tui player in your terminal. Album art rendered as ANSI, mood-aware theming, a search palette with play-now and queue actions, playlist browsing, and a queue peek. It's the player a vibes-enforced codebase deserves.

(The classic spotify player TUI is still there if you want something lighter.)

And it's a full Spotify CLI

The soundtrack is enforced, but the day-to-day tooling carries its weight too: 30+ commands, 12 MCP tools, mood-aware autopilot, event-driven integrations. Every feature is a layer you opt into — nothing assumes anything else is running.

Layer What it does Required?
CLI commands Play, pause, skip, queue, search, volume, shuffle, repeat Just this
Premium player php-tui player with art, mood theming, search palette spotify player:premium when you want it
MCP server 12 tools for AI assistants (Claude, etc.) to control Spotify Configure if you use AI tools
Daemon Headless Spotify Connect speaker via spotifyd Install if you want background playback
Media bridge macOS Control Center + media keys via native Swift Install if you want media key control
Autopilot Background queue auto-refill with mood presets Install if you want hands-off listening
Slack integration Share now-playing to Slack channels Set up if you use Slack
Webhooks Forward playback events to any URL with HMAC signing Configure if you want event-driven automation
Event streaming JSON Lines event bus for track changes, state transitions Enable if you're building on top of this

See the full command reference for all 32 commands.

Why This Instead Of...

spotify_player / ncspot / spotatui — Great TUI players. But they only play music. No commit soundtrack, no MCP server, no queue intelligence, no integrations. If you just want a terminal UI, those are solid. If you want Spotify as composable infrastructure — and your git history to have a soundtrack — this is it.

Standalone MCP servers — There are a handful on Smithery/GitHub. Most are weekend scripts with 3-5 tools and no maintenance. This is a real application with 12 MCP tools, 2 resources, battle-tested against Spotify's API deprecations, and actively maintained.

The Spotify desktop app — 800MB Electron app. This is 30 commands in a single binary.

MCP Server

This CLI doubles as an MCP server — AI assistants like Claude can control your Spotify directly. 12 tools for playback, queue, search, and discovery.

See the MCP setup docs for Claude Desktop, Claude Code, and OpenCode configuration.

Mood-Aware Queue

Built-in mood presets that queue tracks matching an energy profile. Each uses Spotify's audio feature targeting with smart deduplication against your queue and recent history.

Autopilot watches for track changes and auto-refills the queue when it drops below a threshold. Supports moods: chill, flow, hype, focus, party, upbeat, melancholy, ambient, workout, sleep.

macOS Services

Three optional background services, each managed via launchd with auto-restart and logging.

spotifyd — headless Spotify Connect speaker:

On Arch, install enables a systemd user unit aimed at ~/.config/spotify-cli/spotifyd.conf. It restarts with PipeWire. spotify daemon with no arguments lists the speaker verbs.

Swift Media Bridge — Control Center + media keys:

Autopilot — background queue auto-refill:

Service LaunchAgent RunAtLoad KeepAlive Logs
spotifyd com.spotify-cli.spotifyd Yes Yes ~/.config/spotify-cli/spotifyd.log
media-bridge com.theshit.media-bridge Yes Yes ~/.config/spotify-cli/media-bridge.log
autopilot com.theshit.autopilot No (on-demand) Yes ~/.config/spotify-cli/autopilot.log

Integrations

Slack — share now-playing to a channel:

Webhooks — forward events with HMAC signing:

Event streaming — the watch command emits JSON Lines events (track.changed, playback.paused, playback.resumed, etc.) that you can pipe anywhere:

Contributing

PRs welcome. Pick an issue, ship it, CI handles the rest.

CI runs three automated gates on every PR — no manual review bottleneck:

Gate What it checks
PHPStan Static analysis at level 5 (type safety, param mismatches)
Sentinel Gate Test coverage ≥ 50%
Vibe Check Every commit has a Spotify track URL

All must pass. See CONTRIBUTING.md for setup.

Requirements

License

MIT


All versions of music with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
illuminate/http Version ^12.17
laravel-zero/framework Version ^12.0
laravel/ai Version ^0.1
laravel/mcp Version ^0.5.9
laravel/prompts Version ^0.3
php-tui/php-tui Version ^0.2.1
the-shit/vector Version ^0.2.1
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package the-shit/music contains the following files

Loading the files please wait ...