feat: add azure openai support #92

thegovind · 2025-04-16T19:52:30Z

Summary

Adds optional Azure OpenAI support alongside the existing OpenAI flow. When AZURE_OPENAI_ENDPOINT (plus related env vars) is set, Codex will authenticate via Entra ID and call the Responses API against your Azure OpenAI deployments. Otherwise it falls back to the standard OPENAI_API_KEY path.

Closes #11 #174

What’s Changed

Model & Agent code
- model‑utils.ts
  - Detects AZURE_OPENAI_ENDPOINT; if present, uses @azure/identity’s DefaultAzureCredential and the SDK’s AzureOpenAI client to list deployments via Responses API.
  - Falls back to OPENAI_API_KEY flow or default model list on errors.
- agent-loop.ts
  - Updated reasoning initialization to work correctly when using Azure models.
Configuration
- Exported four new env vars in config.ts:
  - AZURE_OPENAI_ENDPOINT
  - AZURE_OPENAI_API_VERSION
  - AZURE_OPENAI_DEPLOYMENT (optional)
  - AZURE_OPENAI_API_KEY (fallback)
CLI error handling
- cli.tsx now errors if neither OPENAI_API_KEY nor AZURE_OPENAI_ENDPOINT is configured.
- Enhanced error messaging to guide through az login and Azure env‑var setup.
README updates
- Added a “Using Azure OpenAI” section under Configuration with bash export examples.
- Clarified that Entra ID auth (via Azure AD) is supported for Azure OpenAI.
Dependencies
- Added @azure/identity and bumped openai to include AzureOpenAI support.

How to Test

