Dictate in any app · Cloud

Voice typing in Google Cloud Console

GCP projects sprawl, and the description fields that would explain them stay empty. Typally puts your words into Google Cloud Console the moment you release the key, in whichever field you left the cursor.

From the people who build Typally. If Google Cloud Console's own option covers your use, use it — this page will tell you when it does.
Dictate into Google Cloud Console 100 free minutes every month. No card, and nothing to cancel if you stop.
Try Typally free

In short

  • Google Cloud Console's own dictation: None. Console text fields are typed.
  • What Typally does instead: types into the focused window, so it works in Google Cloud Console and everywhere else you write.
  • Best used for: resource descriptions

Does Google Cloud Console have built-in dictation?

None. Console text fields are typed.

Why dictate in Google Cloud Console at all?

Service accounts, firewall rules and buckets accumulate across a project's life. Each has a description field. An undocumented service account with broad permissions is the thing security reviews find and nobody can explain.

In practice people use it for: Resource descriptions, service account purposes, firewall rule notes, IAM justifications, and support cases.

How to dictate in Google Cloud Console

Setup happens once, outside Google Cloud Console, and then applies to every program on the machine:

1

Get Typally running

Install, sign in, and it waits in the tray.

2

In Google Cloud Console, click the field before you speak

Whatever has the cursor receives the text, so click the right place in Google Cloud Console before starting.

3

Speak with the key held down

Push to talk, say your piece, release to transcribe.

4

Read it before you move on

The console's forms vary between services and some fields have tight length limits. Check the text fits before moving on.

What Typally adds in Google Cloud Console

Typally types into the console's fields directly, so describing a resource happens when you create it rather than during an audit six months later. Because it needs no browser extension or permission grant, it introduces nothing for a cloud security team to assess.

What this looks like in practice

Before a security review, a team spends an hour speaking descriptions onto every service account. Three turn out to have no owner at all and are disabled without incident.

One habit that makes it work better

Describe every service account with what it is for and which system uses it. That is the single most useful piece of documentation in a cloud project.

What to watch out for in Google Cloud Console

The console's forms vary between services and some fields have tight length limits. Check the text fits before moving on.

Frequently asked questions

Does the GCP console have voice input?

No. All text entry is typed.

What should a service account description say?

What uses it and why it needs the permissions it has.

Can I dictate IAM condition expressions?

Those are structured syntax — type them, and dictate the description beside them.

Try it in Google Cloud Console

The free plan gives you 100 minutes a month without a card — enough to find out whether talking beats typing for you.

Try Typally free

Also dictate in: AWS Console · Azure Portal · Firebase · see all apps