CLI 0.4.1: custom_grain --account resolves toolkit as custom; inconsistent discovery and approval settings UX

Environment

• Composio CLI 0.4.1 on macOS, used from Codex
• composio upgrade reports this is the latest version (September 15, 2026)
• An existing connected custom Grain toolkit: custom_grain

Account selection bug

composio search 'Grain meeting transcripts' correctly discovers CUSTOM_GRAIN_* tools and reports custom_grain connected. Executing those tools without --account succeeds.

However, selecting the existing connected account explicitly fails:

composio execute CUSTOM_GRAIN_SEARCH_PERSONS --account <existing-grain-account-id> -d '{"search_string":"example"}'

Observed error (account ID redacted):

services/ConnectedAccountResolutionError
No connected account matched "<existing-grain-account-id>" for toolkit "custom".
No active connected accounts were found for that toolkit.

composio link custom_grain confirms the account already exists. The error suggests toolkit resolution treats CUSTOM as the toolkit instead of custom_grain; this is an inference from the error, not a source-confirmed diagnosis.

Discovery inconsistency

composio tools list custom_grain reports no tools found, while search discovers tools and execute successfully runs them. A cached CUSTOM_GRAIN_LIST_MEETINGS schema also proved usable despite not appearing in the initial semantic search results.

Persistent approval UX request

Grain reads repeatedly required interactive approval. Session approvals work, but no documented persistent per-toolkit "always allow" setting could be found in composio --help full or composio config --help. Please expose/document a supported way to inspect and set persistent permissions for one custom toolkit, without changing global defaults or editing local caches.

Expected: resolve custom toolkit account selectors correctly, make discovery consistent, and provide a clear supported path for persistent user-authorized per-toolkit approval settings.