Deploy your model
- Go to [Azure AI Foundry](https://ai.azure.com) and deploy either o4‑mini or o3 to your Azure OpenAI resource.

Set up env vars

az login
export AZURE_OPENAI_ENDPOINT="https://<your‑resource>.openai.azure.com"
export AZURE_OPENAI_API_VERSION="2024-02-01"
export AZURE_OPENAI_DEPLOYMENT="your-deployment-name" # optional
export AZURE_OPENAI_API_KEY="your-api-key" # if not present, it'll use Entra ID

Get the Codex CLI by building from your PR branch
Clone your specific PR branch and build the CLI:

# Clone your fork of the repository
git clone https://github.com/thegovind/codex.git

# Navigate into the cloned repository
cd codex

# Checkout your specific PR branch
git checkout gk/azure-openai

# Navigate to the CLI package directory
cd codex-cli

# Enable corepack
corepack enable

# Install dependencies and build
pnpm install
pnpm build

# Get the usage and the options (optional)
node ./dist/cli.js --help

# After building, you can either:
# - Run the locally-built CLI directly using `node ./dist/cli.js <args>`
# - Link the command globally for convenience using `pnpm link` (then use `codex <args>`)

Invoke Codex
Run the locally built CLI using node from the codex-cli directory:
```
node ./dist/cli.js "explain this function"
```
(Alternatively, if you ran pnpm link in the previous step, you can simply use codex "explain this function" from anywhere).

Tests

Updated and ran all tests successfully
~~Update default API version to 2025-04-01-preview once it’s available in Azure OpenAI~~
(Note: Temporary Conditional logic added for Azure OpenAI will be removed in another PR)

Checklist

Model listing and agent loop updated for Azure path
Config exports for Azure env vars
CLI guards/error messages for missing credentials
README examples for Azure OpenAI
Added @azure/identity, bumped openai dependency
Write and update tests for Azure code path

cc @theabhinavdas @nikodem-wrona for SDK review.

codex-cli/package.json

alioftech · 2025-04-16T20:42:35Z

That was fast! Was looking for this. Thanks

github-actions · 2025-04-16T22:58:27Z

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

thegovind · 2025-04-16T23:00:22Z

I have read the CLA Document and I hereby sign the CLA

junseinagao · 2025-04-17T01:42:32Z

@thegovind

Hi,

I tried running this PR, but Codex still throws the error “Missing OpenAI API key.” even though I’ve set the following environment variables: AZURE_OPENAI_ENDPOINT, AZURE_OPENAI_API_VERSION, and AZURE_OPENAI_DEPLOYMENT.

It looks like we might also need to update cli.tsx.

theabhinavdas · 2025-04-17T02:49:51Z

@thegovind Adding tests will also help.

thegovind · 2025-04-17T03:14:46Z

@thegovind

Hi,

I tried running this PR, but Codex still throws the error “Missing OpenAI API key.” even though I’ve set the following environment variables: AZURE_OPENAI_ENDPOINT, AZURE_OPENAI_API_VERSION, and AZURE_OPENAI_DEPLOYMENT.

It looks like we might also need to update cli.tsx.

@junseinagao Thanks for testing. I’ve only added support for Entra ID, so you’ll need to run az login locally before running this and ensure the relevant Azure environment variables are set. I’ve also updated the CLI instructions as you suggested. Thank you!

thegovind · 2025-04-17T03:15:00Z

@thegovind Adding tests will also help.

Agree, working on it.

adhishthite · 2025-04-17T03:17:41Z

@thegovind

Thanks for this, can we make it work with non-Entra ID Azure OpenAI as well, i.e.: Just the AZURE_OPENAI_KEY and stuff? Would be much more helpful!

Thanks!

adhishthite · 2025-04-17T03:50:49Z

@thegovind

#174

Since you're working on this, can you also take a look at this issue above - so that a TON of people will benefit? Much appreciated.

tibo-openai · 2025-04-17T03:54:17Z

Would it be possible to build this in a way that doesn't depend on "@azure/identity"?

thegovind · 2025-04-17T04:50:08Z

@adhishthite @tibo-openai @junseinagao @theabhinavdas @alioftech and others following this - Thanks for your patience! I’ll be pushing more updates soon, but we need to wait for our Azure OpenAI Inference team (@YunsongB) to update the underlying APIs before everything works end-to-end.

The latest API version from our side needs to reach parity with OpenAI (with 2025-04-01-preview):
Azure OpenAI Inference Specs

If you try to use the most recent spec (2025-03-01-preview), you'll likely hit this:

Specifically, ReasoningItem has been updated in OpenAI’s latest inference API. This change needs to propagate into Azure OpenAI with a new API version so the reasoning summary can be set properly in the Codex loop.

You could add a conditional for AOAI here, but that’s probably unnecessary since the update is expected very shortly.

So in short: let’s not put the cart before the horse 😄 I’ll follow up with the commits as soon as the updated APIs are live - likely next week.

pskoett · 2025-04-17T07:25:08Z

This is great, win win

moosh3 · 2025-04-18T14:02:43Z

Nice!

APiTJLillo · 2025-04-18T14:52:04Z

Amazing, keeping an eye on this!

adamgoslin · 2025-04-18T16:56:51Z

@thegovind Any timeline for the update to the Azure openai inference api? If the release is delayed, it might be wise to add the conditional for AOAI and get this merged. You can always come back and remove it.

arynaq · 2025-04-25T10:13:58Z

Can we get this in? OpenAI org verification wants my passport, no thank you, I will run this via Azure

cevatkerim · 2025-04-26T13:45:07Z

/compact didn't work for me I had to make some changes. Can I contribute somehow? @thegovind

thegovind · 2025-04-26T14:12:57Z

/compact didn't work for me I had to make some changes. Can I contribute somehow? @thegovind

Yes, please go ahead-thank you. As for conflicts, I’ve resolved merge conflicts countless times now. I’ll do it one last time once I know that OpenAI and @tibo-openai intend to support Azure OpenAI. Frankly, it’s starting to look like they don’t, which goes against the spirit of open source.

bsormagec · 2025-04-26T14:21:44Z

/compact didn't work for me I had to make some changes. Can I contribute somehow? @thegovind

Yes, please go ahead-thank you. As for conflicts, I’ve resolved merge conflicts countless times now. I’ll do it one last time once I know that OpenAI and @tibo-openai intend to support Azure OpenAI. Frankly, it’s starting to look like they don’t, which goes against the spirit of open source.

Create a new fork similar to open-codex if they're unresponsive; there's no need to handle it that way. :)

heymaaz · 2025-04-26T14:30:34Z

Would it be possible to build this in a way that doesn't depend on "@azure/identity"?

