# The lazy approach to building and modifying Monty configs

**URL:** <https://forum.thousandbrains.org/t/the-lazy-approach-to-building-and-modifying-monty-configs/1058>\
**Category:** Monty Code\
**Created:** [April 14, 2026, 5:27pm UTC](https://forum.thousandbrains.org/t/the-lazy-approach-to-building-and-modifying-monty-configs/1058 "2026-04-14T17:27:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmounir](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.thousandbrains.org/rmounir/32/268_2.png) [@rmounir](https://forum.thousandbrains.org/u/rmounir)\
**Post date:** [April 14, 2026, 5:27pm UTC](https://forum.thousandbrains.org/t/the-lazy-approach-to-building-and-modifying-monty-configs/1058/1 "2026-04-14T17:27:13Z")

</div>

During the London retreat, we worked on simplifying and improving the Monty configs, among other projects. Our configurations are now composable, rather than being overridden through inheritance. This is a big step toward making Monty easier to use and understand. If you’re interested in more details, check out @tslominski’s [post](https://forum.thousandbrains.org/t/we-changed-how-configurations-work-again/1040), or watch our [demo presentation](https://youtu.be/7bnPWJ-k3YE?si=L12UNtVR7uIVJK1r&t=714).

We also built a Terminal User Interface (TUI) called `lazyconfigs` to make it easier for us and the community to quickly put together new experiment config files or modify existing ones. I walk through a [demo](https://youtu.be/7bnPWJ-k3YE?si=-kiV5injf9E8ZCPI&t=1513) of this in the presentation.

 ![lazyconfigs](https://canada1.discourse-cdn.com/flex034/uploads/thousandbrains/original/2X/8/8c9a932083cf948e17b9dc52611aa95ff88a868c.png)

`lazyconfigs` is now available in [this repository](https://github.com/thousandbrainsproject/lazyconfigs) and can be installed with:

```zsh
brew tap thousandbrainsproject/tap
brew install --cask lazyconfigs

```

Alternatively, you can build from source. The tool is relatively straightforward to use and supports customizable themes and keybindings. Let us know if you run into any issues or have feedback.

---

<div class="post-metadata">

**Author:** ![Rich\_Morin](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.thousandbrains.org/rich_morin/32/89_2.png) [@Rich\_Morin](https://forum.thousandbrains.org/u/Rich_Morin)\
**Post date:** [April 14, 2026, 7:54pm UTC](https://forum.thousandbrains.org/t/the-lazy-approach-to-building-and-modifying-monty-configs/1058/2 "2026-04-14T19:54:22Z")

</div>

Thanks, all, for helping make Monty development more approachable. As it gets closer and closer to the point of being painless, more folks may decide to jump in. Specifically, I’ve noted:

- the team’s work on composability and framework independence
- lazyconfigs and other promising work (e.g., [Pythonx](https://hexdocs.pm/pythonx/Pythonx.html) integration)

To that point, I’d like to suggest a complementary approach. Basically, it would use [skills](https://agentskills.io/home) and [setup prompts](https://share.google/aimode/CpdwV6TvC8LmzIFeZ) to assist agentic AI tools (e.g., Codex CLI) with setting up and interacting with Monty.

FWIW, I’m not totally clear on what would need to be in these, but:

- setup prompts would include background information, links, etc.
- skills would handle typical interaction scenarios

If anyone is using this sort of approach, I’d love to hear about it.

-r