kortix-chrome
Drive the USER'S OWN Chrome (their real logged-in session) from a Kortix session, over CDP, through the Kortix Chrome extension. Load this when the task needs the user's logins or real browser state (
SKILL.mdpackages/starter/templates/managed/skills/kortix-chrome/SKILL.md
GitHub<skill name="kortix-chrome">
<overview>
The user installs the Kortix extension in Chrome once. `kortix chrome use`
then attaches that Chrome to this session, and `agent-browser` drives it
through a CDP endpoint on `127.0.0.1:9333`. It is the user's real chrome:
their cookies, logins and extensions.
Use the sandbox browser (agent-browser with no --cdp) when no login is
needed. Use the user's browser when the user says "my browser" or "my Chrome",
or the task needs their logged-in state.
</overview>
kortix chrome status shows whether a browser is attached. kortix chrome ls
lists the user's browsers.
</flow>
The user picks the access mode in the extension or in Kortix settings: without
asking, ask first (your first use shows a prompt in Chrome and waits up to
90 seconds), or off.
</what_the_user_sees>
- All tabs (the default):
agent-browser --cdp 9333 tab listlists every tab in every window. Answer questions about what the user has open from that list. You start in a tab of your own; work there withopenandtab new. Switch to one of the user's tabs (tab <id>) only to read it or when the user asks you to act in it, and never navigate a tab of theirs away from its page. - Only tabs it opens: you see your own tabs and nothing else. If the user
asks about their other tabs, say so in one line and tell them where to change
it: the Kortix extension's options → Tabs → All tabs, or Kortix Settings →
Kortix in Chrome. Then run
kortix chrome useagain.</tabs>