Yes, please go ahead-thank you. As for conflicts, I’ve resolved merge conflicts countless times now. I’ll do it one last time once I know that OpenAI and @tibo-openai intend to support Azure OpenAI. Frankly, it’s starting to look like they don’t, which goes against the spirit of open source.

I think that they don't want to add the azure/identity dependency @thegovind

thegovind · 2025-04-26T14:53:09Z

Would it be possible to build this in a way that doesn't depend on "@azure/identity"?

Yes, please go ahead-thank you. As for conflicts, I’ve resolved merge conflicts countless times now. I’ll do it one last time once I know that OpenAI and @tibo-openai intend to support Azure OpenAI. Frankly, it’s starting to look like they don’t, which goes against the spirit of open source.

I think that they don't want to add the azure/identity dependency @thegovind

@heymaaz @bsormagec @tibo-openai
This approach is not consistent with OpenAI’s official language SDKs, whether in Python or in the recommended Node implementation. Many of the companies I support prohibit static API keys for security reasons and instead require token-based authentication and authorization, which the official SDKs address through the azure-identity library. I do not intend to launch another fork such as “azure-codex” - the goal is a positive-sum outcome that supports both OpenAI and Azure OpenAI so GPT models remain relevant for SWE agents. I trust OpenAI will act in that same spirit of partnership.

jslitzkerttcu · 2025-04-26T17:56:56Z

@tibo-openai can we get a response on this? many of us are waiting for this to be implemented so that we can use the official release and not create a separate fork.

seanabreau · 2025-04-26T23:53:48Z

@tibo-openai can we get a response on this? many of us are waiting for this to be implemented so that we can use the official release and not create a separate fork.

In the openai-python library, azure-identity is currently listed only as a dev dependency.

Could an alternative approach work here to avoid adding it as a mandatory dependency?

For instance:

Modify the client initialization to accept an Azure AD token string or a token provider function directly.
Document how users can leverage azure-identity (or other methods) in their own code to generate the necessary tokens to pass to the client.

This approach seems like it could provide the needed Azure AD authentication flexibility without imposing the dependency on all users of the library. Would you be open to a solution like this?

thegovind · 2025-04-27T00:30:02Z

@tibo-openai can we get a response on this? many of us are waiting for this to be implemented so that we can use the official release and not create a separate fork.

In the openai-python library, azure-identity is currently listed only as a dev dependency.

Could an alternative approach work here to avoid adding it as a mandatory dependency?

For instance:

Modify the client initialization to accept an Azure AD token string or a token provider function directly.

Document how users can leverage azure-identity (or other methods) in their own code to generate the necessary tokens to pass to the client.

This approach seems like it could provide the needed Azure AD authentication flexibility without imposing the dependency on all users of the library. Would you be open to a solution like this?

@seanabreau - I’m happy to refactor to highlight azure-identity in an example (similar to official SDK), but first I need clarity on one point: will OpenAI and @tibo-openai support Azure OpenAI as a target for Codex?

Code generation with Codex and GitHub Copilot was our first proof of PMF for transformer models, well before ChatGPT captured the spotlight. Building on that collaborative ethos, now extended to open-source contributions, I trust OpenAI will guide Codex so it remains valuable to developers everywhere, including those on Azure OpenAI.

Frankly, with Claude and Gemini gaining ground, our relevance and usage are no longer where they once were with Dev audience. Ensuring Codex works on Azure OpenAI would be a decisive step toward regaining that momentum.

pablospe · 2025-04-27T18:27:48Z

2025-04-01-preview inference API in our data plane (current ETA is 4/22)

One question. It seems a bit of delay for this. Any idea why? It seems they are going directly to 2025-05-01: Azure/azure-rest-api-specs#34051?

Nepomuceno · 2025-04-28T19:50:38Z

Do we know if OpenAI will give any response about this support ? Is there a way to get it working today using the API key method or not even that work ?

APiTJLillo · 2025-04-28T19:53:26Z

You can open the fork that was made for this pull request and download/run through there. I was able to successfully do it, I can't remember how. I think Manus told me how.

thegovind · 2025-04-29T04:08:41Z

You can open the fork that was made for this pull request and download/run through there. I was able to successfully do it, I can't remember how. I think Manus told me how.

