Chestnut, explained

More computing. Outside the device.

Chestnut connects an external graphics processor to comma four so openpilot can run a larger driving model.

Chestnut external graphics hardware connected to a comma four
Photo: comma.ai

The plain-language version

An optional helper for comma four.

A driving model helps software interpret the road and plan driving actions. A larger model needs more computing capacity.

The device stays.

comma four remains part of the setup. Chestnut does not replace it.

Extra hardware joins it.

Chestnut connects a separate graphics processor, often called a GPU, to the device.

The software must match.

Use the documented Chestnut software path. A standard installer is not a substitute for the Chestnut setup instructions.

Chestnut graphics hardware mounted in a passenger footwell
Photo: comma.ai

What changes in your car

Plan for the extra hardware.

The assembled hardware needs secure mounting, power, a connection to comma four, and room for airflow.

The ready-to-drive kit and dock-only option are different products. Check the current contents before ordering.

See the installation guide

More computing does not remove driving limits.

Chestnut does not make the car self-driving. You still need a supported car, matching software, and an attentive driver.

A larger model is not a promise of better behavior on every road. Keep the same readiness to steer and brake.

Good questions. Clear answers.

Do I need Chestnut to use comma four?

No. Standard openpilot runs on comma four without Chestnut. Choose Chestnut only if you want its larger-model setup and extra hardware.

Is Chestnut just another name for comma four?

No. comma four is the device. Chestnut is separate hardware that connects an external graphics processor to it.

Will it make my unlisted car compatible?

Do not assume that. Car compatibility still needs a separate exact-model, year, and equipment check.

Was this guide helpful?