Zed v1.8 is out, and the headline feature is deceptively small: a single new setting called agent.terminal_init_command that runs a shell command every time the agent opens a fresh terminal thread. It sounds minor, but it unlocks a whole class of workflows that were awkward before -- environment setup, virtual-env activation, toolchain switching -- all handled automatically before the agent types its first command.
The agent terminal gets a bootstrap hook
When Zed's AI agent runs tasks in a terminal, it previously started from a bare shell. That meant any project-specific environment setup (activating a Python venv, loading a .env file, switching Node versions) had to happen manually or be baked into every prompt. With agent.terminal_init_command, you configure it once in your settings and every new agent terminal thread inherits the right environment automatically.
To use it, add this to your Zed settings:
{
"agent": {
"terminal_init_command": "source .venv/bin/activate && export ENV=dev"
}
}
Don't miss what's next in AI
Join 300,000+ engineers and researchers who get the signal, not the noise.
- Full access to in-depth AI research breakdowns
- Be the first to know what's trending before it hits mainstream
- Daily curated papers, repos, and industry moves