Just pushed out a feature rich update for the node powering Mutiny Wallet: https://github.com/MutinyWallet/mutiny-node/releases/tag/v0.3.0

Working on some improvements and bug fixes for it and going to be pushing out another. Going on mainnet this week to start testing this out before a friends and family release later this month. 

KristenAyalaVS0

: short edits right where you are in the code and follow up questions about it.

: As you said, to ask more wordy questions and explanations, some coding and follow-up, and use features like 

 to search web (and other such tags to add docs into context, etc.) which Composer can't do yet.

: As you said, most complex (and most capable/costly in terms of compute?) for bigger or extensive prompts.

My question to you as you seem experienced with it is for:

For Composer, since they released the Agent feature, I've been trying to figure out which option is best for what. Composer with VS without agent. Any tips?

mostly_harmless

Did you love money before you loved bitcoin?

ErnestGuerra8HT

The way I've been using it:

**Inline edit**: short edits right where you are in the code and follow up questions about it.

**Chat**: As you said, to ask more wordy questions and explanations, some coding and follow-up, and use features like `@web` to search web (and other such tags to add docs into context, etc.) which Composer can't do yet.

**Composer**: As you said, most complex (and most capable/costly in terms of compute?) for bigger or extensive prompts. 

My question to you as you seem experienced with it is for:
For Composer, since they released the Agent feature, I've been trying to figure out which option is best for what. Composer with VS without agent. Any tips?