Find good first issues on GitHub

AI Summary: This feature request aims to make the built-in search action context-aware. When text is selected within a web browser, the search should open in a new tab of that same browser. If the text is selected outside of a browser, it will fall back to opening in the system's default browser.

AI Summary: This issue requests the creation of a concise markdown cheatsheet for the `contract.yaml` file. The goal is to provide a quick reference for new contributors, listing each field with its meaning, requirement status, a minimal example, and common mistakes, thereby reducing the need to consult the longer, detailed specification document.

AI Summary: This issue is a beginner-friendly task to add a new wallpaper URL to a JSON file. No coding or repository setup is required, making it ideal for first-time open-source contributors and Hacktoberfest participants. The contribution can be completed directly in the browser within a minute.

AI Summary: This issue requests the documentation of a new 'Monitor-Alert-Escalate' pattern for an agent. This pattern involves continuous monitoring of a source, alerting on specific thresholds, and escalating to humans only for high-severity events. The deliverable is a markdown file detailing the pattern's intent, use cases, structure, and requirements, following the format of an existing documented pattern.

AI Summary: This issue points out a discrepancy in the `CONTRIBUTING.md` file, which incorrectly states Xcode 15+ as a prerequisite. The project actually requires Xcode 16+ due to its use of Swift 6 with strict concurrency, as indicated in the `README.md`. The proposed solution is to update the `CONTRIBUTING.md` to reflect the correct Xcode version.

AI Summary: The `updateAll()` function in `ExtensionUpdateManager.swift` uses `try?` which silently ignores any errors during extension updates. This prevents users from knowing which updates failed and hinders debugging. The proposed solution involves capturing, logging, and reporting individual update failures to the user.

AI Summary: This bug report identifies unsafe force-casts (`as! T`) in the `SettingsStore.get` method that can lead to runtime crashes if `UserDefaults` returns unexpected data types. The proposed solution is to replace these force-casts with safe conditional casts (`as? T`) and provide a fallback to the default value, ensuring the application doesn't crash due to corrupted or mismatched settings.

AI Summary: The `validate_extension.sh` script currently fails to check if local icon files referenced in the extension manifest actually exist. This enhancement proposes adding a filesystem check to ensure all local icon paths are valid, preventing broken references from being published.

AI Summary: This feature request aims to enable AppleScript actions to access user-configured extension options. Currently, only selection text variants are injected into AppleScript scripts, preventing access to settings like API keys. The proposed solution involves dynamically injecting these options as AppleScript properties into the script preamble during runtime.

AI Summary: This issue identifies an architectural anti-pattern where two separate packages, `pkg/turn/journal.go` and `pkg/convergence/mutation/journal.go`, independently implement the same operation journaling mechanism. This duplication leads to increased maintenance overhead, potential for divergence in fixes, and the risk of one implementation becoming obsolete while still appearing functional.

AI Summary: The `Ledger.persistLocked` function in `pkg/convergence/mutation` uses an outdated and less durable persistence method. It writes to a fixed temporary file and renames it without proper synchronization, which could lead to data loss or corruption during crashes. This pattern has already been corrected in other parts of the codebase.

AI Summary: This issue proposes to refactor a large E2E test file (`mission-control-stress.spec.ts`) into smaller, more manageable files. The goal is to improve maintainability and organization by splitting the 1484-line spec into several new files, each focusing on a specific aspect of mission control stress testing, while adhering to established file-splitting rules.

AI Summary: This issue is a "Good First Issue" that asks contributors to add a new common Japanese learner mistake to a JSON file. No coding is required, and the task can be completed in under a minute directly from the browser by following simple instructions.

AI Summary: This issue proposes to refactor a large end-to-end test file (`mission-journey.spec.ts`) which currently exceeds 1400 lines. The plan is to split it into multiple smaller, more manageable spec files, separating shared setup code into a dedicated helper file and distributing the test journeys across new spec files based on their functionality.

AI Summary: The `server_test.go` file within the `pkg/agent` package has become excessively large, containing 3528 lines and 113 tests. The proposed solution is to split this monolithic test file into several smaller, more manageable files, each focusing on a specific functional area of the server, while adhering to established file-splitting rules for test helpers and imports.

AI Summary: This issue proposes to refactor a large Go file (`kagent.go`) by splitting it into smaller, more manageable files. The goal is to improve code organization by separating helper functions and distinct handler families (kagent CRDs and Kagenti) while maintaining the same package and no API changes. This is a purely structural change to enhance readability and maintainability.