Yes, my fork will remain available for use with Azure OpenAI. Instructions are above. You'll need to set AZURE_OPENAI_ENDPOINT and authenticate using either az login (Entra ID - token based) or Azure OpenAI API Keys. Provision/retrieve these credentials via Azure AI Foundry

Nepomuceno · 2025-04-29T07:47:30Z

My question was more until this is not merged is there some environment variables that I can set tp be able to use it with azureopenai and an api key from main ?

pablospe · 2025-04-29T09:16:45Z

Do we know if OpenAI will give any response about this support ? Is there a way to get it working today using the API key method or not even that work ?

You might want to try using the litellm proxy and set the OPENAI_BASE_URL as a workaround, rather than waiting for this PR to be merged. Here’s an example:
#26 (comment)

While we’ll likely need to be patient for the PR to be merged (it currently has conflicts with the main branch), using the litellm proxy is straightforward and I would say generally recommended. It allows you to support a wide range of models without having to update every piece of software to use Azure OpenAI—just point your applications to the proxy and you’re good to go.

chriswl · 2025-04-29T19:25:56Z

With the changes on this branch, the AOAI settings are not applied when asking to explain the current command (press x in chat when a command needs to be approved). This uses a vanilla OpenAI instance: code

CetinSert · 2025-04-30T07:57:24Z

Everyone! Let's get this rolling!

ilovetocode · 2025-04-30T18:43:10Z

below are the steps I took to get the fork from thegovind working (these may or may not all be required, but, it is what worked for me):

build fork locally and point PATH to ./codex-cli/bin/cli.js
unset OPENAI_API_KEY, else openai provider is used
create openai azure resource manually not through IaC due to this
regional endpoint didn't work, only, the *.openai.azure.com endpoint worked
deployment name seemingly must match model name

and set the env vars:

export AZURE_OPENAI_ENDPOINT="https://<your-instance-name>.openai.azure.com"
export AZURE_OPENAI_DEPLOYMENT="o4-mini"
export AZURE_OPENAI_API_KEY="<your key>"
export AZURE_OPENAI_API_VERSION="2025-04-01-preview" <- previous versions do not seem to support the responses API, and 2025-05-01-preview returns a 404

is there any real reason this pr hasn't been merged?

fouad-openai · 2025-04-30T23:29:19Z

hey @thegovind thanks for this contribution! we landed a PR to add support for multiple providers a ~week ago and would be great if you could use the latest as starting point, here's providers.ts as a reference point

thegovind · 2025-05-01T02:22:26Z

hey @thegovind thanks for this contribution! we landed a PR to add support for multiple providers a ~week ago and would be great if you could use the latest as starting point, here's providers.ts as a reference point

Thank you, @fouad-openai! Working on it now.

thegovind · 2025-05-01T05:11:11Z

hey @thegovind thanks for this contribution! we landed a PR to add support for multiple providers a ~week ago and would be great if you could use the latest as starting point, here's providers.ts as a reference point

Hi @fouad-openai @tibo-openai I'm starting a separate PR (please leave this one open for now) - #769 - as the provider approach is quite different from what Codex was released with.

Now, I have 7 tests in main that are failing. I'm not sure if others are seeing this as well (this is on Windows, but I tested in both bash and pwsh). It would be good to resolve this first.

I've tested my changes with Azure OpenAI locally, and they are working fine.

assinchu · 2025-05-01T22:47:35Z

it just hangs, any idea? how to run codex in debug mode

thegovind · 2025-05-06T19:17:05Z

it just hangs, any idea? how to run codex in debug mode

Have you tried in #769 branch? I'm still waiting on OpenAI to merge #769

@theabhinavdas

