Laravel workflow glossary

This glossary keeps the LaraBench docs consistent. Start here if a page, filter, or screen uses a Laravel workflow term you want defined quickly.

Core workflow terms

• Connection: A saved target LaraBench can run against, such as a local Laravel project, a Docker container, or an SSH server.
• Run Code: The main runner where you execute Tinker snippets or Artisan commands against the selected connection.
• Saved snippet: Reusable code stored locally so you can rerun a query, check, or command later.
• History: The local record of past runs, including output, timing, and the connection used.

Safety and execution

• Dry run: A connection or run mode intended for safe inspection, where LaraBench suppresses writes where it can.
• Write detection: LaraBench's warning system for snippets or commands that look like they may modify data.
• Production confirmation: The extra confirmation step before a run executes against a production-labelled connection.
• Benchmark mode: A repeat-run workflow for comparing two snippets or measuring one snippet over many runs.

Jobs and sharing

• Laravel Jobs: The public LaraBench jobs feed, searchable by stack, source, seniority, arrangement, and country.
• Cloud sync: The Premium feature that syncs supported saved items and history between signed-in devices.
• Share link: A Premium link that exposes a saved item or run on the web without exposing the whole account.
• MCP server: LaraBench's local server for coding assistants, with read access and guarded run access based on your connection settings.