AI Summary: The `pi-native cli-config` provider incorrectly resolves launch models from a bundled catalog instead of the live workspace model listing. This can lead to requests for non-existent endpoints, surfacing as runtime 404 errors. The fix involves prioritizing live workspace models over the bundled catalog for this specific provider path.

AI Summary: CI builds for the extproc image are failing because the `centos:stream10` Docker image, which is a floating tag, was updated to a new version that lacks `/bin/sh`. This prevents the initial `RUN` command in the Dockerfile from executing, causing subsequent build steps to fail. The issue impacts multiple CI jobs and open pull requests.

AI Summary: This issue identifies a critical gap in the v5 release process: the absence of a trackable, defined set of criteria for General Availability (GA). Currently, the GA bar is only described in prose, making it impossible for operators to gauge progress or for the team to confidently announce v4 End-of-Life. The proposed solution is to create a GitHub milestone or tracker issue that enumerates all necessary conditions for v5 GA.

AI Summary: This issue requires addressing a TypeScript error in the `renderSaveCredentialsForm.tsx` file. The error arises because the `trpc.getCapturedInputEvents.query()` can return `inputsUrl` as undefined, while the `PromptPassword` component expects a required string. The goal is to explicitly model this missing URL case and remove the TypeScript suppression without altering the existing save-prompt behavior.

AI Summary: This issue aims to improve type safety in the click recorder by removing a TypeScript suppression. The goal is to correctly narrow down the event target to an `HTMLInputElement` before accessing its properties, ensuring that only relevant input elements are recorded and that the code adheres to type-checking without unsafe casts. This involves implementing runtime type guards and adding a focused test to verify the behavior.

AI Summary: This issue requires updating the `web-extension/README.md` file to reflect the current toolchain and product state. It involves correcting outdated information about build scripts, testing frameworks (Jest to Vitest), browser support (adding Edge), and fixing a typo in Firefox instructions, ensuring consistency with the official download page.

AI Summary: This feature request aims to prevent redundant review dispatches for unchanged goal attempts. It proposes implementing a configurable budget per reviewer and attempt to stop endless review loops and ensure new attempts are only eligible after concrete progress. This will improve efficiency by avoiding repeated submissions of the same review lanes when no changes have occurred.

AI Summary: This issue is a beginner-friendly task to add a new Japanese example sentence to a JSON file. It requires no coding and can be completed in under a minute by forking the repository, editing the file directly in the browser, and submitting a pull request.

AI Summary: This issue is a research task to determine the availability, pricing, and performance of trace methods across configured RPC upstreams for various blockchain chains. The goal is to assess the feasibility of using trace methods for sourcing triggers, which is a prerequisite for a larger feature development.

AI Summary: This issue proposes adding a new trigger source to KeeperHub that can subscribe to off-chain signals (like oracle price updates or bridge queue messages) before they are finalized on-chain. This would allow for more proactive reactions to events, such as preventing liquidations, without requiring users to run their own always-on services.

AI Summary: This issue proposes enabling triggers for security monitoring that can detect events currently invisible to `eth_getLogs`, such as reverted transactions, internal ETH transfers via `call`, and `delegatecall` into unlogged implementations. The solution involves sourcing triggers from block traces instead of emitted events, allowing for monitoring of caller, callee, selector, value, and success/revert status.

AI Summary: This issue proposes a new workflow trigger mechanism that allows actions to be initiated based on derived contract state thresholds, rather than solely relying on emitted events. Currently, workflows cannot react to conditions like health factors dropping below a certain point or balances falling below a threshold if the contract doesn't emit a specific event for it. The proposed solution involves an `eth_call` to a user-specified view function once per block, comparing the result against a threshold.

AI Summary: This issue addresses an outdated dependency on PlantUML within the `codebase-uml` skill. The skill needs to be updated to reflect 36 commits ahead in PlantUML's default branch, specifically addressing changes in browser SVG size limits and `!pragma layout smetana` handling. The goal is to ensure the `codebase-uml` skill accurately represents PlantUML's behavior across different execution modes (CLI vs. browser) and clearly documents which upstream changes are adopted or excluded.

AI Summary: The docs Next.js application lacks essential health and readiness endpoints, making it difficult to detect deployment issues. Additionally, there are no documented procedures for rolling back bad deployments or for handling incidents, impacting the reliability and maintainability of the application.