Kin Browser for teams (1.0)
How a team shares one Kin Browser — on a desktop or a cloud machine — with people signed in, sign-ins agents use without seeing, the team's rules on what is kept, approvals from chat and phones, and many machines working together.
People, roles and single sign-on
Until the first person is added, the console lets in whoever passes its front door (the console key and the proxy's sign-in). Add people and everyone signs in:
kin-browser people add [email protected] --role admin --password # asks for a password (10+ characters)
kin-browser people add [email protected] --role approver # signs in with SSO only
kin-browser people list · people role <email> viewer · people remove <email>| Role | May |
|---|---|
| viewer | watch the Grid, recordings, schedules, workflows and usage |
| approver | also decide: allow sites and risky actions, answer agents, approve drafts, take control, replay recordings, read the audit log, the vault list and connections |
| admin | everything: settings, compliance, the vault, people, automations |
Sign in with Google or Microsoft (OpenID Connect, PKCE, tokens checked against the provider's keys):
kin-browser sso google --clientId … --url https://agent.example.com --domains example.com --role viewer
kin-browser sso microsoft --tenant <tenant id> --clientId … --url https://agent.example.com
kin-browser sso # what is set · kin-browser sso offRegister <url>/auth/callback as the redirect address. People from
--domains get an account with --role the first time they sign in; anyone
else must be added first. Every decision a person makes is in the audit log
with their name.
The credential vault
Sign-ins agents may use without ever seeing them:
kin-browser vault add billing.example.com --username [email protected] # the password is asked for, hidden
kin-browser vault add portal.example.gov.my --username ops --totp # and the authenticator secret
kin-browser vault list · vault policy <id> allow · vault remove <id>Or in the Grid → Vault. An agent on the login page says signIn; Kin
Browser fills the username and password, submits, fills the six-digit code
when the entry has an authenticator secret, and tells the agent "signed in" —
never the username, password or code, which are also masked in every snapshot
after. An entry is ask by default (a person says Allow each time, in the
Grid, the console, Slack, Teams or a phone) or allow (agents may use it on
its own site). Every use is counted and in the audit log.
Encryption at rest and retention
The vault, connected systems' keys, saved sign-ins (saveState), people, SSO,
chat and fleet settings are encrypted on disk (AES-256-GCM) with a key of the
machine's own, machine.key, readable by its user only — a copied data folder
or a backup does not carry them in the clear. Files from before 1.0 are read
as they are and encrypted the next time they are saved.
What is kept, and for how long (days; 0 keeps for ever):
kin-browser retention # recordings 90, reports 60, artifacts 30, audit 365, runs 90
kin-browser retention --recordings 30 --audit 730 # change
kin-browser retention apply # sweep nowstart and serve sweep when they start and daily. An API client's own
folders are swept inside, never removed whole.
Approving from Slack, Teams and a phone
Slack. Make a Slack app with a slash command /kin pointed at
<api address>/api/v1/slack/command and interactivity at
<api address>/api/v1/slack/actions, then:
kin-browser chat slack --approvers U0123ABCD,U0456EFGH # asks for the app's signing secret/kin lists what is waiting with Allow / Deny buttons; /kin approve <id>
and /kin reject <id> why work too. With the notify webhook set to the app's
incoming webhook, new-site and risky-action notices arrive with buttons. Every
request is checked against the signing secret (and refused after five
minutes); only the listed member ids may decide.
Teams. An outgoing webhook pointed at <api address>/api/v1/teams:
kin-browser chat teams --approvers "Aisyah Rahman,Wei Ming" # asks for its security tokenThen @Kin pending, @Kin approve <id>, @Kin reject <id> why in the channel.
A phone. Open the console's Approve page (/pages/approve.html) on a
phone, add it to the home screen, and tap Notify this phone: agents
asking for help, new sites and risky actions arrive as notifications (Web
Push, encrypted for that phone), with Allow and Deny a tap away. Typed answers
(a code, a password) are never asked for through chat or push.
Usage
The Grid → Usage (and usage for agents, /v1/view/usage): steps,
pages, rows collected, decisions, failures and a rough person-hours-saved, by
day, by action and by agent, over 7–365 days. Counts only: nothing about what
the pages said.
A fleet, in several regions
More machines for big batches, and machines where your customers are:
# On the new machine: kin-browser clients add --name home-fleet --per-day 5000
kin-browser fleet add sg-1 --url https://sg.agent.example.com --region SG --key kbc_…
kin-browser fleet list # each member's health and versionbatch with fleet: true spreads the rows over this machine and every
member, each taking the next row when free; results say which machine did
each row. API clients can have a daily quota (clients add --per-day N).
A new regional machine, on AWS, with nothing open to the internet:
packaging/cloud/provision.sh plan --region ap-southeast-1 --name sg-1 # changes nothing
packaging/cloud/provision.sh apply --region ap-southeast-1 --name sg-1 # makes it (costs money while it runs)
packaging/cloud/provision.sh destroy --region ap-southeast-1 --name sg-1Updates and crash reports
When a new Kin Browser is out, the Grid says so with Update now: it
downloads the installer, checks its SHA-256 against the release, and installs
it — macOS shows its own administrator prompt, Linux pkexec, Windows
installs for the user. kin-browser update does the same from a terminal.
Crash reports are off unless a person turns them on (the first-run tour,
or kin-browser crash-reports on). A crash is always written to
crashes.local.jsonl; when on, the error, its stack with the home folder,
addresses and emails taken out, and the versions are sent to the Kin Browser
team. Never a page or anything typed.
Languages
Kin Browser's own pages are in English, Bahasa Melayu and 中文: the menu in each page's bar, remembered for the machine.