Manus Ai Php Laravel Package

Product Decisions This Supports

• Build vs. buy for Manus integration: If your product depends on Manus (agents, tasks, webhooks, projects, websites, usage/discovery), adopting this SDK replaces a bespoke integration layer with a maintained one — freeing engineering to work on differentiated features instead of API plumbing and auth.
• Roadmap timing for AI/agent-powered features: With support for Manus API v2 resources (agents, projects, webhooks, discovery, usage, website), a PM can confidently scope features like in-product agent orchestration, usage-based dashboards, or webhook-driven automation without waiting on a custom connector.
• Auth strategy decision: OAuth Bearer tokens plus API key auth means you can support both multi-tenant user-consented flows (OAuth) and server-to-server/back-office flows (API keys) — a decision that affects onboarding, permissions, and enterprise sales conversations.
• Framework compatibility scope: Laravel 8–12 support lets you ship to existing customers across upgrade cycles; useful when deciding whether to gate features on a Laravel upgrade or support the broader install base.
• Compliance and security sign-off: CI (PHP 8.2–8.4), CodeQL, Dependency Review, and Dependabot give security reviewers concrete evidence to approve the dependency — reducing procurement/security-review friction.
• Migration planning: Backwards-compatible aliases for legacy camelCase options and agent-profile names, plus documented migration guidance (EN/RU), lower the switching cost and let you phase out deprecated field names on your own timeline rather than a forced cutover.
• Risk/roadmap flag: listFiles() removal is an intentional capability gap tied to Manus API v2 — any roadmap item depending on listing files needs a workaround or a request upstream.

When to Consider This Package

Adopt when:

• You are building on Manus and want first-class Laravel integration (service provider bindings, facade, Artisan commands, published config).
• You need both OAuth and API key auth paths in the same product.
• You rely on v2 resources: discovery, usage, website, project, agent, and webhook endpoints.
• Your install base spans Laravel 8–12 and you want one supported dependency.
• Security/compliance review is a gate and you need an auditable CI and scanning baseline.

Look elsewhere or proceed cautiously when:

• You depend on listing files — that capability is no longer supported (listFiles() removed; API v2 has no file-list endpoint). Confirm alternatives before committing.
• You need long-term stability guarantees; the v2 field-name migration (interactive_mode, enable_visible_in_task_list, new agent_profile values) shows the API is still normalizing, and further renames are plausible.
• You are not on Laravel, or are pinned to a version outside 8–12.
• Your workloads need capabilities Manus v2 does not expose (file enumeration, and any endpoints not listed) — a thin custom client won't fix a missing API surface.
• You require strict semantic versioning discipline; this release mixes additive features, behavioral fixes, and removals in a minor bump.

How to Pitch It (Stakeholders)

For executives: This is a maintained Laravel SDK that connects our product to Manus's current API. It converts integration work we would otherwise build and maintain in-house into a dependency we can adopt quickly. It ships with a real security and CI baseline, supports the Laravel versions our customers run, and includes migration guidance — so we can move faster on agent-powered features while lowering maintenance and compliance risk.

For engineering: v2.1.0 aligns the SDK with Manus API v2, adds OAuth Bearer auth alongside API keys, and expands resource coverage (discovery, usage, website, project, agent, webhook). Laravel integration is fleshed out — config, service provider bindings, facade, Artisan commands — with Laravel 8–12 support. Quality posture is credible: 40 tests / 86 assertions, PHP 8.2–8.4 CI, Codecov, CodeQL, Dependency Review, and weekly Dependabot.

What to plan for:

• Adopt the new field names now (interactive_mode over enable_ask_user; enable_visible_in_task_list over hide_in_task_list; agent_profile values standard/lite/max). Legacy aliases exist, but treat them as transitional.
• Audit for listFiles() usage — it is gone with no v2 equivalent. Identify affected roadmap items and either re-scope or raise upstream.
• Keep an eye on error handling, timeouts, JSON parsing safeguards, and response-size limits — these are improvements, but they change behavior at the edges, so re-run integration tests against real responses.
• Add CODECOV_TOKEN to repository secrets if we want coverage uploads.

Bottom line: A net-positive release with meaningful capability and governance gains. The only blocker-class item is the listFiles() removal — resolve that dependency question before committing it to the roadmap.