{
  "id": 8486793,
  "title": "Switch Codex accounts seamlessly with AgentHop",
  "url": "https://urgent.news/2026/09/19/switch-codex-accounts-seamlessly-with-agenthop",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-19T15:28:48.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/thegm26/switch-codex-accounts-seamlessly-with-agenthop-11b7"
  },
  "original_language": "en",
  "account": "Storytime: Separating profiles from continuity proved to be a significant challenge for the author. Previously, they utilized distinct, legitimate Codex profiles for various contexts, such as personal work, client workspaces, and experimental environments. The repetitive process of logging out, changing the active setup, and reloading Codex was not only tedious but also disruptive. The author sought to make the switching process more seamless.\n\nInitially, they devised a simple CLI script to create isolated local profiles for each context and eliminate the need for repeated sign-out/re-authentication. This approach did improve speed, but it did not alleviate the need for manual status checking of each profile. The AgentHop CLI addressed this issue by displaying the current status of each local profile in a concise and readable format. Profiles that are currently usable are displayed first, while blocked profiles remain muted until reactivated by the provider.\n\nThe AgentHop dashboard emerged as a solution to the need for a quick status check without opening a separate window. It is designed to keep the overall account picture visible even when performing a simple status check. For more comprehensive tasks, such as adding an identity, inspecting details, or starting a new session, the full dashboard remains accessible.\n\nHowever, the author discovered that switching profiles alone was not sufficient to maintain the continuity of their work. The account-specific identity and session state were stored in the same local profile directory, causing confusion when attempting to continue a task after switching profiles. This prompted a more profound question about separating identity from continuity without creating separate \"universes\" for each account switch.\n\nAgentHop, an unofficial local-first dashboard, was born from this inquiry. It aims to manage AI coding CLI profiles while maintaining resumable work close at hand. The software separates profile identity from continuity, displays Codex's status, and prepares the next Codex command without treating profile changes as entirely new projects. AgentHop achieves this by keeping identity isolated in individual local profile directories and maintaining continuity through shared, provider-defined state storage.\n\nThe current AgentHop software includes an OpenAI Codex adapter and a local React + FastAPI control surface. It can discover and display the default and named local profiles, show their current status, and provide human-readable reset times when provided by the provider. The software also silences blocked profiles and groups usable profiles based on their status. AgentHop is independent of OpenAI and does not create accounts, combine subscriptions, bypass limits, or expose credentials. Its architecture is designed to keep identity isolated while preserving continuity, distinguishing the process of switching between accounts from creating entirely new environments.",
  "summary": "Story time I use separate, legitimate Codex profiles for distinct contexts: personal work, a client workspace, and experiments that should not inherit the same local setup. Keeping those contexts separate is useful; repeatedly navigating between them was not. Each time I needed a different profile, I would log out, change the active setup, reload Codex, and authenticate again. That routine was…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}