Give each agent thread its own running instance of the app

[SunkenInTime]

One bullet under AGENTS.md's general rules: each thread starts one instance of the app, keyed by worktree or branch name, with its own Hive store inside the app container and its own pid file; hot reloads it with SIGUSR1 after each edit; keeps it for the thread's life; never signs out from it, since the session is shared.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 76af8445-b80c-47e0-84c6-8c86d89e2990

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

Safe to merge based on the verified isolated-store and PID-file reload behavior.

What we checked:

• Alternate store argument ignored: The launch parser consumes the Hive-store option and does not append it to file-open arguments. Startup initializes Hive with the prepared alternate directory when that option is provided.
• Unprepared Hive directory: Alternate-store setup creates, canonicalizes, and write-probes the requested directory before returning it to startup. A preparation failure is surfaced instead of falling back to the default shared store.
• PID reload signal unsupported: The repository-local Flutter tool documents SIGUSR1 hot reload for the PID-file process. A resident application was launched and successfully hot reloaded after SIGUSR1 was sent to the PID recorded in that file.
• Ran the hive_store_launch_test.dart test suite from the repository and confirmed the full run passed (13/13 tests), with the targeted named subset also passing (2/2).
• Validated the six alternate-store preparation tests by capturing before, during, and after states, including a focused full-suite run; all six tests passed.
• Validated the SIGUSR1 hot-reload capability flow, including pre-capability capture checks, full resident-flow execution with Xvfb/Chrome, and confirming the document reference; all steps completed successfully.

Summary

• This update documents a parallel-development workflow where each worktree or branch runs its own Flutter process, Hive store, PID file, and hot-reload signal.
• The documented store-selection, directory-preparation, and PID-file reload behaviors were exercised successfully. No correctness or security defect was found.

_{Reviews (1) · Last reviewed commit: "Give each agent thread its own running i..."}