Feature Roadmap

[castastrophe]

This discussion tracks planned features for envoy. React with 👍 on the issues that matter most to you — that feedback shapes what gets prioritized.

Planned features

🔁 Variable resolution (#10)

When your ~/.env uses variable references like DATABASE_URL=${DB_HOST}:${DB_PORT}/dev, envoy should resolve those references before writing to the project .env. Today it copies the template string literally.

Open questions: Should this be opt-in (--resolve-vars) or always-on? How should circular references be handled?

---

🏷️ Key aliasing (#11)

Support a mapping between project key names and what you call them in your personal ~/.env. If a project wants API_KEY but you store it as MY_SERVICE_API_KEY, you should be able to declare that alias rather than rename your global key.

Three syntaxes are under consideration — inline comments in .env.example, a separate .env.map file, or an envoy field in package.json. Discussion on the issue welcome.

---

🔒 Pre-commit secret validation (#14)

A --check flag that runs envoy in read-only mode, cross-referencing staged files against known secret values in ~/.env. Designed to slot into a pre-commit hook or CI step — exits non-zero if a real secret is detected in a tracked file, zero if clean.

Open questions: Should it scan only staged files or all tracked files? How should intentional example values be distinguished from real secrets? Should there be an allowlist mechanism?

---

How to contribute

• Vote: React 👍 to the issue for features you want
• Comment: Leave feedback directly on the linked issue
• Propose: Open a new issue with the enhancement label to suggest something not listed here

This roadmap is intentionally lightweight — priorities will shift based on what people actually need.