Good First Issues

It would be great to allow users to **use the keyboard** instead of only clicking/tapping. * Map keys for actions in the reaction test (e.g., spacebar or enter) * Keep current click/tap controls as alternative * Ensure responsiveness and accuracy with keyboard input This addition would make the test more accessible and improve user experience.

Created: 2/2/2026

## Summary Add a new LLM provider plugin using the existing plugin architecture (proxy + client entrypoints) and schema-first validation. ## Scope - New package under `packages/plugin-llm-<name>/` - Minimal supported action(s): `chat.completions` (or equivalent) - Add docs: how to enable plugin via `proxy.plugins.ts` - Add a basic request validation test ## Acceptance criteria - Plugin can be enabled/disabled from `proxy.plugins.ts` - Builds successfully - Documentation added under docs/ - Example usage added (1 short snippet)

Created: 2/2/2026

Following the official release, Aether Command is to be added to the software catalog. This is a first-party terminal emulator and needs to be listed alongside our other core applications.

Created: 2/2/2026

## Summary Improve docs for plugin enablement and the pairing flow so first-time users understand the concept in <2 minutes. ## Suggested changes - Add a short diagram of: App -> Gateway -> Provider - Add a small section: "Enable/Disable plugins" referencing `proxy.plugins.ts` - Add 2–3 screenshots or asciinema-style output (optional) ## Acceptance criteria - Docs reduce setup questions (esp. around plugins + pairing) - No deep refactors; docs-only PR is OK

Created: 2/2/2026

Created: 2/2/2026

## Summary Make CI run the core checks on every PR: install -> lint -> build -> tests. ## Tasks - Confirm existing workflows under `.github/workflows/` - Add/adjust PR workflow: - `npm ci` - `npm run lint` (or equivalent) - `npm run build` - `npm run test` (if exists; otherwise stub and document) ## Acceptance criteria - PRs show a green check when basic quality gates pass - Workflow is under ~5–10 minutes on GitHub-hosted runners

Created: 2/2/2026

fdasfdasfdafdsafdsafdsafdas

Created: 2/2/2026

## 📖 Add New Grammar Point **Category:** Community Contribution - Grammar **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this grammar explanation to our learner-friendly grammar list! ### The Grammar Point > "〜てはいけません" means "must not" and is used for prohibitions. ### 📝 Instructions 1. Open [`data/community-content/japanese-grammar.json`](../blob/main/data/community-content/japanese-grammar.json) 2. Add this grammar string to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item ```json ""〜てはいけません" means "must not" and is used for prohibitions." ``` 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add new grammar point` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/2/2026

## Summary Ensure the gateway works with the official OpenAI SDK configuration pattern (baseURL + custom fetch). Add a test or example that verifies request shape and response passthrough. ## What to add One of: 1) Integration test using a mocked upstream server (preferred, no real keys) 2) Example script under `scripts/` that hits a local gateway and validates behavior ## Acceptance criteria - A contributor can run the test locally without real provider keys (mock upstream) - The example matches the README pattern (OpenAI SDK with gateway baseURL + gateway fetch) - Document any caveats (streaming, headers) if needed

Created: 2/2/2026

## Summary Fork the project from main branch and verify the README Quick Start works (admin guide). Fix any broken steps, missing env vars, or outdated commands. ## What to verify - build works - `apps/proxy` env setup (`.env.example` -> `.env`) - Database migrations - `npm run dev` - Demo target app still connects / sample request still works ## Deliverables - PR with doc fixes (README and/or docs/*) - Add a small "Common issues" section (1–5 bullets max) ## Acceptance criteria - A newcomer can follow the docs without guesswork - Any required env vars are documented - Commands match repo scripts and current structure

Created: 2/2/2026

## Current behavior Program starts in interactive mode, requiring user input for configuration. --- ## Desired behavior Support CLI arguments to allow headless/scripted usage. **Good first issue** — requires only basic `argparse` knowledge, no audio/libinput internals. --- ## Need to introduce - Arguments for cli use: --version (-V), --keyboard (-k), --mouse (-m), --sensitivity (-s), --base-loudness (-bl), and behavior|acceptable values according to their names. --- ### Example usage ```bash quarks -bl 10 -k -m -s 20 # Base sound loudness: 10/100, sensitivity to user actions: 20/100, keyboard affects sound, mouse affects sound ``` --- ## Notes - Interactive mode should remain the default when no arguments provided - Invalid values should cause sys.exit(1) like in interactive mode

Created: 2/2/2026

## Summary Add GitHub issue templates to standardize incoming issues and make triage easier. ## Tasks Create: - `.github/ISSUE_TEMPLATE/bug_report.md` - `.github/ISSUE_TEMPLATE/feature_request.md` - `.github/ISSUE_TEMPLATE/docs.md` - Optional: `.github/ISSUE_TEMPLATE/config.yml` to disable blank issues ## Acceptance criteria - Templates appear in "New issue" - Each template asks for minimal but useful info: - Repro steps (bug) - Expected vs actual - Environment (Node version, deployment target) - Logs/screenshots where relevant

Created: 2/2/2026

## Summary The README links to `CONTRIBUTING.md`, but the file is currently missing (404). Let's add a clear, minimal contributing guide so newcomers can run the gateway locally, know where to make changes, and open PRs confidently. ## Goals - Add `CONTRIBUTING.md` at repo root - Keep it short, practical, and aligned with the current repo structure (`apps/proxy`, `packages/*`, `examples/demo-target-app`) and plugin architecture (`proxy.plugins.ts`) ## Suggested content - Dev prerequisites (Node version, npm) - Local setup steps (install, env setup, migrations, run) - How to add/enable plugins (point to `proxy.plugins.ts`) - How to run formatting/lint/tests (whatever exists today; if missing, document what's available) - PR checklist ## Acceptance criteria - `CONTRIBUTING.md` exists at the repo root - README "Contributing" link resolves correctly - Steps are copy/paste friendly and verified on a clean clone ## Helpful pointers - README has the project structure and plugin enabling snippet.

Created: 2/2/2026

Hi! New contributor here. Problem I want to help quickly, but I’m not sure: which areas are most in need (docs, examples, integrations, tests, etc.) what a “good first PR” looks like how you prefer issues to be formatted/labeled Suggested improvement Add a short section to CONTRIBUTING.md that includes: recommended first contributions (docs fixes, examples, labeling issues, etc.) how to run any basic checks locally (if applicable) suggested labels to use (bug/docs/enhancement/good first issue) Why it matters Lowers contribution barrier and increases PR volume/quality.

Created: 2/2/2026

## Description Create a complete example in `examples/fastapi-strawberry-redis/` demonstrating CacheQL integration with Strawberry GraphQL and FastAPI. ## Requirements ### Directory Structure ``` examples/fastapi-strawberry-redis/ ├── app/ │ ├── __init__.py │ ├── main.py # FastAPI app with Strawberry │ ├── schema.py # Strawberry schema with cache hints │ ├── resolvers.py # Resolvers with dynamic hints │ └── database.py # SQLite for demo ├── docker-compose.yml ├── Dockerfile ├── requirements.txt └── README.md ``` ### Features to Demonstrate - [ ] Schema with `@strawberry.field` and cache hints - [ ] Resolvers using dynamic cache hints - [ ] Mutations with cache invalidation - [ ] Docker Compose setup with Redis - [ ] README with clear setup instructions ## Context Currently, only an Ariadne example exists. Strawberry is a popular GraphQL library for Python, and users need a reference implementation. ## Acceptance Criteria 1. Example runs with `docker-compose up` 2. Cache control headers are correctly set 3. Redis caching works properly 4. README explains all features

Created: 2/2/2026

Created: 2/2/2026

## 🎌 Add Japanese Proverb (ことわざ) **Category:** Community Contribution - Proverb **Difficulty:** Easy (good first issue!) **Estimated Time:** <1 min --- ### 🎯 Your Task Add this traditional Japanese proverb to help learners understand Japanese wisdom! ### The Proverb | Japanese | Reading | English | |----------|---------|---------| | **泣きっ面に蜂** | Nakittsura ni hachi | A bee on a crying face | > 💡 **Meaning:** Misfortune never comes alone ### 📝 Instructions 1. Open [`data/community-content/japanese-proverbs.json`](../blob/main/data/community-content/japanese-proverbs.json) 2. Add this proverb object to the end of the array (before the closing `]`) 3. Make sure to add a comma after the previous last item ```json { "japanese": "泣きっ面に蜂", "romaji": "Nakittsura ni hachi", "english": "A bee on a crying face", "meaning": "Misfortune never comes alone" } ``` 4. Save the file and commit the changes 5. Submit a Pull Request with title: `content: add new japanese proverb` 6. Link this issue using `Closes #<issue_number>` 7. Star our repo ⭐, drink some delicious bubble tea 🍹 and wait for review! --- **Questions?** Comment below and we'll help! 🙌

Created: 2/2/2026

## Description JSR requires explicit type annotations for all public API symbols to enable fast type checking. Currently the `no-slow-types` lint rule is disabled because many exported symbols are missing explicit types. ## Examples of missing types ```typescript // src/core/registry.ts:230 export const globalRegistry = new CommandRegistry(); // Should be: export const globalRegistry: CommandRegistry = new CommandRegistry(); // src/restframework/viewsets/model_viewset.ts:428 export const ListModelMixin = { ... }; // Should be: export const ListModelMixin: { list: ... } = { ... }; ``` ## Files to fix - `src/core/registry.ts` - `src/restframework/viewsets/model_viewset.ts` - And likely others ## Why this matters - Enables faster type checking for consumers - Required for proper JSR publishing - Better IDE support and documentation ## References - https://jsr.io/go/slow-type-missing-explicit-type - https://docs.deno.com/lint/rules/no-slow-types

Created: 2/2/2026

## Problem Statement As someone from a design/product background, it’s not obvious how non-core engineers can meaningfully contribute to Hive. The repository feels primarily oriented toward code contributions, but there are many ways others could help (docs, diagrams, examples, UX improvements). ## Proposed Solution Add a short section explaining how contributors from different backgrounds can help improve Hive. ## Alternatives Considered Contributors figuring it out themselves, but explicit guidance can attract a wider contributor base. ## Additional Context Open-source projects often benefit from documentation and UX contributions, not just code. ## Implementation Ideas A **“How you can contribute”** section in the `README` or `CONTRIBUTING.md`.

Created: 2/2/2026 • 1 comments

Created: 2/2/2026