Product feedback

Help shape CodeLedger

Improvements are tracked publicly in GitHub Discussions — so you can see what others have requested, upvote ideas that matter, and follow the status of your suggestion.

💡

Feature idea

Something you wish CodeLedger did — a new command, a better signal, a workflow improvement.

Open an idea
🐛

Bug report

A command that fails, an unexpected output, or a result that doesn't match what the docs describe.

Report a bug
✏️

Docs improvement

Missing example, confusing explanation, outdated flag description, or a guide you wish existed.

Suggest a docs fix
🗺️

Roadmap discussion

Weigh in on what gets built next. See what others have requested and upvote what matters most.

See the roadmap thread

How we handle feedback

  1. 1
    You submit — Post to GitHub Discussions or Issues using one of the links above. The pre-filled templates make it fast.
  2. 2
    We triage — Every submission gets a response within 5 business days. We label, clarify if needed, and link related requests.
  3. 3
    Community upvotes — Other users can +1 and comment on open ideas. High-signal ideas move up the roadmap.
  4. 4
    We ship or explain — When we build it, we close the thread with a link to the release. When we decline, we explain why.

Prefer email?

For security issues or enterprise feedback that shouldn't be public, write directly to us.

product@codeledger.devsecurity@codeledger.dev

Looking for documentation? Browse the docs →