Download the PHP package jordandalton/tackle-grokbot without Composer

On this page you can find all versions of the php package jordandalton/tackle-grokbot. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package tackle-grokbot

Tackle Grokbot

jordandalton/tackle-grokbot adds named Cursor automation webhooks to Laravel Tackle. Register any number of bots with instructions, let the agent discover and invoke them, and inspect delivery history.

Requires PHP 8.3+, Laravel 12/13, and Laravel Tackle ^1.56.8. Tackle 1.56.8 adds automatic discovery of package tools through the tackle.tools container tag.

Installation

With Tackle 1.56.9 or later, install and set up Grokbot in one command:

This installs jordandalton/tackle-grokbot:^0.1.1 as a development dependency, then starts grokbot:install in a fresh Artisan process. Use --no-dev to install it as a production dependency. If the package is already installed with its setup command, Composer is skipped and setup runs again.

For unattended production setup:

Registration is offered only in an interactive terminal. Without a TTY, setup runs non-interactively; register credentials afterward from a terminal.

Alternatively, install the package directly (also supported with Tackle 1.56.8):

Laravel discovers the service provider automatically. Migrations are loaded by the package. The application must have an APP_KEY for encrypted credentials.

The installer runs only this package’s migrations, then offers to register the first bot. It is safe to rerun: existing migrations and bots are preserved. Decline registration to configure bots later. For unattended deployment, use php artisan grokbot:install --no-interaction; production also requires --force. Registration prompts are skipped in unattended mode.

Manage bots

Credentials have no CLI argument or option: enter them directly into the hidden terminal prompt. No supplied credentials or endpoints are seeded by the package.

Instructions should explain when to use the bot and what JSON fields it expects. For example: “Reviews pull requests. Send repository_url, pr_number, and optional review_concerns.” Instructions are agent-facing metadata, not automatically added to the outbound payload.

Agent tools

The default Tackle agent receives three tools through the tackle.tools container tag. They retain Tackle's allowlist, hooks, and tool event handling:

If tackle.tools is configured as an allowlist, include the tool class names above. Custom agents that override tools() must include these classes themselves; read-only and lean agents do not gain sending access automatically. MCP tools are separately configured in tackle.mcp.tools.

Delivery behavior

Requests use POST, JSON, and bearer authentication. Destinations are restricted to HTTPS Cursor automation URLs on api2.cursor.sh. Redirects are not followed. Connect timeout is 10 seconds and overall timeout is 30 seconds. Requests are synchronous and are never automatically retried.

Every attempt is persisted before HTTP:

Logs retain the bot ID, sanitized payload, status, HTTP status, duration, timestamps, and a generic error. Response bodies, headers, and exception messages are deliberately not persisted. Payload fields named like credentials and occurrences of the destination's bearer token are redacted. Other task content is retained; do not include unnecessary secrets in payloads. History is retained indefinitely unless the host application removes it.

Tokens are encrypted at rest and both tokens and URLs are hidden from model serialization and discovery tools. These boundaries do not stop an agent with arbitrary application PHP/shell/database access from decrypting credentials. Configure host permissions accordingly. Host HTTP instrumentation such as Telescope must separately redact Authorization headers.

Development

From this package directory, using the sibling Tackle checkout’s installed dependencies:

With this package’s own Composer dependencies installed, run composer test. Tests fake HTTP; no live automation is triggered.


All versions of tackle-grokbot with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
jordandalton/laravel-tackle Version ^1.56.8
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package jordandalton/tackle-grokbot contains the following files

Loading the files please wait ...