Blog

ColdBox Free Tip 3: CommandBox ColdBox Commands

Victor Campos September 04, 2025

Spread the word

Victor Campos

September 04, 2025

Spread the word


Share your thoughts

102 ColdBox Tips and Ticks by Luis Majano

What is CommandBox and why is a key tool for ColdBox users?

CommandBox isn't just a powerful CLI for CFML—it’s also packed with tools to make ColdBox development faster and more efficient. In this tip, we’ll explore some of the most useful ColdBox-specific commands that can make your development life easier.

ColdBox CLI

All the CommandBox commands for ColdBox are encapsulated in the coldbox-cli package that comes pre-bundled with CommandBox. However, just to make sure let’s install it again to get the latest and greatest.


install coldbox-cli --force

CommandBox ColdBox Commands

CommandBox comes with a coldbox namespace loaded with commands to assist you throughout your ColdBox development journey. Whether you need to generate complete applications, monitor your code edits, or quickly reinit your framework, these commands have got you covered.

ColdBox Book

To see all available ColdBox commands, just run:

coldbox ?

You’ll get a list of namespaces and commands that make your workflow smoother. Let’s take a look at a few key commands:

Example
Example

Top-level ColdBox Commands:

  • reinit: Quickly reinitialize your running ColdBox application without restarting the server.

    coldbox reinit
    
  • watch-reinit: Set up an async watcher to monitor your file changes. If a file is modified, ColdBox will automatically reinit the app for you. This is super handy during development to keep things in sync without constant manual restarts.

    coldbox watch-reinit
    

Creation Commands:

CommandBox's coldbox create namespace allows you to generate various ColdBox elements easily:

  • coldbox create ?: Shows all the available commands under the create namespace.

    Use this to generate handlers, modules, interceptors, and much more, right from the CLI. It’s a huge time-saver, letting you scaffold your application with ease.

Try out these commands next time you’re building with ColdBox and let CommandBox do the heavy lifting for you! Keep an eye out for our next tip, and as always, happy coding!

Example
Example

Learn More ColdBox Tips and Tricks

Stay tuned for more ColdBox tips in our ongoing series. if you want to learn more than 10 free tips and tricks make sure to get your “ColdBox 102 tips and tricks book” We have a variety of formats you can choose from.

Getyour Copy

Join the Ortus Community

Be part of the movement shaping the future of web development. Stay connected and receive the latest updates on**, product launches, tool updates, promo services and much more.**

Subscribe to our newsletter for exclusive content.

Follow Us on Social media and don’t miss any news and updates:

Add Your Comment

Recent Entries

ColdBox 8.2.0: Middleware, Streaming, AI Gateways, and a Whole Lot More

ColdBox 8.2.0: Middleware, Streaming, AI Gateways, and a Whole Lot More

ColdBox 8.2.0 is the result of work we started in March. Several of its headline features, including route-scoped middleware and Server-Sent Events, were incubated for months before shipping. We held them back on purpose: we wanted the APIs settled, the edge cases covered, and the testing story complete before asking you to build on them. They're ready now.

Luis Majano
Luis Majano
September 23, 2026
Assert Like You Mean It, TestBox 7.1 Part 1: Set Expectations

Assert Like You Mean It, TestBox 7.1 Part 1: Set Expectations

If you have ever tested that two collections contain "the same stuff, order doesn't matter," you already know the workaround: sort both arrays, compare them element by element, and hope nobody adds a duplicate. It works, but it isn't what you meant to write. You meant "these are the same set."

Luis Majano
Luis Majano
September 23, 2026
Is Your QA Process Ready for Your Next ColdFusion or BoxLang Release?

Is Your QA Process Ready for Your Next ColdFusion or BoxLang Release?

As applications continue to evolve, QA can easily become reactive. Teams may test late in the development process, focus only on happy-path scenarios, repeat manual checks, or rely on AI-generated changes without fully validating the results. ​ These gaps can create risks that are not always visible until they affect users, disrupt operations, or require costly fixes in production.

Maria Jose Herrera
Maria Jose Herrera
September 21, 2026