Use case / sign in and configure
Let your coding agent sign in and finish setup
Use a browser session you choose, then let Trusty Squire handle the settings, console, and integration work that lives behind the login.
Ask for the outcome
“Add Google OAuth in one prompt.”
“Go live: deploy, custom domain, and SSL.”
“Send gifts privately (Hermes).”
How it works
- 01
You choose the signed-in session
Connect Google or GitHub in the Trusty Squire browser, or work with the provider session already present in that browser profile.
- 02
Your agent reads the current page
It sees the available controls and page state, then asks Trusty Squire to take one scoped action at a time.
- 03
The browser completes the setup
Trusty Squire clicks, types, and navigates through project settings while your coding agent keeps the requested outcome in view.
- 04
Human decisions stay human
If the site asks for consent, a risky choice, or a gate that should not be guessed, the run stops and tells you what is needed. Every charge requires exactly one human approval before payment, then the run can continue.
What to know
Work behind auth is the point
General browser automation is easy to demo on a public page. Developer setup usually starts after a login: create a project, open a settings panel, register a callback URL, generate a key, or paste one value into a second console. Trusty Squire is built for that authenticated part of the job.
Cross-console secrets can stay sealed
Some integrations create a secret in one console and require it in another. Trusty Squire can capture that value into a sealed in-session slot and type it at the destination without placing the plaintext in the agent conversation. Read more about the credential boundary in the API key guide.
A real browser, not your password in a prompt
You perform the identity connection in a browser. The agent drives the resulting website session, but it does not need your Google or GitHub password to do so. Reauthentication and account switching remain explicit user actions.