Connect your tools

Choose a coding assistant

A coding provider helps turn your description into changes. Use the provider setup and diagnostics in your build, then follow that provider’s own installation and sign-in steps. You can also edit files directly.

Lyre account sign-in is separate from a provider login. Early access does not require a Lyre account, but your chosen provider may require an account, subscription or API key. Provider availability varies by build.

Put credentials with the service that uses them

An API key is a credential that lets software use a service. Keep personal credentials on the trusted host or backend that needs them. Do not put them in browser code, shared plugin settings, screenshots, marketplace listings or a public repository.

A public Supabase publishable key can be included in a client; a Supabase secret or management token cannot. Public keys still rely on database access rules.

Speech-to-text with Groq

On compatible foundation hosts, Groq uses the OpenAI-compatible speech endpoint. Configure the host’s providers.openai.stt with your personal key and base URL https://api.groq.com/openai/v1. Select openai as the dictation STT provider and a Groq-supported transcription model in that feature’s settings.

This configures transcription, not text-to-speech or your coding assistant. Review where recordings go before using dictation. Keep credentials out of projects and restart the host normally when configuration requires it.

Need a service Lyre does not expose?

You can connect a service in your own app, or build a trusted host plugin when the connection belongs in Lyre. Choose the right integration boundary before adding code.