Rohan

📜 CHANGELOG April ’26: - Offline mode: for when stuck on localhost ️✈🚇🛜⁉️ - Azure External Identity - Secret reference tab completions - Self-serve OIDC SSO - Full auth rewrite. No more NextAuth! 🥳

New – PHASE_OFFLINE=1 Stuck on localhost? ✈️🚇🛜⁉️ All your secrets and configs remain securely available.

we also added detection for broken secret references, to make debugging easier and the overall ux for constructing references less error prone

this was really fun to build! the secret referencing syntax has grown in complexity as we've expanded the feature to support cross-app referencing on top of cross-env and folder based referencing, so this was a much needed dx improvement

📜 CHANGELOG March ’26: - CLI 2.0: AI skills, Python → Go rewrite, 90% smaller, 5× faster, 16 build targets - Azure Key Vault secrets sync - Azure External Identity - Authelia OIDC SSO - Go SDK 2.0: No CGO/libsodium, dynamic secrets - Secret types: Config, Secret, Sealed secret

@ScuderiaFerrari another build target for the @phasedotdev cli? 👀

“This is like a mushroom in Mario Kart.” 👀🍄 Now we know why…

watching the LLM perfectly perform the skill you spent 12 years mastering

turns out it was just stale cache on the frontend that required a simple refetch

the machines are getting incredibly good at writing code but are still susceptible to being easily misled or primed by bad context this initially seemed like a backend bug and claude confidently hallucinated a soft-delete issue and spun up a 50+line diff over 6 files

can't get no

Introducing: Phase Deployment Skill Imagine a forward-deployed engineer that automates @phasedotdev self-hosting and maintenance. Install the skill. Then tell Claude Code, Codex, Cursor, or any agent to deploy Phase: - Via Helm chart or Docker Compose - Set up a custom domain - Configure Let’s Encrypt certificates - Choose an internal or external managed database - Set up backups - Deploy inside your @Tailscale tailnet - Upgrades and migrations If something goes wrong Automatically debug it with all the relevant context available.

@icyphox congrats anirudh! stoked to see what you're building

very excited to finally announce this! our vision for tangled is big: we want to build foundational infrastructure for the next-generation of open source.

We are officially SOC 2 Type 2 compliant!

@nimishkarmali @phasedotdev Yep that could work pretty well and we can also integrate shortcuts for generating random secret values etc

@ascendance0 @phasedotdev What do you think about having a similar drop down UX for when entering the secret key for secret type: env, secret, sealed secret etc.

Working on a full revamp of secret referencing ux in the @phasedotdev console - Coming Soon™️

Got the Phase CLI running on my TP-Link OpenWRT router. Its mips lol The Golang rewrite was worth it 💯

We’ve put a ton of work into improving the GitHub integration in @phasedotdev. Starting now, you can sync secrets directly to: • GitHub Actions - at the repo or org level • Repo-specific Actions environments (development, uat, prod, etc.) • GitHub Dependabot - at the repo or org level Org-level secrets are automatically inherited by repositories, and you can choose whether they apply to all repos or only private ones. GitHub uses the following precedence: → Use environment secret → if missing, fallback to repo secret → if missing, fallback to org secret Everything is now at feature parity between GitHub(.)com and GitHub Enterprise Server (GHES).

📜 CHANGELOG! New: Dynamic Secrets – Every user, app and service gets unique secrets on every request 🪪 – Automate the entire secret lifecycle 🌀 – Trace every secret 🩻 – Web, CLI, REST API, SDKs ☑️ – DX 🔥 – Low latency ⏱️: <2s / lease creation AWS IAM Demo: