Community support · GitHub Issues · no signup wall

Report an Issue

Bugs, feature requests, packaging problems, doc typos — all welcome on the OpenBox GitHub issue tracker. There's no separate forum, no support tier, no "premium users first". Everything happens in one place.

→ Open a new issue Browse existing issues

Before You File

A little prep makes your issue much more likely to get fixed quickly.

🔍

Search first

Search both open and closed issues for keywords related to your problem. Many common questions have already been answered.

🧪

Reproduce on the latest build

Issues filed against old versions are hard to fix. Download the latest release and confirm the bug still reproduces. If it doesn't, you've already solved your problem.

📋

Pick the right template

The issue picker offers templates for bug reports, feature requests, and packaging issues. Pick the closest match — the template will prompt you for the info we need.

📸

Include a screenshot

If it's a UI bug, drag a screenshot into the issue body. If it's a CLI bug, paste the exact command and the full error output (redact any private paths first).

💻

Share your environment

OS version, OpenBox version (visible in About tab or samai-openbox --version), and for Linux the distro + desktop environment. One line is enough.

🎯

One issue = one problem

If you found three bugs, file three issues. It keeps the discussion focused and lets each fix ship independently without waiting on the others.

Issue Templates

What the GitHub issue picker will ask you for. Fill in as much as you can.

Bug

Bug report

Use this when OpenBox crashes, misbehaves, or produces wrong output. The template asks for:

  • OpenBox version and OS (auto-filled from the picker)
  • Steps to reproduce — numbered list of exact clicks / commands
  • Expected behavior vs. actual behavior
  • Screenshot or error log (drag-and-drop into the issue)
  • The archive file itself (if you can share it; otherwise the file listing)
Feature

Feature request

Use this when OpenBox works but you wish it did something it doesn't. The template asks for:

  • The problem you're trying to solve (not the solution you imagined)
  • Current workaround (if any) and why it's painful
  • Proposed behavior — be specific, but don't over-prescribe the implementation
  • Alternatives you've considered
Packaging

Packaging / install issue

Use this when the download won't install, the file associations don't register, or the binary won't launch. Include:

  • OS version and CPU architecture (e.g. Windows 11 23H2 x64, macOS 14.5 arm64, Ubuntu 24.04 x64)
  • Which file you downloaded (exact filename from the download page)
  • Step where it failed (double-click? wizard? post-install launch?)
  • Screenshot of any error dialog, or paste of any terminal output

Security Reports

Found a vulnerability? Please don't open a public issue. Report privately.

OpenBox is a desktop archiver, so the main security surface is archive extraction. We already block path-traversal entries (../../etc/passwd style attacks) at the engine level, and we don't auto-execute anything inside archives.

If you find a way to:

Please report it privately via GitHub's advisory feature:

→ Open a private security advisory

We acknowledge reports within 48 hours and aim to ship a fix within 30 days for high-severity issues.

Other Ways to Reach Us

Issues are best for actionable bugs and features. For everything else, here are the alternatives.

💬

Discussions

Questions like "how do I …?" or "what's the best format for …?" belong in GitHub Discussions, not the issue tracker. Issues are for actionable work items.

🔀

Pull requests

Code contributions welcome — fork the repo, push to a branch, open a PR against main. Small bugfixes can go straight in; larger changes should have an issue first to discuss the approach.

📣

SamAI Group

OpenBox is one of the SamAI Group's public-welfare open-source projects. Cross-project discussions happen on the SamAI community channels linked from samai.cc.