CLI tool
pop-os/cosmic-term avatar
pop-os/cosmic-term

cosmic-term's manifest names two git dependencies with no revision

COSMIC terminal emulator. cosmic-term provides bidirectional rendering and ligatures with a custom renderer based on cosmic-text.

603 stars210 forksRustGPL-3.0

At a glance

What is it?
A COSMIC terminal emulator built on another project's terminal parser, with a GPU renderer that has a named software fallback. Its build pulls two dependencies straight from git branches, and the version 1.9.0 exists only in the manifest because no release has been published.
Who is it for?
Use it if you want a terminal inside the COSMIC desktop and you accept that a build reaches two git branches rather than pinned crates. Two things to check before you commit to it.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 7 days ago.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • pop-os/cosmic-term603 ★ · +19
Star history
Repository2026-07-312026-11-15
pop-os/cosmic-term584603

19 Stars in the last 107 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The GPU path has a named software fallback

Rendering is the feature the whole project is described by. The terminal is built on the terminal parser provided by another project, and what this project adds is bidirectional rendering and ligatures through a custom renderer based on a text shaping library from the same organisation.

The graphics feature is on by default. When it is enabled, rendering goes through a GPU path using two libraries, one for shaping and one for the graphics abstraction. The interesting sentence is the failure case: if that feature is not enabled, or if it fails to initialise, rendering falls back to a software path using a software framebuffer and a software rasteriser.

That fallback is named rather than implied, which is unusual and useful. A terminal that cannot initialise its GPU path has a defined alternative rather than a blank window, and the condition covers both a build that never enabled the feature and a build where the hardware or driver refused it.

What the feature does is delegate: it turns on the graphics feature in the desktop toolkit and in the file-picker dependency alongside its own. So the graphics capability of the terminal is assembled from three crates rather than implemented once.

The page's own description of scope is short. What is documented on it is the parser this project reuses, the two rendering additions, the GPU feature and its fallback, and how to import a colour scheme.

Two dependencies come from git with no revision named

The manifest has two dependencies that are not crates.io packages. Both point at repositories in the same organisation as this project, the desktop toolkit and the file-picker library, and both are declared with default features switched off.

As written, neither declaration names a revision or a tag. That means a build follows the default branch of each repository rather than a fixed point, so two checkouts of the same commit of this project can produce different binaries. It is a normal arrangement for a project that develops alongside its own toolkit, and it is also the reason a release tarball built elsewhere may not match what you build.

The feature list passed to the toolkit is short and specific: about dialog, autosize, multi-window, an async runtime, the windowing backend, and a message-passing surface. Immediately above it sits a comment worth reading, a to-do noting that the accessibility feature crashes the file chooser dialog. So accessibility is deliberately left out of the feature set for now, with the reason recorded in the file rather than in an issue.

Two features simply pass through to the toolkit and the file picker together: the graphics feature and the Wayland feature. Both turn on the same capability in both dependencies, which is the mechanism that keeps the three crates consistent with each other.

Command line arguments are tokenised, not parsed by a framework

The dependency list has one entry for command line handling and it is a lexer, not a parser generator. There is no derive-style argument framework in the list, which means the flags this terminal accepts are assembled by hand from tokens.

For a terminal emulator that is a reasonable trade. The surface is small, and it avoids pulling a parser and its derive machinery into a binary that mostly needs to accept an executable path, working directory and a handful of switches.

The async story is equally narrow. The runtime dependency enables exactly one feature, the synchronisation primitive, rather than the full runtime. That matches an application that owns its own event loop through the windowing backend and needs a lock or a channel, not a task runtime.

There is also a Unix-only dependency on a process forking library, declared under a target-specific table rather than generally, which is the sort of detail that matters on the platforms the toolkit actually supports.

Configuration is handled separately, in a plain object notation format rather than JSON or TOML, with a matching serialisation library and an ordered map type in the dependency list. Shelling out is handled by a shell-lexing library, which is what you want in a terminal that launches commands.

Passwords come from the desktop keyring, and that feature is on by default

The password manager feature is part of the default feature set, and it pulls in three crates that exist only for that purpose: a client for the desktop secret service, a string type for holding secrets safely, and an error library.

