Add flue to Server Applications

[karngyan]

Required links

Provide the links below. Our CI will automatically validate them.

• Forge link (github.com, gitlab.com, etc): https://github.com/karnstack/flue
• pkg.go.dev: https://pkg.go.dev/github.com/karnstack/flue
• goreportcard.com: https://goreportcard.com/report/github.com/karnstack/flue
• Coverage service link (codecov, coveralls, etc.)

Two of these are not checked, and I want to be upfront about why.

Go Report Card. The link above resolves, but it no longer produces a
grade. goreportcard.com has been sunset. Every report URL now serves the
same farewell page, including the ones for projects already on this list.
So I cannot show a grade for flue, and I did not want to tick a box that
says I can. What the repo does have is make lint, which runs go vet
over three build tag variants plus shellcheck on the install script, and
CI runs it on every push and every pull request.

Coverage service. flue does not publish to Codecov or Coveralls yet.
The Go, web and relay test suites all run in CI, but no coverage report is
uploaded anywhere I can link to. I would rather leave this blank than
point at something that is not there.

Pre-submission checklist

• I have read the Contribution Guidelines
• I have read the Quality Standards

Repository requirements

These are validated automatically by CI:

• The repo has a go.mod file and at least one SemVer release (vX.Y.Z). Latest is v0.9.1.
• The repo has an open source license. MIT.
• The repo documentation has a pkg.go.dev link.
• The repo documentation has a goreportcard link (grade A- or better).
• The repo documentation has a coverage service link.

The README carries CI, release and license badges, but not the three
above. A pkg.go.dev badge is easy to add if that helps. The other two
cannot be added honestly today, for the reasons given at the top.

These are recommended and reported as warnings:

• The repo has a continuous integration process (GitHub Actions, etc.).
• CI runs tests that must pass before merging.

On the last one: CI does run the full test suite on every pull request and
every push to main, and all work lands through pull requests. But the
branch ruleset does not list the CI job as a required status check, so a
red build is not a hard block today. That is worth tightening and it is on
our list.

Pull Request content

• This PR adds/removes/changes only one package.
• The package has been added in alphabetical order. It sits between flipt and go-feature-flag in Server Applications.
• The link text is the exact project name.
• The description is clear, concise, non-promotional, and ends with a period.
• The link in README.md matches the forge link above.

Category quality

• The packages around my addition still meet the Quality Standards.

I checked four entries above and four below. Easegress, Fider, Flagr,
flipt, go-feature-flag, go-proxy-cache, gondola and goshs are all active,
none are archived, and all have commits within the last month.

About flue

flue is a small Go daemon that holds your terminal sessions and serves
them to a browser tab. Closing the tab does not kill the session, it only
detaches it, so a build or an SSH session keeps running and reattaching
replays what you missed. It is the same space as gotty and ttyd, with
session persistence and a session list across machines added on top.

Site: https://flue.sh

One thing that may block this

The repository maturity rule asks for at least 5 months of history since
the first commit. flue's first commit is from 2026-07-28, so it is about
three weeks old. It does not meet that rule. Everything else is in place:
MIT license, go.mod, tagged SemVer releases up to v0.9.1, English
documentation, a working CI, and daily commits.

I am opening this now rather than sitting on it, but I fully understand if
you would rather hold or close it until flue clears the 5 month mark. Just
say so and I will resubmit then.

[qodo-code-review]

ⓘ Your Qodo trial ends soon. Ask your workspace admin to set up billing to keep reviews running after the trial. Manage billing

[qodo-code-review]

PR Summary by Qodo

Add flue to Server Applications directory

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Adds flue to the Server Applications directory.
• Describes its browser-accessible, persistent terminal session functionality.

High-Level Assessment

The existing approach is optimal: flue is added directly to the established alphabetical Server Applications list with a concise capability-focused description. No architectural alternative is warranted for a single catalog entry.

Files changed (1) +1 / -0

Documentation (1) +1 / -0

README.mdList flue under Server Applications +1/-0

List flue under Server Applications

• Adds flue to the Server Applications section, linking its repository and describing its persistent browser-based terminal sessions.

README.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

Qodo Fixer

No findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR.

[github-actions]

Automated Quality Checks

Required checks

✅ Repo: accessible, has go.mod and SemVer release
✅ pkg.go.dev: OK
✅ Go Report Card: OK (grade unknown)

Additional checks

✅ License: MIT
⚠️ Maturity: repo appears to have less than 5 months of history

How to fix: Your repository needs at least 5 months of history since the first commit.
Please resubmit after the repository meets this requirement.
✅ CI/CD: GitHub Actions workflows detected
✅ README: present
⚠️ Coverage: missing from PR body
How to fix: Add a coverage service link to your PR description:

Coverage: https://app.codecov.io/gh/your-org/your-project

Popular options: [Codecov](https://codecov.io), [Coveralls](https://coveralls.io). Integrate one with your CI to track coverage automatically.


_These checks are automated and do not replace maintainer review. See [CONTRIBUTING.md](https://github.com/avelino/awesome-go/blob/main/CONTRIBUTING.md) for full guidelines._

---

## PR Diff Validation

### Content checks

✅ **Files changed**: only README.md
✅ **Single item**: one package added
✅ **Link consistency**: README link matches forge link in PR body
✅ **Link text**: matches repository name
✅ **Description**: ends with punctuation
✅ **Description tone**: no promotional language detected
✅ **Category size**: Server Applications has 37 items


_Automated diff validation — does not replace maintainer review._
<!-- Sticky Pull Request Commentpr-quality-check -->