EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Hacker News·5h ago·5 min read
Codex CLI installs a persistent, self-updating background daemon by default
TL;DR
The Codex CLI now installs a persistent, self-updating background daemon by default, which has raised concerns among users about unexpected behavior. Many users prefer the daemon to be an opt-in feature rather than a default setting.
✦ Why It Matters
Consider disabling the auto-start feature of the Codex CLI daemon to avoid unexpected background processes.
Key Takeaways
- Disable daemon auto-start to prevent unexpected behavior.
- Monitor background processes to manage system resources effectively.
- Provide feedback to developers about default settings.
- Stay updated on changes in CLI behavior with new versions.
How It Works
The Codex CLI launches a background daemon that runs independently of the user's terminal session. This daemon is designed to update itself and maintain a separate state from the CLI version installed via the package manager.
It copies the necessary files to a managed release directory, allowing for seamless updates without user intervention.
⚠ The Catch
The auto-starting daemon does not terminate when the last client disconnects, leading to lingering processes that can consume system resources.