Allow tailscale development websites

Open
#34,148 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet

Research direction

No file, test, or entry point is named. Start by reproducing browser automation against a foo.bar.ts.net address and trace where the corporate-network block is reported. Done means the reported Tailscale development site is usable without removing the existing network protection behavior.

Written by the indexing model from the issue text.

Description

app browser bug connectivity safety-check
What version of the Codex App are you using (From “About Codex” dialog)?

26.715.31925

What subscription do you have?

Pro ($240)

What platform is your computer?

Darwin 25.5.0 arm64 arm, Linux 7.0.11-76070011-generic x86_64 x86_64

What issue are you seeing?

I used to do this: launch dev env on my dev Linux machine, open it in Codex Browser via Tailscale address (valid SSL cert etc.), and let codex make changes via ssh. This way I can use macOS Codex app for browser feedback, while development happens on its native Linux environment. Unfortunately, recently Codex started blocking my Tailscale address due to "corporate network security measurements". Tailscale network is totally private and has nothing to do with corporate, just add your computer in Tailscale and get its own .ts.net personal subdomain with valid CERT. It was very convenient.

What steps can reproduce the bug?

Ask codex to do browser automation with your foo.bar.ts.net personal network

What is the expected behavior?

Don't block, do work

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.