A social-media report described a curious experience: the user kept using Astra, changed the working environment from Codex to Zed, and suddenly the whole coding loop felt much faster. Their usage also seemed to decrease far more slowly.
The confusing part is that Zed, GitHub, Astra, and Codex all sound like parts of the same thing. They are not.
Zed is not a replacement for GitHub, and it is not a replacement for Astra. It is a place where you open code, ask an agent to work, edit files, run terminals, and review changes. Even if the AI brain stays the same, changing the “body” and the workflow around that brain can change the experience substantially.
1. The 30-second answer
Separate the four roles and the picture becomes simple.
| Name | Rough role |
|---|---|
| Zed | The editor and workbench where code and agents operate |
| GitHub | Remote repository, history, branches, pull requests, and collaboration |
| GPT-6 Astra | The AI model that reasons and generates code or text |
| Codex | An agentic software-development surface and execution path |
A useful analogy is: GitHub is the warehouse and ledger, Zed is the workbench, Astra is the brain, and Codex is another production line.
Most importantly, Zed and Codex are not mutually exclusive. Zed officially supports its native Zed Agent, Codex as an ACP external agent, and Codex CLI inside terminal-based workflows.[1][2][3]
2. What is Zed IDE?
Zed is a code editor in the same broad category as VS Code and Cursor. It is commonly called Zed Editor.
Zed is written in Rust and uses a GPU-oriented rendering architecture. Zed 1.0 was announced in April 2026, with support across macOS, Linux, and Windows.[4]
Modern Zed is also deeply integrated with AI. The Zed Agent can search a project, read files, edit code, run terminal commands, and present changes for review.[2]
So it is less like a fancy notepad and more like a coding desk where the editor, Git, terminal, and an AI worker all sit together.
3. Separate Zed, GitHub, Astra, and Codex
A common mistake is to think Zed and GitHub occupy the same layer.
GitHub stores remote repositories, keeps history, and coordinates branches and pull requests. Zed is the local application where you can open that repository and work on it.
Astra is a different layer again. OpenAI introduced GPT-6 Astra in September 2026 as a model aimed at demanding work including software engineering, computer use, browsing, and research.[5]
Codex is easier to understand as a product and agentic execution path for software development, not merely the name of a model. OpenAI currently presents Chat, Work, and Codex as distinct working surfaces around ChatGPT.[6]
That means the model can stay the same while the path used to run the work changes.
4. What does “moving Astra from Codex to Zed” actually change?
It does not literally move the Astra model onto your laptop.
What changes is the machinery that supplies context, reads files, invokes tools, runs the terminal, shows diffs, and manages an agent thread. This machinery is often called an agent harness. Zed’s own documentation says an agent path is sometimes called a harness.[2]
Zed currently offers at least three relevant paths:
- Use OpenAI models through the native Zed Agent.
- Run Codex as an ACP external agent inside Zed.
- Run Codex CLI inside Zed’s terminal or Terminal Threads.
So the sentence “I moved from Codex to Zed” does not uniquely identify one technical setup.
The brain may be the same. The body and cockpit are what changed.
5. Why can the same AI feel faster?
The elapsed time of an agentic task is not just model inference.
Conceptually:
Total time
= model reasoning
+ context gathering
+ file search and reads
+ tool calls
+ terminal execution
+ retries
+ reconnect delays
+ diff and review overhead
The model can be identical while the other terms change. If one environment repeatedly suffers reconnects or retries and another avoids them, the second can feel dramatically faster even when the underlying model is not computing faster.
That does not mean Zed is always faster. Large repositories, broad context searches, external-agent processes, or different settings can add overhead of their own.
The important point is that perceived speed is a property of the whole system, not just the model name.
6. Does “my tokens are barely going down” mean unlimited usage?
No such conclusion follows from the official documentation.
In May 2026, Zed announced that users can sign in to Zed Agent with a ChatGPT account and use OpenAI models with the same subscription-backed usage they receive in Codex. This is separate from bringing an OpenAI API key and paying API usage by token.[1][7]
However, Zed also states that usage is determined by the user’s ChatGPT tier.[1]
A “barely decreasing” feeling could have several explanations:
- less context or fewer tool round trips per task;
- fewer retries;
- a usage display that does not map one-to-one to internal token processing;
- simply comparing tasks of different difficulty.
So Zed does not unlock token immortality.
7. Does moving to Zed make Codex unnecessary?
The question is too binary for the current architecture.
You can run Codex inside Zed.[2][3]
The native Zed Agent is a natural fit when you want tight integration with the editor, code search, file edits, terminal commands, and MCP. If you want Codex’s own agent behavior or configuration, you can use Codex through ACP or run Codex CLI in a Zed terminal.
Astra also has Codex-specific capabilities. OpenAI describes a new Codex context mechanism in which Astra can preserve notes across context windows and search earlier context instead of relying only on repeated compaction.[5]
So “use Zed” does not mean “Codex now has zero value.”
You can prefer Zed as the desk and still choose Codex as the worker sitting at that desk.
8. How does this map to “I already work through GitHub”?
If you already let AI modify a GitHub-centered project, the mental model is close.
The difference is that GitHub is normally the remote source of truth, while Zed is the local workbench.
A typical flow looks like this:
GitHub repository
↓ clone / pull
Open project in Zed
↓
Give instructions to an AI agent
↓
Search and edit files
↓
Run tests in terminal
↓
Review the diff
↓
commit / push
↓
GitHub history / PR / CI
If “AI works directly in GitHub” is your current mental picture, Zed is closer to bringing that same repository onto your computer, putting it on a workbench, and having the agent work beside you.
Same repo, different workspace.
9. What does the real workflow look like?
Suppose an existing service has a bug. Open the repository in Zed and ask an agent to identify the cause, implement a fix, run relevant tests, and explain the resulting diff.
With Zed Agent, that work can use Zed’s native project and terminal tools. If you want Codex behavior, open Codex as an external agent or run the CLI in a terminal.[2][3]
After the agent edits the code, review the diff and test results, commit with Git, and push to GitHub. In a team environment, the flow continues through pull requests and CI.
Zed does not remove GitHub from the picture. It connects local agentic work to GitHub’s history, review, and integration layer.
10. Which path fits which job?
Instead of asking which tool is universally “best,” ask which behavior you want to preserve.
| Goal | Natural path |
|---|---|
| Keep Zed’s editor, review UI, and native coding-agent workflow | Zed Agent |
| Keep Zed’s UI but use Codex itself as the agent | Codex via ACP |
| Preserve Codex CLI’s native configuration and interaction style | Codex CLI / Terminal Threads |
| Use broader OpenAI working surfaces or computer-oriented capabilities | Combine with ChatGPT / Work / Codex as needed |
| Store, share, review, and integrate code remotely | Keep using GitHub |
Choosing Zed and abandoning Codex are not the same decision.
11. Common misunderstandings
“Zed replaces GitHub.”
No. Zed is a workbench; GitHub is the remote repository, history, and collaboration layer.
“Astra itself becomes faster when I open it in Zed.”
Not necessarily. The overall harness, context building, connectivity, and tool loop change.
“Zed means unlimited tokens.”
The official material does not say that. Subscription-backed usage follows the relevant ChatGPT tier.[1]
“Zed and Codex compete, so I can use only one.”
No. Codex can run in Zed through ACP, and Codex CLI can run in Zed’s terminal workflows.[2][3]
“If the model is the same, changing environments cannot matter.”
It can. Context construction, tool calls, retries, connection stability, and review flow can all change total time.
12. Summary
Zed IDE is neither the AI model nor a GitHub replacement. It is a fast environment for opening code, running agents, editing files, executing commands, and reviewing changes.
When someone says they “moved Astra from Codex to Zed,” the important change is often not the brain but the route around the brain.
That can make the same Astra feel much faster. But “faster” does not prove the model itself changed speed, and “usage barely moved” does not prove unlimited access.
The most interesting part is that this is not simply Zed versus Codex.
You can seat Codex at the Zed workbench.
Bring the same repository from the GitHub warehouse, work on it in Zed with Astra, choose Codex when its agent path is useful, then send the result back to GitHub.
Once the buzzwords are separated, the architecture is surprisingly ordinary: warehouse, workbench, brain, production line.
- [4] Zed, “Zed 1.0” — https://zed.dev/blog/zed-1-0
- [1] Zed, “Use Your ChatGPT Subscription in Zed” — https://zed.dev/blog/chatgpt-subscription-in-zed
- [2] Zed Docs, “Agents” — https://zed.dev/docs/ai/agents
- [3] Zed Docs, “External Agents” — https://zed.dev/docs/ai/external-agents
- [7] Zed Docs, “Use an Existing Subscription” — https://zed.dev/docs/ai/use-an-existing-subscription
- [5] OpenAI, “GPT-6 Astra: A new generation of intelligence” — https://openai.com/index/gpt-6-astra/
- [6] OpenAI Help Center, “ChatGPT Work and Codex” — https://help.openai.com/en/articles/20001275/
Sources
- https://zed.dev/blog/chatgpt-subscription-in-zed zed.dev
- https://zed.dev/docs/ai/agents zed.dev
- https://zed.dev/docs/ai/external-agents zed.dev
- https://zed.dev/blog/zed-1-0 zed.dev
- https://openai.com/index/gpt-6-astra/ openai.com
- https://help.openai.com/en/articles/20001275/ help.openai.com
- https://zed.dev/docs/ai/use-an-existing-subscription zed.dev