Reading the feature definition makes the intent plain. Enabling it is what pulls those three in, so a build with the feature disabled has no secret-service client at all. That is the cleaner arrangement for a distribution that does not want a keyring dependency, and it is a decision rather than an omission.

Localisation is handled with a Fluent-based embedding crate configured for two backends: the system locale, and a desktop requester that asks the running session for its language preference. That second backend is why a localisation library appears in the list at all. Locale data comes from a Unicode component library with its data compiled in, and the translation files themselves are embedded at build time rather than read from disk, which is what the embedding crate in the list does.

An internationalisation configuration file and a directory of translations sit at the root. The terminal is therefore localisable without a runtime lookup, at the cost of shipping every locale inside the binary.

The build generates its own desktop file, and 1.9.0 exists only in the manifest

The version is 1.9.0 and there are no published releases, so that number exists in exactly one place, the manifest. The metadata calls the licence GPL-3.0 while the manifest is more precise, GPL-3.0-only, which excludes later versions of the licence from the grant. The edition is 2024 and the minimum Rust version is 1.93, which is recent enough to rule out older toolchains.

The build script generates the desktop integration. A build dependency produces the desktop entry and the metainfo document, and the task runner wires them into place: an application identifier of the form used for the desktop system, a desktop file named from that identifier, a metainfo file named from it, and an icon directory copied under a share prefix.

The task file is where the project tells you how it builds. Compilation is Cargo with a debug and a release recipe, and a vendored recipe that builds with the frozen and offline flags after extracting vendored sources. The lint recipe runs clippy across all features with the pedantic group enabled at warning level, and a second recipe emits the same checks as JSON for tooling. There is a separate recipe to remove vendored dependencies, and one that runs the formatter before launching.

The run recipe is worth noting for anyone debugging: it sets the log filter to this crate at debug level and turns on full backtraces, then runs the release build. Development convenience is built into the standard command rather than left to a separate script.

The tree also carries a shell script for ANSI colours at the root, which the page does not mention, plus a Nix flake, a Debian packaging directory and a direnv file.

Editorial conclusion

Use it if you want a terminal inside the COSMIC desktop and you accept that a build reaches two git branches rather than pinned crates. Two things to check before you commit to it. Both git dependencies are declared without a revision or tag in the manifest as written, so a build is not reproducible until you pin them yourself. And the graphics feature list has no X11 entry even though Wayland is on by default, so confirm your session type is covered before installing.

Frequently asked questions

What is cosmic-term?

A terminal emulator for the COSMIC desktop, built on the terminal parser provided by the alacritty project. It adds bidirectional rendering and ligatures through a custom renderer based on cosmic-text, and it is authored by Jeremy Soller under GPL-3.0-only.

Does cosmic-term need a GPU?

No. The wgpu feature is enabled by default and uses glyphon and wgpu for GPU rendering, but if it is not enabled or fails to initialise, rendering falls back to softbuffer and tiny-skia. Both the graphics feature and the Wayland feature are turned on in the desktop toolkit and the file picker together.

How do I add a color scheme to cosmic-term?

Custom schemes are imported from the View -> Color schemes... menu item, and templates for new ones live in the color-schemes directory in the repository.

How does cosmic-term store passwords?

Through the desktop secret service, using a secret string type and an error library. Those three crates are pulled in only by the password_manager feature, which is part of the default feature set, so a build with it disabled carries no keyring client.

Which version of cosmic-term is current?

1.9.0, as declared in the manifest, with no GitHub releases published, so there is no tag to install from. The crate targets Rust edition 2024 and requires Rust 1.93 or newer, and the last push on the master branch is dated 2026-09-30.

What does cosmic-term depend on that is not a published crate?

Two: libcosmic and cosmic-files, both taken from git repositories in the same organisation with default features disabled. As declared in the manifest, neither names a revision or a tag, so a build follows each repository's default branch.

Official sources

  1. Official README
  2. Project repository
  3. README
  4. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pop-os-cosmic-term.svg)](https://hysenlabs.com/projects/pop-os-cosmic-term)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pop-os-cosmic-term.svg)](https://hysenlabs.com/projects/pop-os-cosmic-term)

Was this useful?