Weave Code
There There Cli Laravel Package
spatie/there-there-cli
A command-line tool for There There that lets you interact with the There There API from your terminal. Install it globally with Composer, log in per workspace profile, and manage tickets—list, show, reply, forward, and update—right from the CLI. Full docs at there-there.app.
A standalone CLI tool for the There There helpdesk.
Frequently asked questions about There There Cli
- How do I install and authenticate the There There CLI?
- Install it globally with composer global require spatie/there-there-cli and make sure Composer's global bin directory is on your PATH (composer global config bin-dir --absolute prints the path). Then run there-there login and paste the API token from there-there.app; credentials are written to ~/.there-there/config.json under a profile named after your workspace. Use there-there logout to remove credentials for the active profile, and rerun the same composer global require command to update later.
- Can I install spatie/there-there-cli inside my Laravel app to build a helpdesk?
- No. It is a standalone CLI built on Laravel Zero and shipped as a PHAR, not an in-app library or SDK, so there is nothing to import or inject into your application. It cannot satisfy an in-app helpdesk requirement; if you need to create or list tickets from application code, call the There There API over HTTP instead. The CLI belongs in the operations layer around your app: cron jobs, CI pipelines, runbooks and on-call tooling.
- Which Laravel and PHP versions does it support?
- Because it is a Laravel Zero application distributed as a PHAR, it is never loaded into your Laravel app, so your application's framework version is irrelevant. What matters is having a PHP runtime and Composer's global bin directory available in every environment where you run it, including containers and CI runners. Check the Packagist page for the current PHP requirement before pinning a version in an image.
- How do I run there-there non-interactively in CI or a container?
- You need PHP plus Composer's global bin on PATH in the image, which is a heavier footprint than a single static binary and awkward in slim containers. Authentication is the friction point: there-there login writes to ~/.there-there/config.json, so in CI you must either seed that file from your secret store or replay the login as a pipeline step. Fields can be passed inline (for example --field body="..."), which keeps commands scriptable and free of prompts.
- How do profiles work with multiple workspaces?
- Each there-there login --profile=name stores a separate set of credentials, and there-there profiles lists them. there-there use spatie switches the default profile, while adding --profile=ohdear to a single command targets a different workspace for that call only. That makes it practical to keep production and staging workspaces side by side without re-authenticating.
- How do I filter tickets when listing them?
- list-tickets accepts flags such as --q="refund request", --filter-search="billing" and --filter-created-after=2026-01-01 to narrow results. Other commands cover the rest of the API, for example show-ticket, reply-to-ticket, forward-ticket, add-note-to-ticket, update-ticket-status and update-ticket-assignee. Run there-there <command> --help to see the exact flags for a specific command.
- Is the JSON output stable enough to pipe into jq for reporting?
- Output is JSON and pipes cleanly into jq, but stdout purity is a convention rather than a documented contract — the 0.8.2 changelog records binary responses that were previously corrupted by console formatting. The response envelope also changed to a data wrapper in 0.5.0, so any parser needs a test around it. Validate the exact shape you depend on before building reporting on top of it.
- Will command names change between releases?
- Possibly. Command names are derived from the API's OpenAPI operationIds, so resyncing the spec renames commands — earlier releases renamed get-tickets-ticket to show-ticket and patch-company to update-company. The package is pre-1.0 with no SemVer guarantee, so a minor bump can silently break scripts referencing the old names. Pin the version and diff the changelog before upgrading.
- How do I create a ticket from my Laravel application code instead?
- You cannot do it through this package: it is a shell tool, so the only option would be shelling out to the binary, which drags a PHP runtime and a config file into your app's environment. Use a normal HTTP client against the There There API for in-app ticket creation, and keep the CLI for scheduled digests, escalation routing and other operational jobs.
- What are the maintenance and production risks of this package?
- Releases are cut manually and the PHAR in builds/ is what Composer installs, so the artifact is only as correct as the last human running the build script — version 0.8.0 shipped tagged with the previous PHAR and a stale API spec. Adoption signal is zero, with no stars or dependents, so there is no third-party battle-testing or community troubleshooting to fall back on. The mitigating factor is first-party ownership: Spatie maintains the CLI alongside There There itself, so it has a direct incentive to keep it aligned with the API. Ask the vendor about exit-code stability, 429 and 5xx retry behavior, and rate limits before depending on it in automation.
Weaver
How can I help you explore Laravel packages today?