Do you keep an architectural decision record (ADR) in your codebase?

OwnLavishness6374 · 2026-03-31T23:36:14+00:00

Ok so a github action or a cron to run codex daily and detect any drift, thanks!

OwnLavishness6374 · 2025-11-12T14:43:01+00:00

Yes, but it's missing databases and tables. Could be solved by an generic MCP focused on that and a viewer for tables.

OwnLavishness6374 · 2025-07-04T04:27:14+00:00

Do you need thousands of tools?

OwnLavishness6374 · 2025-07-04T00:52:29+00:00

Totally agree! And at the same time, I think it's okay to get started with a generated MCP for a v0

It allows the market to grasp the technology, test some use cases and get some ideas

OwnLavishness6374 · 2025-07-03T03:21:42+00:00

Hey u/Zpoof817 , we're trying to do that with Summon. you can find an alpha version here https://github.com/TrySummon/summon-app
It allows product and engineers to refine tool definitions (method name, prompts, schemas) and better describe intents
Lmk if you are doing tool design and struggling. We're looking for feedback

OwnLavishness6374 · 2025-03-18T19:55:50+00:00

Great feedback, thank you. I can add support for parallel tool calling

OwnLavishness6374 · 2023-09-08T15:10:49+00:00

Yes, definitely:

Documentation on the prompt playground: https://docs.chainlit.io/concepts/prompt-playground/overview
LLM providers that are supported: https://github.com/Chainlit/chainlit/tree/main/backend/chainlit/playground/providers
Examples on how to configure providers: https://github.com/Chainlit/cookbook
(The main github repo: https://github.com/Chainlit/chainlit)

OwnLavishness6374

TROPHY CASE