[Suggestion] UX Improvements & Developer Experience Enhancements

[SherlockSalvatore]

HarnessKit 是一个很棒很有趣的项目，非常感谢！！！后续可以演进出更丰富的功能和更好的体验～以下是我的一些小建议(个人手打后 AI 帮整理了下)：
Hi there! HarnessKit is such an awesome and fun project to play with. I can really see it evolving into something incredibly feature-rich down the line. While exploring it, I jotted down a few small suggestions for UX and Developer Experience (DX):

1. UX: Reorder Tabs in the Agents Module

Currently, the "Memory" section appears before "Settings" and "Extensions". When an agent tracks memory across multiple project workspaces, the Memory list becomes extremely long, forcing users to scroll endlessly just to reach the Settings or Extensions configuration.
Suggestion: Move "Settings" and "Extensions" above "Memory" (or reorder the navigation tabs) so high-frequency management actions are instantly accessible.

2. Feature: Memory Sidebar & Categorization

As the number of agents and tracked projects grows, flattening all Memory logs into one scrolling view can be overwhelming.
Suggestion for future iterations:

• Collapse "Memory" into a dedicated sidebar panel (similar to how Extensions are managed).
• Add capabilities to group, filter, and categorize memory logs by specific Agents and Project Workspaces for better readability.

3. Housekeeping: Ignore Auto-generated Tauri Schemas

The crates/hk-desktop/gen/schemas/*.json files are dynamically generated by Tauri v2 during build/dev time (e.g., when plugin versions change). Currently, they are not ignored, which pollutes the Git working tree and causes unnecessary diffs.
Suggestion: Please add crates/hk-desktop/gen/ to .gitignore.

4. Docs: Add Dependencies & Developer Guide to README

The current README.md is excellent for end-users but lacks essential information for contributors. Since this is a Tauri + Rust + React monorepo, it can be slightly confusing to set up initially.
Suggestion:

• Add a Development / Contributing section.
• List required dependencies (e.g., Node.js >= 18, Rust/Cargo, pnpm, Tauri CLI).
• Add basic commands for local development (e.g., pnpm install, cargo tauri dev) and building (e.g., ./build.sh).
• Briefly explain the monorepo architecture (hk-core, hk-desktop, hk-cli, and frontend src/).

5. Question/Suggestion: "Install to Agent" Compatibility & Codex Support

While testing the "Install to Agent" feature for skills, a couple of questions came up:

• Agent Differentiation: Should the installation logic or UI specifically differentiate between Gemini CLI and Antigravity when handling skills? Currently, it seems they are treated uniformly, but their underlying skill formats or execution engines might differ.
• Codex Support: Are there any plans or ETAs on when Codex will be fully supported for extension installation?

Thanks again for the awesome tool! Let me know if you'd accept a PR for any of the above.

[RealZST]

Thanks for the detailed feedback. It’s very helpful. Status on each item:

• 1 is done in v1.2.1. Order is now settings → rules → memory → ignore → extensions. Slightly different from your suggestion: Rules and Memory stay next to each other (b/c they are both text files the agent reads), and Extensions still stays at the end, because there's already a dedicated Extensions page in the main nav.
• 2 isn't done yet, but I have a plan. The Agents detail page already shows Global / project name pills in the top-right. The plan is to make them clickable filters that filter all sections (rules / memory / settings / extensions) by scope. This also needs project-level extension scanning (so the Extensions summary card can filter the same way). It's planned for the next version. If you have any ideas on how this should work, feel free to drop a comment.
• 3 and 4 are done in v1.2.1.
• For 5, I need to look into these more before answering. Will reply later.

Thanks again for all your suggestions!