- How do I install tigusigalpa/manus-ai-php in a Laravel application?
- Install it with Composer using composer require tigusigalpa/manus-ai-php. Laravel package auto-discovery registers the service provider and facade, so no manual wiring is usually required. After installing, publish the configuration file with php artisan vendor:publish and set your Manus API key in your .env file.
- Which Laravel and PHP versions does this Manus AI SDK support?
- The package claims support for Laravel 8 through 12 and PHP 8.2 through 8.4. Before rolling out, confirm that your exact Laravel and PHP combination is covered by the package's CI matrix, since compatibility is often validated per PHP version rather than per Laravel version. Older Laravel 8 applications deserve extra attention, especially if other dependencies constrain your PHP version.
- How do I configure the Manus AI API key in this package?
- Configuration is handled through the publishable config file and environment variables, following standard Laravel package conventions. Publish the config, add your Manus API key to .env, and clear your config cache after changes. Keep credentials out of version control and use per-environment keys for staging and production.
- Does the package support OAuth Bearer tokens as well as API keys?
- Yes. Version 2.1.0 adds OAuth Bearer token support alongside API key authentication, which helps in multi-tenant or delegated-authorization scenarios. Token refresh, storage, and rotation ownership are not clearly defined in the release notes, so plan for your application to manage the token lifecycle unless you confirm otherwise. Test OAuth flows in staging before relying on them in production.
- How do I create and manage Manus AI tasks with this SDK?
- You create, update, and retrieve tasks through the facade or the underlying client using type-safe interfaces. In v2.1.0, task payload fields changed, so replace deprecated options with interactive_mode, enable_visible_in_task_list, and the standard, lite, or max agent profiles. Validate your task create and update payloads against the normalized response envelopes before deploying.
- Does the package handle Manus webhooks and signature verification?
- The SDK supports webhook integration with real-time notifications for events delivered by the Manus API. Signature verification, replay protection, and retry semantics are security concerns you should confirm in the source or docs, and add at the application level if they are not provided. Expose your webhook endpoint as a stateless route, return fast responses, and queue heavy processing so retries do not cause duplicate work.
- What happened to listFiles() in version 2.1.0?
- listFiles() was removed in v2.1.0, which is a hard breaking change for any code that relies on file listing or file inventory workflows. Review the release migration guidance for the supported replacement approach and inventory every call site before upgrading. Workflows that need file discovery should be validated against the Manus API v2 file endpoints in staging.
- Are legacy aliases like manus-1.6, enable_ask_user, and hide_in_task_list still supported?
- Backwards-compatible aliases are still present in v2.1.0, including legacy manus-1.6 style identifiers and the older option names. They reduce short-term upgrade risk but create migration debt, and no removal timeline has been published. Migrate to interactive_mode, enable_visible_in_task_list, and the standard, lite, or max profiles now so a future release does not break you.
- Can I use this Manus AI PHP SDK outside of Laravel?
- Yes. It is a standalone PHP client for the Manus AI API and requires PHP 8.2 or newer, so it can be used in any Composer-based PHP application. Laravel-specific features such as the facade, service provider, config publishing, and Artisan commands are simply conveniences layered on top. Outside Laravel, instantiate the client directly and pass your API key or OAuth token.
- How should I test and roll out this package safely in production?
- Pin v2.1.0 on a non-production branch, publish and diff the config, then run your full test suite with extra coverage for task create and update, file upload, webhook handling, and error paths. Smoke-test each Manus API v2 resource in staging, including discovery, usage, website, project, agent, webhook, task, and file upload. Deploy gradually and monitor for API errors, timeouts, oversized responses, auth failures, and rate-limit or retry-after behavior.