Ai Mate Laravel Package

Product Decisions This Supports

• Standardize the AI-tooling layer vs. build bespoke glue. symfony/ai-mate v0.14.0 ships a maturing CLI surface (skills:install, tools:list, tools:inspect, tools:call) for exposing application capabilities to AI agents. The decision this informs: adopt a package-provided tool registry instead of hand-rolled scripts per team.
• Build vs. buy on developer-experience plumbing. This release is almost entirely DX polish — per-skill status reporting, argument visibility in tools:list, error messages that point at tools:inspect, pretty-output that no longer pads to the widest column and auto-falls back to JSON for large results. That is exactly the low-differentiation work we should not own.
• Roadmap sequencing and pilot timing. v0.14.0 contains no breaking changes and no deprecations — it is incremental hardening. That makes it a low-risk candidate for a scoped pilot now, while keeping us aware the package is still pre-1.0.
• Onboarding and support-cost reduction. The new per-skill status table in skills:install directly reduces "did the install actually work?" support load, and the tools:call → tools:inspect error routing shortens the debugging loop for new adopters.
• Operational correctness as a release gate. Three fixes matter for go-live confidence: symfony/dotenv is now a hard requirement so mate.env_file works out of the box; MATE_DEBUG_LOG_FILE resolves against the project root and accepts absolute paths; and has_api_key no longer reports true for unset env vars. The last one is a false-positive credential signal — a real blocker for any team gating features on key presence.
• Internationalization hygiene. Preserving non-ASCII characters when init rewrites composer.json avoids silent metadata corruption for teams with localized package descriptions or author names.
• CI and log ergonomics. Unpadded output and JSON fallback for oversized results make CLI output cheaper to parse, diff, and archive in CI — relevant if we plan to script around tools:call rather than read it by eye.

When to Consider This Package

Adopt when:

• You are a PHP/Symfony application team wanting to expose internal capabilities as AI-callable tools with an inspectable registry and a usable CLI.
• You want developers to self-serve tool discovery and invocation without writing bespoke wrappers per integration.
• You can pin to 0.14.x and absorb minor-version churn; the release cadence is fast and the API is pre-1.0.
• You are comfortable with symfony/dotenv as a dependency (now required, not optional).

Look elsewhere when:

• Your stack is Laravel-first. Despite the broad "Laravel/PHP" framing, this is a Symfony-ecosystem package (symfony/ai-mate); bundles, skills, and conventions assume Symfony. Treat this as a reason to validate fit before committing roadmap slots.
• You need a stable 1.0 contract with semver guarantees — 0.x minor releases can and do change behavior.
• You are not yet doing AI-agent or LLM tool integration; the package optimizes a workflow you do not have.
• You want a hosted or managed platform; this is a local developer CLI, not a service.
• Output format stability is a hard requirement — the pretty-rendering changes in this release are UX improvements, not a compatibility commitment.

How to Pitch It (Stakeholders)

To executives: This is a low-cost developer-experience layer that lets our PHP application expose its capabilities to AI tooling through a standard CLI instead of per-team custom scripts. The v0.14.0 release is incremental — no breaking changes, no deprecations — and is mostly about making the tooling easier to install, inspect, and debug. It also closes two config/credential bugs that would otherwise have surfaced as environment troubleshooting during a rollout. Recommendation: fund a scoped pilot, pin the version, and revisit at 1.0. One caveat worth stating plainly: this is a Symfony-ecosystem package, so fit for a Laravel-first codebase needs validation before we commit further.

To engineering: Safe minor upgrade. No API breaks. symfony/dotenv is now a required dependency so mate.env_file works without extra setup — expect a new entry in composer.lock. If you run into a failing tools:call, the error now points you at tools:inspect. MATE_DEBUG_LOG_FILE now resolves relative to the project root and accepts absolute paths, so existing relative-path configs should be re-verified once. Critically, has_api_key was returning true for unset env vars — any feature flagged on that check should be re-tested. Pretty output for tools:call no longer pads columns and falls back to JSON for large payloads; if you parse that output in CI, assert against JSON, not the aligned table.