## Summary This PR introduces support for Azure OpenAI as a provider within the Codex CLI. Users can now configure the tool to leverage their Azure OpenAI deployments by specifying `"azure"` as the provider in `config.json` and setting the corresponding `AZURE_OPENAI_API_KEY` and `AZURE_OPENAI_API_VERSION` environment variables. This functionality is added alongside the existing provider options (OpenAI, OpenRouter, etc.). Related to #92 **Note:** This PR is currently in **Draft** status because tests on the `main` branch are failing. It will be marked as ready for review once the `main` branch is stable and tests are passing. --- ## What’s Changed - **Configuration (`config.ts`, `providers.ts`, `README.md`):** - Added `"azure"` to the supported `providers` list in `providers.ts`, specifying its name, default base URL structure, and environment variable key (`AZURE_OPENAI_API_KEY`). - Defined the `AZURE_OPENAI_API_VERSION` environment variable in `config.ts` with a default value (`2025-03-01-preview`). - Updated `README.md` to: - Include "azure" in the list of providers. - Add a configuration section for Azure OpenAI, detailing the required environment variables (`AZURE_OPENAI_API_KEY`, `AZURE_OPENAI_API_VERSION`) with examples. - **Client Instantiation (`terminal-chat.tsx`, `singlepass-cli-app.tsx`, `agent-loop.ts`, `compact-summary.ts`, `model-utils.ts`):** - Modified various components and utility functions where the OpenAI client is initialized. - Added conditional logic to check if the configured `provider` is `"azure"`. - If the provider is Azure, the `AzureOpenAI` client from the `openai` package is instantiated, using the configured `baseURL`, `apiKey` (from `AZURE_OPENAI_API_KEY`), and `apiVersion` (from `AZURE_OPENAI_API_VERSION`). - Otherwise, the standard `OpenAI` client is instantiated as before. - **Dependencies:** - Relies on the `openai` package's built-in support for `AzureOpenAI`. No *new* external dependencies were added specifically for this Azure implementation beyond the `openai` package itself. --- ## How to Test *This has been tested locally and confirmed working with Azure OpenAI.* 1. **Configure `config.json`:** Ensure your `~/.codex/config.json` (or project-specific config) includes Azure and sets it as the active provider: ```json { "providers": { // ... other providers "azure": { "name": "AzureOpenAI", "baseURL": "https://YOUR_RESOURCE_NAME.openai.azure.com", // Replace with your Azure endpoint "envKey": "AZURE_OPENAI_API_KEY" } }, "provider": "azure", // Set Azure as the active provider "model": "o4-mini" // Use your Azure deployment name here // ... other config settings } ``` 2. **Set up Environment Variables:** ```bash # Set the API Key for your Azure OpenAI resource export AZURE_OPENAI_API_KEY="your-azure-api-key-here" # Set the API Version (Optional - defaults to `2025-03-01-preview` if not set) # Ensure this version is supported by your Azure deployment and endpoint export AZURE_OPENAI_API_VERSION="2025-03-01-preview" ``` 3. **Get the Codex CLI by building from this PR branch:** Clone your fork, checkout this branch (`feat/azure-openai`), navigate to `codex-cli`, and build: ```bash # cd /path/to/your/fork/codex git checkout feat/azure-openai # Or your branch name cd codex-cli corepack enable pnpm install pnpm build ``` 4. **Invoke Codex:** Run the locally built CLI using `node` from the `codex-cli` directory: ```bash node ./dist/cli.js "Explain the purpose of this PR" ``` *(Alternatively, if you ran `pnpm link` after building, you can use `codex "Explain the purpose of this PR"` from anywhere)*. 5. **Verify:** Confirm that the command executes successfully and interacts with your configured Azure OpenAI deployment. --- ## Tests - [x] Tested locally against an Azure OpenAI deployment using API Key authentication. Basic commands and interactions confirmed working. --- ## Checklist - [x] Added Azure provider details to configuration files (`providers.ts`, `config.ts`). - [x] Implemented conditional `AzureOpenAI` client initialization based on provider setting. - [x] Ensured `apiVersion` is passed correctly to the Azure client. - [x] Updated `README.md` with Azure OpenAI setup instructions. - [x] Manually tested core functionality against a live Azure OpenAI endpoint. - [x] Add/update automated tests for the Azure code path (pending `main` stability). cc @theabhinavdas @nikodem-wrona @fouad-openai @tibo-openai (adjust as needed) --- I have read the CLA Document and I hereby sign the CLA

fouad-openai · 2025-05-10T23:24:16Z

closing now that #769 merged

add azure openai support

124724f

