Weave Code
Tinker Laravel Package
botman/tinker
botman/tinker brings Laravel Tinker support to BotMan, letting you chat with your bot from the console to test replies and debug conversations quickly without connecting a real messaging channel.
Gives your Laravel chatbot the ability to try your chatbot in your local terminal.
Frequently asked questions about Tinker
- How do I install botman/tinker in a Laravel application?
- Install it with Composer alongside the core BotMan package, then confirm the package's service provider is registered (or auto-discovered) for your Laravel version. Because the package's supported framework range is narrow, run the install in a throwaway branch first and check the resolved lockfile delta. If Composer refuses the install, that is a platform constraint problem, not a configuration mistake.
- Which Laravel versions does botman/tinker support?
- The 1.2.0 release changed only the composer.json platform constraint to admit Laravel 7.x; no runtime code was modified. That means Laravel 7 is the newest framework version the package has declared, and Laravel 7 reached end of life in March 2021. Check whether the constraint is a range such as ^6.0|^7.0 or a replacement such as ^7.0, since a replacement would silently drop Laravel 6 support. Nothing in the release indicates support for Laravel 8 or later.
- How do I chat with my BotMan bot from the terminal?
- Once installed, the package exposes an Artisan command that opens an interactive console session where you type a message and your bot replies using the listeners already registered in your application. That means no webhook, tunnel, or messaging driver is needed to exercise your conversation logic. It is intended for local development and debugging, not for handling real users.
- Can I test my BotMan bot without connecting Telegram, Slack, or another channel?
- Yes. That is exactly the purpose of botman/tinker: it lets you exercise your bot's replies directly in the terminal, bypassing real messaging channels entirely. You can iterate on conversation flows, intent matching, and reply formatting locally before wiring up a production driver. This shortens the feedback loop considerably compared with deploying to a test channel for every change.
- Does botman/tinker support Laravel 8, 9, 10, 11, or 12?
- There is no evidence of it. The only change in 1.2.0 was widening the platform constraint to admit Laravel 7.x, which suggests the package is roughly five major framework versions behind current Laravel releases. Do not assume that a permissive constraint equals tested compatibility; the question of whether the code was actually exercised against Laravel 7 is unresolved. Verify against your pinned framework version in an isolated branch before planning adoption.
- Is botman/tinker safe to install in a production Laravel application?
- It is a development aid, so the sensible pattern is to require it as a dev dependency and keep the console chat command out of production environments. The package itself carries low direct risk because the 1.2.0 change is a non-breaking constraint widening with nothing removed. The larger concern is indirect: a widened platform constraint can pull previously blocked transitive dependencies into your lockfile. Capture and review the lockfile delta before merging.
- Why does Composer refuse to install botman/tinker on my Laravel version?
- The package declares a narrow platform constraint that tops out at Laravel 7.x, so Composer will block installation on Laravel 8 and above. Do not hand-edit the constraint in your own composer.json to force it through, because that produces an install that was never tested by the maintainers and can fail at runtime rather than at install time. The correct next step is to raise the constraint with the maintainer or evaluate an alternative.
- How is botman/tinker different from BotMan Studio?
- BotMan Studio is a full Laravel starter project for building bots, bundling the framework, configuration, and channel scaffolding. botman/tinker is a small add-on whose only job is to give you a console REPL for talking to an existing bot. Use tinker when you already have a BotMan setup and want a fast way to test replies without touching a real channel.
- Is botman/tinker still actively maintained?
- The signals are mixed. The Laravel 7 constraint update arrived as a community pull request, which shows some responsiveness, but it landed long after Laravel 7 was already end of life, which points to maintenance lag and thin maintainer bandwidth. The bus factor is likely one or two people. Before adopting, check release cadence and issue-triage latency over the last twelve months and ask whether a support policy exists.
- How do I debug conversation flows and see what my bot replies?
- Use the package's terminal command to send messages and read the bot's responses directly, which makes reply formatting and listener matching issues visible immediately. Combine that with application logging so you can see which listener was matched and why. Exercise the same flows in a sandbox branch at your actual Laravel and PHP versions, since console behaviour can differ from webhook-driven behaviour.
Weaver
How can I help you explore Laravel packages today?