Skip to content

[Feature]: Explore libghostty as an optional backend for dpcode’s integrated terminal #63

@HarrjyotSingh

Description

@HarrjyotSingh

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

Not Sure

Problem or use case

The integrated terminal currently feels a bit limited for more advanced workflows, especially when using tools like Neovim or Yazi.

Things like inline image rendering, file previews, and support for modern terminal features (e.g. Kitty graphics) don’t work well, which often forces me to switch to an external terminal. That breaks the overall workflow and makes the integration less useful.

Proposed solution

It might be worth exploring libghostty as an optional or experimental terminal backend. It could enable better support for modern terminal features, including inline images and improved compatibility with TUI tools.
Even a simple configurable option (e.g. switching terminal backend or enabling richer rendering) would already be helpful.

Why this matters

This would make dpcode much more usable for terminal-heavy workflows and Neovim users, and reduce the need to rely on an external terminal.

Smallest useful scope

Not suggesting replacing the current terminal, just exploring this as an optional or experimental direction. Even a small prototype would be valuable to see what’s possible.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

  • I would be open to helping implement this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementRequested improvement or new capability.needs-triageIssue needs maintainer review and initial categorization.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions