15 Open Issues Need Help Last updated: Feb 6, 2026

Open Issues Need Help

View All on GitHub

AI Summary: This issue proposes to improve the user experience by dynamically setting the filename for SVG downloads. Instead of a hardcoded name, the download filename should use the user-provided canvas name, making it easier for users to identify and organize their exported diagrams.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue addresses a potential unbounded storage growth in Redis by adding a Time-To-Live (TTL) to classification results. Currently, these results are stored indefinitely, which can lead to excessive memory usage over time, especially when associated ideas are deleted. The proposed solution involves setting a 30-day TTL on these Redis entries.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue identifies two identical enums, `IdeaClassification` and `ClassificationType`, in different files. The recommended fix is to consolidate these into a single shared enum in a new module and import it where needed, potentially with backward-compatible aliases. This aims to improve code quality and adhere to the DRY principle.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue requests the addition of missing integration and unit tests for several components of the P08 implementation, including RedisGraphStore, IdeaHandler, and Classification Worker. The goal is to improve test coverage before production deployment by addressing specific gaps in functionality like CRUD operations, edge cases, and error handling.

Complexity: 3/5
enhancement good first issue

AI Summary: This issue requests the addition of structured logging to the MCP Redis and Elasticsearch servers. Currently, these servers lack logging capabilities, hindering debugging efforts. The proposed solution involves importing the `logging` module and configuring a basic logger.

Complexity: 2/5
enhancement good first issue

AI Summary: This issue identifies duplicate `formatTime` utility functions across several chart components in the `hitl-ui` project. The proposed solution is to extract this function into a shared utility file (`formatters.ts`) and import it where needed, reducing code redundancy and improving maintainability.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue proposes minor code quality improvements for the P02-F06 coordination sender identity feature. The suggested changes include adding an explicit return code check for a subprocess call, removing an unused test fixture, and optionally adding `shell=False` to a subprocess call for clarity.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue proposes adding a unit test for the `run_stdio()` method in the `KnowledgeStoreMCPServer` class. The test should verify the method's existence and its ability to be called with mocked standard input, addressing a gap in current test coverage.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue requests adding test coverage for the `updateMermaidTheme` function in the mermaid config module. The function currently delegates to `initMermaid` and a new test case is proposed to document its behavior, ensure the export contract, and prevent regressions.

Complexity: 1/5
enhancement good first issue

AI Summary: This issue reports 22 pre-existing frontend test failures in the Sidebar component. The failures seem to stem from tests looking for removed 'Operations' text, indicating the tests need to be updated to reflect the current Sidebar implementation.

Complexity: 2/5
bug help wanted

AI Summary: The current tests for the feedback API only verify the existence of hooks and successful type compilation. They do not cover crucial aspects like actual mutation behavior, error handling, or cache invalidation logic, indicating a significant gap in test coverage.

Complexity: 2/5
enhancement help wanted

AI Summary: This issue identifies an unused `useEffect` import in the `DecisionForm.tsx` file. Removing this unused import will improve code quality and maintainability.

Complexity: 1/5
bug good first issue

AI Summary: This issue identifies a `console.log` statement present in production code within the `RuleProposalsPage.tsx` file. The `console.log` should be removed or conditionally executed only during development to maintain code quality and prevent unintended output in production environments.

Complexity: 1/5
bug good first issue

AI Summary: The TypeScript parser in the repository mapper is missing the ability to parse `type` aliases and `enum` declarations. This is a feature enhancement that would improve the completeness of the parser's output.

Complexity: 2/5
enhancement good first issue

AI Summary: This issue identifies that the `metadata` field in `src/workers/agents/development/models.py` uses `dict[str, Any]`, which compromises type safety. The suggestion is to improve type safety by addressing this flexible but less secure type usage.

Complexity: 2/5
enhancement good first issue