Commit Graph
6 Commits
Author SHA1 Message Date
yilsemandClaude Opus 5.5 86a6621936 feat(chrome): let the IDE agent use the user's Chrome and beta.42
Server CI and Windows package / verify (push) Successful in 3m33s
Server CI and Windows package / windows-package (push) Successful in 7m36s
The AITURK Chrome extension now registers the user's Chrome as the desktop
backend's browser controller, the way the ChatGPT extension lets its agent
work in the user's browser. The agent's existing browser tools (navigate,
snapshot, click, type, scroll, back, press, get_images, vision) run in its
own background tabs grouped as "AITURK", or a tab the user hands over.

Backend: a local desktop lane in the browser-control broker. One controller
registered from the loopback desktop transport is offered to every desktop
session as a lane template; each session still gets its own exact scope on
first use. The lane has its own switch (browser.extension_control.local_desktop,
on by default); with no extension registered, or after it disconnects, the
normal browser backend runs unchanged. browser_vision turns the extension's
capture into the usual native/auxiliary vision result.

Bridge: forwards controller commands only to a connection that registered,
refuses unknown or oversized commands, relays results.

Extension: service-worker controller with its own native connection,
trusted chrome.debugger input (press/release only: a hover move waits 5 s on
background tabs), refusal of password and payment-card fields and of
browser, extension, file and Web Store pages, panel switch, Stop, tab
hand-over, recent actions, Alt+Shift+A and right-click "send to AITURK".
Cancelling Chrome's debugging bar stops the agent. Existing panel flows and
privacy rules are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-15 08:38:52 +03:00
yilsem 1acb5dd90f fix(mobile): wire plugin catalog and session-scoped subagent controls 2026-10-07 22:37:49 +03:00
yilsemandClaude Opus 5.5 67a99be224 feat(aiturk): produce media through the AITURK CLI, stop adding the media MCP server (beta.13)
Owner decision (3 Oct 2026): where the AITURK CLI is available, TurkServis
models are reached through it, not MCP. The backend no longer writes a
`turkservis-media` MCP server into config.yaml on startup or when a member
endpoint is saved. Existing entries, including disabled ones, are left exactly
as they are. A bundled `aiturk-media` skill teaches the agent to list and run
media with `aiturk media`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012wwqJMAuhMBMWvsvNLFGb9
2026-10-03 11:03:47 +03:00
yilsem 8f38fd53e4 fix(ide): upgrade managed agent and migrate existing member media connection 2026-09-05 15:35:04 +03:00
yilsem e874ce9c4c feat(aiturk): connect shared media MCP with the member provider key 2026-09-05 14:48:52 +03:00
yilsem 03634b1ca3 Import AITURK IDE 1.0.0-beta.1 from Hermes 63279301; preserve MIT license 2026-09-05 13:26:46 +03:00