{"id":3547,"date":"2026-05-20T15:41:37","date_gmt":"2026-05-20T15:41:37","guid":{"rendered":"https:\/\/aiopsschool.com\/blog\/?p=3547"},"modified":"2026-05-20T15:41:39","modified_gmt":"2026-05-20T15:41:39","slug":"codex-cli-permissions-sandboxing-and-account-switching-explained","status":"publish","type":"post","link":"https:\/\/aiopsschool.com\/blog\/codex-cli-permissions-sandboxing-and-account-switching-explained\/","title":{"rendered":"Codex CLI Permissions, Sandboxing, and Account Switching Explained"},"content":{"rendered":"\n
    \n
  1. How to Use Codex CLI Safely Without Losing Context<\/strong><\/li>\n\n\n\n
  2. Codex CLI Permissions, Sandboxing, and Account Switching Explained<\/strong><\/li>\n\n\n\n
  3. Stop Typing \u201cYes\u201d in Codex: A Practical Guide to Approvals and Sandboxes<\/strong><\/li>\n\n\n\n
  4. How to Give Codex the Right Access Without Going Full YOLO<\/strong><\/li>\n\n\n\n
  5. Codex CLI Workflow: Workspace Write, Extra Directories, Resume, and Login Switching<\/strong><\/li>\n<\/ol>\n\n\n\n

    Stop Typing \u201cYes\u201d in Codex: A Practical Guide to Approvals and Sandboxes<\/strong><\/p>\n\n\n\n

    \n\n\n\n

    Stop Typing \u201cYes\u201d in Codex: A Practical Guide to Approvals, Sandboxes, Extra Directories, and Account Switching<\/h1>\n\n\n\n

    When you start using Codex CLI seriously, you quickly run into a few practical questions:<\/p>\n\n\n\n

    \u201cHow do I stop Codex from asking yes, yes, yes again and again?\u201d<\/p>\n\n\n\n

    \u201cHow do I allow it to write files in \/tmp<\/code> or another folder?\u201d<\/p>\n\n\n\n

    \u201cWhat if one Codex account hits the usage limit and I need to switch accounts?\u201d<\/p>\n\n\n\n

    \u201cAnd most importantly: will I lose my current context?\u201d<\/p>\n\n\n\n

    This tutorial walks through all of those topics in a simple, practical way.<\/p>\n\n\n\n

    Codex CLI has two major controls you should understand: sandbox mode<\/strong> and approval mode<\/strong>. The sandbox controls what Codex can access, and the approval mode controls when Codex pauses to ask you before running something. OpenAI\u2019s Codex docs describe --sandbox workspace-write<\/code> with --ask-for-approval on-request<\/code> as the common \u201cAuto\u201d setup: Codex can read, edit, and run commands inside the working directory, but asks before going outside the workspace or doing things like network access. (OpenAI Developers<\/a>)<\/p>\n\n\n\n

    \n\n\n\n

    1. The basic Codex command<\/h2>\n\n\n\n

    The simplest way to start Codex is:<\/p>\n\n\n\n

    codex\n<\/code><\/pre>\n\n\n\n
    This opens the interactive Codex terminal interface.<\/p>\n\n\n\n
    But if you want Codex to edit code in your current project folder without constantly asking for approval, use:<\/p>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    This is a good everyday setup.<\/p>\n\n\n\n
    It means:<\/p>\n\n\n\n
    Codex can work inside the current project folder.\nCodex can edit files there.\nCodex can run commands there.\nCodex will ask before doing higher-risk things outside that boundary.\n<\/code><\/pre>\n\n\n\n
    That is usually much better than blindly approving everything.<\/p>\n\n\n\n
    \n\n\n\n
    2. What --sandbox workspace-write<\/code> means<\/h2>\n\n\n\n
    This flag:<\/p>\n\n\n\n
    --sandbox workspace-write\n<\/code><\/pre>\n\n\n\n
    means Codex can write inside the active workspace.<\/p>\n\n\n\n
    For example, if you are inside this folder:<\/p>\n\n\n\n
    cd ~\/projects\/my-app\ncodex --sandbox workspace-write\n<\/code><\/pre>\n\n\n\n
    Codex can usually work inside:<\/p>\n\n\n\n
    ~\/projects\/my-app\n<\/code><\/pre>\n\n\n\n
    It can do things like:<\/p>\n\n\n\n
    edit src\/index.js\ncreate tests\/app.test.js\nrun npm test\nrun pytest\nupdate package files\n<\/code><\/pre>\n\n\n\n
    But it should not freely modify random files elsewhere on your machine.<\/p>\n\n\n\n
    So this is allowed:<\/p>\n\n\n\n
    ~\/projects\/my-app\/src\/main.py\n<\/code><\/pre>\n\n\n\n
    But this may require permission:<\/p>\n\n\n\n
    ~\/Documents\/another-project\/file.py\n\/etc\/hosts\n~\/.ssh\/config\n<\/code><\/pre>\n\n\n\n
    OpenAI\u2019s docs describe the sandbox as the boundary that lets Codex act autonomously without giving it unrestricted access to your machine. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    \n\n\n\n
    3. What --ask-for-approval<\/code> means<\/h2>\n\n\n\n
    The approval mode controls when Codex asks you before running a command.<\/p>\n\n\n\n
    Common options are:<\/p>\n\n\n\n
    --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    and:<\/p>\n\n\n\n
    --ask-for-approval never\n<\/code><\/pre>\n\n\n\n
    OpenAI\u2019s CLI reference lists --ask-for-approval<\/code> values including untrusted<\/code>, on-request<\/code>, and never<\/code>. It also notes that on-request<\/code> is preferred for interactive runs, while never<\/code> is more suitable for non-interactive runs. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Recommended for normal use<\/h3>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    This is the best balance.<\/p>\n\n\n\n
    Codex can work normally inside your project, but if it needs something more sensitive, it asks.<\/p>\n\n\n\n
    Fewer prompts<\/h3>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval never\n<\/code><\/pre>\n\n\n\n
    This means Codex will not stop to ask you for approval.<\/p>\n\n\n\n
    But there is a catch: it still must stay within the sandbox. If something is blocked, Codex may fail instead of asking.<\/p>\n\n\n\n
    So use never<\/code> when you already know the permissions are enough.<\/p>\n\n\n\n
    \n\n\n\n
    4. How to avoid typing yes<\/code> again and again<\/h2>\n\n\n\n
    Do not<\/strong> solve this by piping yes<\/code> into Codex:<\/p>\n\n\n\n
    yes | codex\n<\/code><\/pre>\n\n\n\n
    That is a bad idea because it can approve things you did not actually inspect. Tiny foot-gun, huge boot.<\/p>\n\n\n\n
    Instead, configure approvals properly.<\/p>\n\n\n\n
    For normal work:<\/p>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    For trusted local work where you do not want prompts:<\/p>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval never\n<\/code><\/pre>\n\n\n\n
    For one-shot automation:<\/p>\n\n\n\n
    codex exec --sandbox workspace-write --ask-for-approval never \"Fix the failing tests\"\n<\/code><\/pre>\n\n\n\n
    The important idea is this:<\/p>\n\n\n\n
    Do not auto-type yes.\nUse the approval policy designed for this.\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    5. How to give Codex access to another folder, such as \/tmp<\/code><\/h2>\n\n\n\n
    Sometimes Codex needs to write outside your project folder.<\/p>\n\n\n\n
    For example, it may need:<\/p>\n\n\n\n
    \/tmp\n~\/scratch\n~\/projects\/shared-library\n~\/Downloads\n<\/code><\/pre>\n\n\n\n
    The clean way to grant extra access is --add-dir<\/code>.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    Now Codex can work inside your current project folder and<\/strong> \/tmp<\/code>.<\/p>\n\n\n\n
    For multiple folders:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir \/tmp \\\n  --add-dir ~\/scratch \\\n  --add-dir ~\/projects\/shared-library\n<\/code><\/pre>\n\n\n\n
    OpenAI\u2019s CLI reference says --add-dir<\/code> grants additional directories write access alongside the main workspace, and you can repeat it for multiple paths. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    This is the best way to give Codex more room without removing all safety boundaries.<\/p>\n\n\n\n
    \n\n\n\n
    6. How to give access in advance<\/h2>\n\n\n\n
    Yes, you can give access in advance.<\/p>\n\n\n\n
    Use this pattern:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir \/tmp \\\n  --add-dir ~\/projects \\\n  --add-dir ~\/Downloads\n<\/code><\/pre>\n\n\n\n
    This tells Codex:<\/p>\n\n\n\n
    You may write inside the current project.\nYou may also write inside \/tmp.\nYou may also write inside ~\/projects.\nYou may also write inside ~\/Downloads.\nAsk me if you need anything else.\n<\/code><\/pre>\n\n\n\n
    For a smoother but still bounded setup:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval never \\\n  --add-dir \/tmp \\\n  --add-dir ~\/scratch\n<\/code><\/pre>\n\n\n\n
    This means:<\/p>\n\n\n\n
    Do not ask me.\nWork only inside the allowed areas.\n<\/code><\/pre>\n\n\n\n
    That is useful when you want Codex to complete a task without stopping every few minutes.<\/p>\n\n\n\n
    \n\n\n\n
    7. How to make these permissions permanent<\/h2>\n\n\n\n
    Typing long flags every time gets annoying. Very relatable. The terminal is already enough of a little goblin.<\/p>\n\n\n\n
    You can put defaults in:<\/p>\n\n\n\n
    ~\/.codex\/config.toml\n<\/code><\/pre>\n\n\n\n
    Example config:<\/p>\n\n\n\n
    sandbox_mode = \"workspace-write\"\napproval_policy = \"on-request\"<\/code><\/pre>\n\n\n
    [sandbox_workspace_write]<\/p>\n\n\n\n
    writable_roots = [ “\/tmp”, “\/home\/YOUR_USER\/scratch”, “\/home\/YOUR_USER\/projects\/shared-library” ]<\/p>\n\n\n\n
    Replace YOUR_USER<\/code> with your real username.<\/p>\n\n\n\n
    The Codex config reference documents sandbox_workspace_write.writable_roots<\/code> as additional writable roots when sandbox_mode = \"workspace-write\"<\/code>. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    You can also enable network access in this section if your workflow needs it:<\/p>\n\n\n\n
    sandbox_mode = \"workspace-write\"\napproval_policy = \"on-request\"<\/code><\/pre>\n\n\n
    [sandbox_workspace_write]<\/p>\n\n\n\n
    network_access = true writable_roots = [ “\/tmp”, “\/home\/YOUR_USER\/scratch” ]<\/p>\n\n\n\n
    OpenAI\u2019s docs note that network_access<\/code> allows outbound network access inside the workspace-write<\/code> sandbox. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    Use network access carefully, especially if your repo contains secrets or production credentials.<\/p>\n\n\n\n
    \n\n\n\n
    8. Should you use --yolo<\/code>?<\/h2>\n\n\n\n
    Codex has a full bypass mode:<\/p>\n\n\n\n
    codex --dangerously-bypass-approvals-and-sandbox\n<\/code><\/pre>\n\n\n\n
    There is also an alias:<\/p>\n\n\n\n
    codex --yolo\n<\/code><\/pre>\n\n\n\n
    This disables approvals and sandboxing.<\/p>\n\n\n\n
    OpenAI\u2019s CLI reference describes this as running commands without approvals or sandboxing, and says it should only be used inside an externally hardened environment. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    In plain English:<\/p>\n\n\n\n
    Use this only inside a disposable VM, dev container, or isolated machine.\nDo not use this casually on your main laptop.\n<\/code><\/pre>\n\n\n\n
    A safer alternative is almost always:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval never \\\n  --add-dir \/tmp \\\n  --add-dir ~\/scratch\n<\/code><\/pre>\n\n\n\n
    That gives Codex useful freedom without handing over your whole machine.<\/p>\n\n\n\n
    \n\n\n\n
    9. How to check what Codex can access<\/h2>\n\n\n\n
    Inside Codex, run:<\/p>\n\n\n\n
    \/status\n<\/code><\/pre>\n\n\n\n
    This shows useful information about the current session.<\/p>\n\n\n\n
    OpenAI\u2019s docs mention that \/status<\/code> can show which directories are in the workspace. They also note that the workspace can include the current directory and temporary directories like \/tmp<\/code>, depending on setup. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    So when in doubt, start Codex and run:<\/p>\n\n\n\n
    \/status\n<\/code><\/pre>\n\n\n\n
    Then verify whether \/tmp<\/code> or your extra folder is listed.<\/p>\n\n\n\n
    \n\n\n\n
    10. What to do when one Codex account hits the usage limit<\/h2>\n\n\n\n
    Sometimes your current Codex account hits its usage limit, and you need to login with another account.<\/p>\n\n\n\n
    The scary question is:<\/p>\n\n\n\n
    If I logout and login again, will I lose my Codex context?\n<\/code><\/pre>\n\n\n\n
    Usually, no.<\/p>\n\n\n\n
    Codex sessions are stored locally and can be resumed. The Codex docs say codex resume<\/code> can reopen previous interactive sessions, and a resumed run keeps the original transcript, plan history, and approvals. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    So the safe flow is:<\/p>\n\n\n\n
    1. Save or copy your session ID.\n2. Exit Codex.\n3. Logout.\n4. Login with the other account.\n5. Resume the previous session.\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    11. Safe account-switching workflow<\/h2>\n\n\n\n
    Inside your current Codex session, run:<\/p>\n\n\n\n
    \/status\n<\/code><\/pre>\n\n\n\n
    Copy the session ID.<\/p>\n\n\n\n
    Then exit Codex:<\/p>\n\n\n\n
    \/exit\n<\/code><\/pre>\n\n\n\n
    Now logout:<\/p>\n\n\n\n
    codex logout\n<\/code><\/pre>\n\n\n\n
    Then login with your other account:<\/p>\n\n\n\n
    codex login\n<\/code><\/pre>\n\n\n\n
    The Codex CLI reference says codex login<\/code> authenticates the CLI with a ChatGPT account, API key, or access token, and codex logout<\/code> removes saved credentials. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    After logging in again, resume:<\/p>\n\n\n\n
    codex resume\n<\/code><\/pre>\n\n\n\n
    Or resume the latest session in the current working directory:<\/p>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    Or resume a specific session:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    The CLI reference documents codex resume --last<\/code>, codex resume --all<\/code>, and codex resume <SESSION_ID><\/code>. (OpenAI Developers<\/a>)<\/p>\n\n\n\n
    \n\n\n\n
    12. Extra-safe handoff before switching accounts<\/h2>\n\n\n\n
    Before you logout, it is smart to ask Codex to create a handoff file.<\/p>\n\n\n\n
    Inside Codex, say:<\/p>\n\n\n\n
    Create a file named CODEX_HANDOFF.md summarizing:\n- current task\n- files changed\n- decisions made\n- commands already run\n- remaining TODOs\n- exact next command to continue\n<\/code><\/pre>\n\n\n\n
    Then in your terminal, save your current diff:<\/p>\n\n\n\n
    git status\ngit diff > codex-wip.patch\n<\/code><\/pre>\n\n\n\n
    This gives you a backup even if something weird happens.<\/p>\n\n\n\n
    Recommended full sequence:<\/p>\n\n\n\n
    # Inside Codex\n\/status\n<\/code><\/pre>\n\n\n\n
    Copy the session ID.<\/p>\n\n\n\n
    Create CODEX_HANDOFF.md with the current task summary and next steps.\n<\/code><\/pre>\n\n\n\n
    Then:<\/p>\n\n\n\n
    # Terminal\ngit status\ngit diff > codex-wip.patch\n\ncodex logout\ncodex login\n\ncodex resume --last\n<\/code><\/pre>\n\n\n\n
    If --last<\/code> does not pick the right session:<\/p>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    Or:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    13. Recommended commands for common situations<\/h2>\n\n\n\n
    Normal daily coding<\/h3>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    Use this when you want Codex to edit your project but still ask before risky actions.<\/p>\n\n\n\n
    Daily coding with \/tmp<\/code> access<\/h3>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    Use this when tools need temporary files.<\/p>\n\n\n\n
    Trusted repo with fewer prompts<\/h3>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval never \\\n  --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    Use this when you trust the repo and want fewer interruptions.<\/p>\n\n\n\n
    Extra writable project folders<\/h3>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir ~\/projects\/shared-library \\\n  --add-dir ~\/scratch\n<\/code><\/pre>\n\n\n\n
    Use this when Codex needs to modify a shared dependency or scratch folder.<\/p>\n\n\n\n
    Resume after account switch<\/h3>\n\n\n\n
    codex resume --last\n<\/code><\/pre>\n\n\n\n
    Or:<\/p>\n\n\n\n
    codex resume --all\n<\/code><\/pre>\n\n\n\n
    Or:<\/p>\n\n\n\n
    codex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    Full access mode<\/h3>\n\n\n\n
    codex --yolo\n<\/code><\/pre>\n\n\n\n
    Use only inside a disposable VM\/container. Not your main laptop. Seriously, do not let the robot do interpretive dance in your home directory.<\/p>\n\n\n\n
    \n\n\n\n
    14. My recommended setup<\/h2>\n\n\n\n
    For most developers, I recommend this command:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    And this config:<\/p>\n\n\n\n
    sandbox_mode = \"workspace-write\"\napproval_policy = \"on-request\"<\/code><\/pre>\n\n\n
    [sandbox_workspace_write]<\/p>\n\n\n\n
    writable_roots = [ “\/tmp”, “\/home\/YOUR_USER\/scratch” ]<\/p>\n\n\n\n
    This gives Codex enough freedom to be useful, while still keeping boundaries.<\/p>\n\n\n\n
    If you want fewer prompts in trusted projects, use:<\/p>\n\n\n\n
    codex --sandbox workspace-write \\\n  --ask-for-approval never \\\n  --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    But I would avoid --yolo<\/code> unless you are working inside a disposable dev container or VM.<\/p>\n\n\n\n
    \n\n\n\n
    15. Final cheat sheet<\/h2>\n\n\n\n
    # Start Codex safely with write access to current project\ncodex --sandbox workspace-write --ask-for-approval on-request\n<\/code><\/pre>\n\n\n\n
    # Allow Codex to also write to \/tmp\ncodex --sandbox workspace-write --ask-for-approval on-request --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    # Allow multiple folders\ncodex --sandbox workspace-write \\\n  --ask-for-approval on-request \\\n  --add-dir \/tmp \\\n  --add-dir ~\/scratch \\\n  --add-dir ~\/projects\/shared-library\n<\/code><\/pre>\n\n\n\n
    # Reduce approval prompts\ncodex --sandbox workspace-write --ask-for-approval never --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    # Check current session and workspace info\n\/status\n<\/code><\/pre>\n\n\n\n
    # Logout and login with another account\ncodex logout\ncodex login\n<\/code><\/pre>\n\n\n\n
    # Resume latest session\ncodex resume --last\n<\/code><\/pre>\n\n\n\n
    # Resume from any directory\ncodex resume --all\n<\/code><\/pre>\n\n\n\n
    # Resume exact session\ncodex resume <SESSION_ID>\n<\/code><\/pre>\n\n\n\n
    # Dangerous full-access mode \u2014 only in VM\/container\ncodex --yolo\n<\/code><\/pre>\n\n\n\n
    \n\n\n\n
    Conclusion<\/h2>\n\n\n\n
    The best Codex workflow is not \u201capprove everything.\u201d It is giving Codex the right amount of access before it starts.<\/p>\n\n\n\n
    Use workspace-write<\/code> for normal coding. Use --add-dir<\/code> when Codex needs extra folders like \/tmp<\/code>. Use on-request<\/code> when you still want safety checks. Use never<\/code> when the task is trusted and bounded. Use codex resume<\/code> when switching accounts so you do not lose context.<\/p>\n\n\n\n
    The practical default is:<\/p>\n\n\n\n
    codex --sandbox workspace-write --ask-for-approval on-request --add-dir \/tmp\n<\/code><\/pre>\n\n\n\n
    That setup is boring in the best way: powerful enough to get real coding done, but not wild enough to turn your laptop into a crime scene.<\/p>\n","protected":false},"excerpt":{"rendered":"
    Stop Typing \u201cYes\u201d in Codex: A Practical Guide to Approvals and Sandboxes Stop Typing \u201cYes\u201d in Codex: A Practical Guide […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3547","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3547","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=3547"}],"version-history":[{"count":1,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3547\/revisions"}],"predecessor-version":[{"id":3548,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/3547\/revisions\/3548"}],"wp:attachment":[{"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=3547"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=3547"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aiopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=3547"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}