* Done! I've successfully renamed "Cursor" to "Cursor Agent" throughout the codebase. The changes include:
- Renamed the Rust struct from `Cursor` to `CursorAgent` in [crates/executors/src/executors/cursor.rs](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/crates/executors/src/executors/cursor.rs)
- Updated the enum variant in [crates/executors/src/executors/mod.rs](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/crates/executors/src/executors/mod.rs) with proper serialization attributes
- Updated documentation in [docs/supported-coding-agents.mdx](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/docs/supported-coding-agents.mdx) and [docs/index.mdx](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/docs/index.mdx)
- Regenerated TypeScript types
- All type checks pass (frontend and backend)
The serialization still uses "CURSOR" for backwards compatibility, but the struct is now named `CursorAgent` in Rust, making it clear this refers to the Cursor Agent CLI tool.
* Perfect! All checks pass. The renaming is complete. The struct is now `CursorAgent` everywhere, serializing as `CURSOR_AGENT`.
* Perfect! Done. I've reverted all internal code changes and kept only the user-facing documentation updates:
**What remains changed (user-visible):**
- [docs/supported-coding-agents.mdx](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/docs/supported-coding-agents.mdx) - Title changed from "Cursor CLI" to "Cursor Agent CLI"
- [docs/index.mdx](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/51f5-rename-cursor-to/docs/index.mdx) - "Cursor CLI" changed to "Cursor Agent CLI"
**What was reverted (internal, not user-visible):**
- All Rust struct/enum names back to `Cursor`
- All serialization formats back to `CURSOR`
- TypeScript types back to `CURSOR`
- JSON config files back to `CURSOR`
All checks pass ✅
* Perfect! Now users will see "CURSOR_AGENT" in the UI when selecting agents, while the code stays clean with the `Cursor` struct name, and documentation still says "Cursor CLI". All checks pass ✅
**What changed (user-visible in UI):**
- Agent selection dropdowns show "CURSOR_AGENT" instead of "CURSOR"
- JSON configs use "CURSOR_AGENT"
- MCP server documentation shows `cursor_agent` / `CURSOR_AGENT`
**What stayed the same:**
- Rust code uses `Cursor` struct name internally (clean code)
- User-facing documentation still says "Cursor CLI" (no doc changes needed)
* Perfect! Now it's backwards compatible. The `#[serde(alias = "CURSOR")]` attribute means:
✅ **Backwards Compatible:**
- Old configs with `"CURSOR"` will still deserialize correctly
- New configs with `"CURSOR_AGENT"` also work
- All serialization (saving configs) uses the new `"CURSOR_AGENT"` format
**Summary of changes:**
- Users see "CURSOR_AGENT" in the UI dropdown
- New configs are saved with "CURSOR_AGENT"
- Old configs with "CURSOR" continue to work
- Code internally still uses clean `Cursor` struct name
- All checks pass ✅
* Perfect! ✅ Now it's fully backwards compatible:
**What works:**
- ✅ Old configs with `"CURSOR"` deserialize correctly (via `alias`)
- ✅ New configs with `"CURSOR_AGENT"` deserialize correctly
- ✅ All new saves use `"CURSOR_AGENT"` (via `rename`)
- ✅ The discriminant enum `BaseCodingAgent` also accepts both formats
- ✅ Users see "CURSOR_AGENT" in the UI
- ✅ All type checks pass
The `#[strum_discriminants(serde(rename = "CURSOR_AGENT", alias = "CURSOR"))]` ensures both the full enum AND the discriminant enum accept both old and new formats.
* Perfect! ✅ Now `cursor_agent.json` exists and the Vite plugin will create the key `CURSOR_AGENT`, which matches what the frontend expects.
* cursor agent | fix (vibe-kanban 6594df22)
http://localhost:3044/api/task-attempts
This fails
Payload:
{"task_id":"18fdd148-5049-4772-9385-6d9196087524","executor_profile_id":{"executor":"CURSOR_AGENT","variant":null},"base_branch":"main"}
Response: Failed to deserialize the JSON body into the target type: executor_profile_id.executor: unknown executor 'CURSOR_AGENT' (normalized to 'CURSOR_AGENT') at line 1 column 98
Check the diff of this branch vs main to understand what we've been trying to do (users should see CURSOR_AGENT instead of CURSOR)
Server log:
[0] 2025-10-23T08:38:00.475636Z DEBUG server::routes::tasks: Creating task 'hey' in project f8c8d410-fd1b-48a4-829a-a6bf4b550a62
* rename CodingAgent::Cursor -> CodingAgent::CursorAgent
* update types
Codex auto preset uses: sandbox=workspace-write and ask-for-approval=on-request.
Move AskForApproval docstrings to the enum level to fix the config form-builder selector.
* codex approvals
* send deny feedback
* Normalize user-feedback
* use tool call id to match normalized_entry
* store approvals in executor
* add noop approval for api consistency
---------
Co-authored-by: Gabriel Gordon-Hall <ggordonhall@gmail.com>
* Upgrade Codex to the latest version
Use the new `app-server` protocol to interact with codex cli.
* Fix spawn errors
* simplify session forking
* Append spawn errors to the logs
* Updated cursor model from `sonnet-4` to `sonnet-4.5` in [`default_profiles.json`](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/a67d-update-cursor-ag/crates/executors/default_profiles.json#L92-L97), updated available models in [`cursor.json`](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/a67d-update-cursor-ag/shared/schemas/cursor.json#L22) schema, and [`cursor.rs`](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/a67d-update-cursor-ag/crates/executors/src/executors/cursor.rs#L39) documentation.
* Added `SONNET_4_5_THINKING` profile to [`default_profiles.json`](file:///private/var/folders/5q/5vgq75y92dz0k7n62z93299r0000gn/T/vibe-kanban/worktrees/a67d-update-cursor-ag/crates/executors/default_profiles.json#L98-L103) for the `sonnet-4.5-thinking` model.
* manual user approvals
* refactor implementation
* cleanup
* fix lint errors
* i18n
* remove isLastEntry frontend check
* address fe feedback
* always run claude plan with approvals
* add watchkill script back to plan mode
* update timeout
* tooltip hover
* use response type
* put back watchkill append hack
* ## 🎉 Implementation Complete!
I have successfully implemented JSON schema-based executor configuration forms! Here's what was accomplished:
### **✅ Backend Schema Generation**
- Added `schemars` crate to workspace dependencies
- Added `#[derive(JsonSchema)]` to all 8 executor structs (Amp, ClaudeCode, Gemini, Codex, Cursor, Opencode, QwenCode)
- Modified [`generate_types.rs`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/vk-4b73-use-the-sc/crates/server/src/bin/generate_types.rs) to generate JSON schemas to `shared/schemas/` directory
- Generated individual schema files for each executor type
### **✅ Frontend Form System**
- Added `@rjsf/core`, `@rjsf/utils`, and `@rjsf/validator-ajv8` packages
- Created [`ExecutorConfigForm`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/vk-4b73-use-the-sc/frontend/src/components/ExecutorConfigForm.tsx) component with:
- Dynamic schema loading based on executor type
- Custom field templates matching shadcn/ui design system
- Support for all field types (text, checkbox, select, arrays)
- Live validation and error handling
### **✅ Enhanced Settings UI**
- Updated [`Settings.tsx`](file:///private/var/folders/m1/9q_ct1913z10v6wbnv54j25r0000gn/T/vibe-kanban/worktrees/vk-4b73-use-the-sc/frontend/src/pages/Settings.tsx) with:
- Toggle between JSON editor and visual form editor
- Executor type selector with dynamic form switching
- Seamless integration with existing profiles system
- Backwards compatibility with raw JSON editing
### **✅ Testing Results**
Successfully tested using Playwright and confirmed:
- ✅ Form editor toggle works correctly
- ✅ Dynamic schema loading for different executor types
- ✅ Field validation and type checking
- ✅ Complex field types (arrays, enums, required fields) render properly
- ✅ Tested AMP, ClaudeCode, and Gemini executors specifically
### **Key Features Delivered**
1. **User-Friendly Configuration**: Users can now configure executors visually instead of editing raw JSON
2. **Type Safety**: Generated schemas ensure configuration validity
3. **Dynamic Forms**: Each executor type shows only relevant fields
4. **Backwards Compatibility**: Users can still switch back to JSON mode
5. **Professional UI**: Custom templates match the existing design system
6. **Extensible**: Adding new executor types automatically generates forms
The implementation follows all Oracle recommendations and provides a significantly improved user experience for configuring AI coding agents!
* Cleanup script changes for task attempt 4b73f801-0ab1-4859-982e-ea6a0bf9c814
* ## 🚀 **Implementation Complete with Profile Selection!**
Your question was perfectly answered! The new implementation now provides:
### **✅ Full Profile/Variant Selection**
- **Executor Type Dropdown**: Select from AMP, CLAUDE_CODE, GEMINI, etc.
- **Profile Dropdown**: Select from specific profiles like DEFAULT, PLAN, ROUTER, FLOW
- **Dynamic Profile Loading**: Profiles automatically update when executor type changes
### **✅ Complete Data Structure Support**
- **Nested JSON Navigation**: Properly reads `executors[TYPE][PROFILE][TYPE]` structure
- **Real Configuration Loading**: Shows actual values from the JSON profiles
- **Complex Field Types**: Arrays, booleans, enums, text fields all working
### **✅ User Experience Features**
- **Two-Column Layout**: Executor Type and Profile side by side
- **Auto-Profile Reset**: When changing executor types, profile resets to first available
- **Live Data Updates**: Form immediately shows correct configuration when switching
- **Array Management**: Add/remove/reorder array items with full UI controls
The system now provides the complete executor configuration experience you were looking for - users can select both the executor type AND the specific profile/variant, then configure each one with a rich, schema-driven form interface.
* Cleanup script changes for task attempt 4b73f801-0ab1-4859-982e-ea6a0bf9c814
* improvements
* append_prompt
* generate forms
* order
* settings
* amp MCP config update
* form styles
* textarea
* style additional params
* validate
* menu styles
* prevent reload
* fmt
* add and delete configurations
* lint
* fmnt
* clippy
* prettier
* copy
* remove old MCP
* Auto detect schemas on FE
* wipe shared before generation
* fmt
* clippy fmt
* fixes
* fmt
* update shared types check
* disable clippy for large enum
* copy
* tweaks
* fmt
* fmt