thegovind marked this pull request as ready for review April 16, 2025 19:54

theabhinavdas reviewed Apr 16, 2025

View reviewed changes

codex-cli/package.json Outdated Show resolved Hide resolved

thegovind added 3 commits April 16, 2025 14:09

only use entra id flow for AOAI

ce1390d

Merge branch 'main' into gk/azure-openai

db4a7a5

add updated package-lock for ci build error

d8fb41f

thegovind mentioned this pull request Apr 16, 2025

Supporting Azure OpenAI #11

Open

github-actions bot added a commit that referenced this pull request Apr 16, 2025

@thegovind has signed the CLA in #92

e7bcaf8

ronaldchwu mentioned this pull request Apr 16, 2025

Support providing azureADToken as credential openai/openai-node#1467

Closed

1 task

thegovind added 2 commits April 16, 2025 17:35

fix tests and linter issues

8658d06

Merge branch 'main' into gk/azure-openai

d8c883b

thegovind added 2 commits April 16, 2025 19:46

update Azure OpenAI instructions for Entra ID

4f04005

Merge branch 'main' into gk/azure-openai

7695d3a

updated cli instructions and fixed local build where zod was missing

fd79649

tibo-openai mentioned this pull request Apr 17, 2025

Azure OpenAI Python SDK works, but codex CLI fails with 404 #174

Open

thegovind mentioned this pull request Apr 26, 2025

Azure Open AI #681

Open

fouad-openai changed the title ~~(feat) add azure openai support~~ feat: add azure openai support Apr 30, 2025

thegovind mentioned this pull request May 1, 2025

Adds Azure OpenAI support #769

Merged

7 tasks

fouad-openai closed this May 10, 2025

openai locked and limited conversation to collaborators May 10, 2025

feat: add azure openai support #92

feat: add azure openai support #92

Uh oh!

Conversation

thegovind commented Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What’s Changed

How to Test

Tests

Checklist

Uh oh!

Uh oh!

alioftech commented Apr 16, 2025

Uh oh!

github-actions bot commented Apr 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

thegovind commented Apr 16, 2025

Uh oh!

junseinagao commented Apr 17, 2025

Uh oh!

theabhinavdas commented Apr 17, 2025

Uh oh!

thegovind commented Apr 17, 2025

Uh oh!

thegovind commented Apr 17, 2025

Uh oh!

adhishthite commented Apr 17, 2025

Uh oh!

adhishthite commented Apr 17, 2025

Uh oh!

tibo-openai commented Apr 17, 2025

Uh oh!

thegovind commented Apr 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pskoett commented Apr 17, 2025

Uh oh!

moosh3 commented Apr 18, 2025

Uh oh!

APiTJLillo commented Apr 18, 2025

Uh oh!

adamgoslin commented Apr 18, 2025

Uh oh!

arynaq commented Apr 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cevatkerim commented Apr 26, 2025

Uh oh!

thegovind commented Apr 26, 2025

Uh oh!

bsormagec commented Apr 26, 2025

Uh oh!

heymaaz commented Apr 26, 2025

Uh oh!

thegovind commented Apr 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jslitzkerttcu commented Apr 26, 2025

Uh oh!

seanabreau commented Apr 26, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

thegovind commented Apr 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pablospe commented Apr 27, 2025

Uh oh!

Nepomuceno commented Apr 28, 2025

Uh oh!

APiTJLillo commented Apr 28, 2025

Uh oh!

thegovind commented Apr 29, 2025

Uh oh!

Nepomuceno commented Apr 29, 2025

Uh oh!

pablospe commented Apr 29, 2025

Uh oh!

chriswl commented Apr 29, 2025

thegovind commented Apr 16, 2025 •

edited

Loading

github-actions bot commented Apr 16, 2025 •

edited

Loading

thegovind commented Apr 17, 2025 •

edited

Loading

arynaq commented Apr 25, 2025 •

edited

Loading

thegovind commented Apr 26, 2025 •

edited

Loading

seanabreau commented Apr 26, 2025 •

edited

Loading

thegovind commented Apr 27, 2025 •

edited

Loading

thegovind commented May 1, 2025 •

edited

Loading

assinchu commented May 1, 2025 •

edited

Loading