Lokey

Lokey is a local-first Chrome extension for professional web developers who need to connect SSO-protected remote environments with a local development host. When frontend applications are developed locally, teams often need to test against real development, staging, verification, or production-like API environments. In those workflows, developers may run into repeated friction: SSO login flows return to the remote site instead of localhost, authentication cookies are not available to the local app, and configured API infrastructure may reject localhost origins during local CORS/origin checks. Lokey helps solve those local development problems through user-configured profiles. You can configure: - local host and port; - remote site host; - authentication cookie key; - SSO URL patterns; - app entry paths; - API hosts that need origin/referer header replacement; - optional region and language navigation data. With those settings, Lokey can: - detect a configured SSO login flow and return the active tab to the configured local app; - copy selected authentication cookies from a user-configured, Chrome-approved remote domain to the configured local development host as session cookies; - show login status in the extension popup and local floating panel; - navigate local apps by app path, region, and language; - request Chrome host permissions only for domains configured by the user; - modify origin and referer headers for explicitly configured API hosts to support local development requests. Lokey is designed for local-first operation. Lokey does not operate a backend server, does not include analytics, does not use advertising, and does not transmit extension data to the developer. Configuration, cookie handling, navigation detection, permission checks, and header rules are processed inside the Chrome extension runtime on the user's browser. Lokey is intended only for authorized development workflows. Use it only with systems, accounts, domains, cookies, API hosts, and presets that you are permitted to access. Lokey does not grant access to any remote system and does not replace your organization’s security policies or access-control rules. Users are responsible for reviewing imported presets, approving only expected Chrome host permissions, and using Lokey in accordance with their employer, client, or organization’s security and data-handling requirements. Lokey is not a password manager, VPN, security scanner, monitoring tool, or general browsing assistant. It is a developer tool for bridging configured local development environments with trusted remote authentication and API environments.