cyrusagents
diff --git a/‎.claude/agents/f1-test-drive.md‎
Lines changed: 8 additions & 183 deletions b/‎.claude/agents/f1-test-drive.md‎
Lines changed: 8 additions & 183 deletions
diff --git a/‎.claude/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions b/‎.claude/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.codex/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions b/‎.codex/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎.gitignore‎
Lines changed: 2 additions & 1 deletion b/‎.gitignore‎
Lines changed: 2 additions & 1 deletion
diff --git a/‎.opencode/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions b/‎.opencode/skills/f1-test-drive‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions b/‎AGENTS.md‎
Lines changed: 1 addition & 0 deletions
diff --git a/‎CHANGELOG.internal.md‎
Lines changed: 5 additions & 0 deletions b/‎CHANGELOG.internal.md‎
Lines changed: 5 additions & 0 deletions
diff --git a/‎CHANGELOG.md‎
Lines changed: 8 additions & 0 deletions b/‎CHANGELOG.md‎
Lines changed: 8 additions & 0 deletions
@@ -5,191 +5,16 @@ tools: Bash, Read, Write, Glob, Grep, TodoWrite
 model: sonnet
 ---
 
-# F1 Test Drive Agent
+# F1 Test Drive Agent (Wrapper)
 
-You are the F1 Test Drive Agent, responsible for orchestrating comprehensive test drives of the Cyrus agent system. Your role is to validate the entire pipeline: Issue-tracker -> EdgeWorker -> Renderer.
+Use the shared canonical skill:
 
-## Your Mission
+- `skills/f1-test-drive/SKILL.md`
 
-Execute test drives that verify:
-1. **Issue-tracker verification**: Issues are created and processed correctly
-2. **EdgeWorker verification**: Git worktrees are created, agent sessions start, outputs are available via RPC
-3. **Renderer verification**: Outputs are accessible and well-formed
+Treat this subagent file as a thin harness-specific wrapper only.
 
-## Test Drive Protocol
+Execution requirements:
 
-### Phase 1: Setup
-
-1. **Create test repository** (if needed):
-   ```bash
-   cd apps/f1
-   ./f1 init-test-repo --path /tmp/f1-test-drive-<timestamp>
-   ```
-
-2. **Start F1 server**:
-   ```bash
-   CYRUS_PORT=3600 CYRUS_REPO_PATH=/tmp/f1-test-drive-<timestamp> bun run apps/f1/server.ts &
-   ```
-
-3. **Verify server health**:
-   ```bash
-   CYRUS_PORT=3600 ./f1 ping
-   CYRUS_PORT=3600 ./f1 status
-   ```
-
-### Phase 2: Issue-Tracker Verification
-
-1. **Create test issue**:
-   ```bash
-   CYRUS_PORT=3600 ./f1 create-issue \
-     --title "<issue title>" \
-     --description "<issue description>"
-   ```
-
-2. **Verify issue created**: Confirm issue ID returned
-
-### Phase 3: EdgeWorker Verification
-
-1. **Start agent session**:
-   ```bash
-   CYRUS_PORT=3600 ./f1 start-session --issue-id <issue-id>
-   ```
-
-2. **Monitor session activities**:
-   ```bash
-   CYRUS_PORT=3600 ./f1 view-session --session-id <session-id>
-   ```
-
-3. **Verify**:
-   - Session started successfully
-   - Activities are being tracked
-   - Agent is processing the issue
-
-### Phase 4: Renderer Verification
-
-1. **Check activity output format**:
-   - Activities have proper types (thought, action)
-   - Timestamps are present
-   - Content is well-formed
-
-2. **Test pagination** (if many activities):
-   ```bash
-   CYRUS_PORT=3600 ./f1 view-session --session-id <session-id> --limit 10 --offset 0
-   ```
-
-### Phase 5: Cleanup
-
-1. **Stop session**:
-   ```bash
-   CYRUS_PORT=3600 ./f1 stop-session --session-id <session-id>
-   ```
-
-2. **Stop server**: Kill the background server process
-
-## Test Drive Documentation
-
-Create a test drive report in `apps/f1/test-drives/` with this structure:
-
-```markdown
-# Test Drive #NNN: [Goal Description]
-
-**Date**: YYYY-MM-DD
-**Goal**: [One sentence]
-**Test Repo**: [Path to test repository]
-
----
-
-## Verification Results
-
-### Issue-Tracker Verification
-- [ ] Issue created successfully
-- [ ] Issue ID returned
-- [ ] Issue details accessible
-
-### EdgeWorker Verification
-- [ ] Session started successfully
-- [ ] Git worktree created (check server logs)
-- [ ] Activities being tracked
-- [ ] Agent processing issue
-
-### Renderer Verification
-- [ ] Activities have proper format
-- [ ] Pagination works correctly
-- [ ] Search works correctly
-
----
-
-## Session Log
-
-### [Timestamp] - [Phase]
-
-**Command**: [Exact command]
-**Output**: [Key output]
-**Status**: [PASS/FAIL]
-
----
-
-## Final Retrospective
-
-### What Worked Well
-[List successes]
-
-### Issues Found
-[List problems with severity]
-
-### Recommendations
-[Actionable improvements]
-
-### Overall Score
-- **Issue-Tracker**: X/10
-- **EdgeWorker**: X/10
-- **Renderer**: X/10
-- **Overall**: X/10
-
----
-
-**Test Drive Complete**: [Timestamp]
-```
-
-## Acceptance Criteria for Test Drives
-
-A test drive PASSES if:
-1. Server starts successfully
-2. Issue is created and has valid ID
-3. Session starts and activities appear
-4. Activities are well-formatted with types and timestamps
-5. Session can be stopped gracefully
-6. No unhandled errors occur
-
-A test drive FAILS if:
-- Server won't start
-- Issue creation fails
-- Session won't start
-- No activities appear after 30 seconds
-- Malformed activity data
-- Unhandled exceptions
-
-## Important Notes
-
-- Always use `CYRUS_PORT=3600` to avoid conflicts
-- Create fresh test repos for each test drive
-- Document all observations, both positive and negative
-- Take screenshots of terminal output when relevant
-- Clean up test repos after successful test drives
-- If the test drive fails, preserve the state for debugging
-
-## Sample Test Issues
-
-For the rate limiter test repo, use these realistic issues:
-
-1. **Sliding Window Algorithm**:
-   - Title: "Implement sliding window rate limiter algorithm"
-   - Description: Implement the SlidingWindowRateLimiter class with configurable window size
-
-2. **Fixed Window Algorithm**:
-   - Title: "Implement fixed window rate limiter algorithm"
-   - Description: Add FixedWindowRateLimiter that resets counter at fixed intervals
-
-3. **Unit Tests**:
-   - Title: "Add comprehensive unit tests for rate limiter"
-   - Description: Add Vitest tests for TokenBucketRateLimiter covering edge cases
+1. Load and follow `skills/f1-test-drive/SKILL.md` as the primary protocol.
+2. Keep behavior aligned with the shared skill so other harnesses can reuse the same source.
+3. Prefer updating the shared skill over adding logic here.
@@ -0,0 +1 @@
+../../skills/f1-test-drive
@@ -0,0 +1 @@
+../../skills/f1-test-drive
@@ -1,5 +1,6 @@
 # Dependency directories
-node_modules/
+node_modules
+**/node_modules
 
 # Build output
 dist/
 
@@ -0,0 +1 @@
+../../skills/f1-test-drive
@@ -0,0 +1 @@
+CLAUDE.md
@@ -5,6 +5,7 @@ This changelog documents internal development changes, refactors, tooling update
 ## [Unreleased]
 
 ### Changed
+- Merged `main` into `cypack-807` branch, resolving 7 merge conflicts and fixing auto-merge issues across AgentSessionManager, EdgeWorker, GitService, ProcedureAnalyzer, gemini-runner, and changelogs. Updated 2 test files from `IIssueTrackerService` to `IActivitySink` interface. ([CYPACK-821](https://linear.app/ceedar/issue/CYPACK-821), [#873](https://github.com/ceedaragents/cyrus/pull/873))
 - Decoupled Slack webhook handler from `RepositoryConfig`: introduced `NoopActivitySink` for non-repository sessions, dedicated `slackSessionManager` on `EdgeWorker`, and `slackThreadSessions` map for thread-based session reuse. `createSlackWorkspace` now creates plain directories under `~/.cyrus/slack-workspaces/` instead of git worktrees. Runner config is built inline (bypassing `buildAgentRunnerConfig` which requires a repository). Added `SlackReactionService` to `cyrus-slack-event-transport` package. ([CYPACK-815](https://linear.app/ceedar/issue/CYPACK-815), [#868](https://github.com/ceedaragents/cyrus/pull/868))
 - Refactored logging across all packages to use a dedicated `ILogger` interface and `Logger` implementation in `packages/core/src/logging/`. Replaced direct `console.log`/`console.error` calls in EdgeWorker, AgentSessionManager, ClaudeRunner, GitService, RepositoryRouter, SharedApplicationServer, SharedWebhookServer, WorktreeIncludeService, ProcedureAnalyzer, AskUserQuestionHandler, LinearEventTransport, and LinearIssueTrackerService with structured logger calls. Log level is configurable via the `CYRUS_LOG_LEVEL` environment variable (DEBUG, INFO, WARN, ERROR, SILENT).
 - Added source context (session ID, platform, issue identifier, repository) to log messages via `logger.withContext()`, enabling easier debugging and log filtering across concurrent sessions
@@ -20,6 +21,10 @@ This changelog documents internal development changes, refactors, tooling update
 - Created `GlobalSessionRegistry` class for centralized session storage across all repositories, enabling cross-repository session lookups in orchestrator workflows ([CYPACK-725](https://linear.app/ceedar/issue/CYPACK-725), [#766](https://github.com/ceedaragents/cyrus/pull/766))
 - Extracted `IActivitySink` interface and `LinearActivitySink` implementation to decouple activity posting from `IIssueTrackerService`, enabling multiple activity sinks to receive session activities ([CYPACK-726](https://linear.app/ceedar/issue/CYPACK-726), [#767](https://github.com/ceedaragents/cyrus/pull/767))
 - Integrated `GlobalSessionRegistry` with `EdgeWorker`, making it the single source of truth for parent-child session mappings and cross-repository session lookups ([CYPACK-727](https://linear.app/ceedar/issue/CYPACK-727), [#769](https://github.com/ceedaragents/cyrus/pull/769))
+- Added Cursor harness `[agent=cursor]`, including offline F1 drives for stop/tool activity, resume continuation, and permission synchronization behavior. Also added project-level Cursor CLI permissions mapping from Cyrus tool permissions (including subroutine-time updates), pre-run MCP server enablement (`agent mcp list` + `agent mcp enable <server>`), switched the default Codex runner model to `gpt-5.3-codex`, and aligned edge-worker Vitest module resolution to use local `cyrus-claude-runner` sources during tests. ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
+
+### Fixed
+- Updated orchestrator system prompts to explicitly require `state: "To Do"` when creating issues via `mcp__linear__create_issue`, preventing issues from being created in "Triage" status. ([CYPACK-761](https://linear.app/ceedar/issue/CYPACK-761), [#815](https://github.com/ceedaragents/cyrus/pull/815))
 
 ## [0.2.21] - 2026-02-09
 
 
@@ -10,10 +10,18 @@ All notable changes to this project will be documented in this file.
 
 ### Changed
 - Slack agent sessions now run in transient empty directories instead of git worktrees, and subsequent @mentions in the same thread share the same session context. ([CYPACK-815](https://linear.app/ceedar/issue/CYPACK-815), [#868](https://github.com/ceedaragents/cyrus/pull/868))
+- **Agent and model selectors now work across Claude, Gemini, and Codex** - You can now set runner and model directly in issue descriptions using `[agent=claude|gemini|codex]` and `[model=<model-name>]`. This is not Codex-only: selectors apply to all supported runners. `[agent=...]` explicitly selects the runner, `[model=...]` selects the model and can infer runner family, and description tags take precedence over labels. ([#850](https://github.com/ceedaragents/cyrus/pull/850))
+- **Codex tool activity is now visible in Linear sessions** - Codex runs now emit tool lifecycle activity (including command execution, file edits, web fetch/search, MCP tool calls, and todo updates) so activity streams show execution details instead of only final output. ([#850](https://github.com/ceedaragents/cyrus/pull/850))
+- **Codex todo output now renders as proper checklists** - Todo items are now formatted as markdown task lists (`- [ ]` and `- [x]`) for correct checklist rendering in Linear. ([#850](https://github.com/ceedaragents/cyrus/pull/850))
+- **Major new feature: Cursor agent harness support** - Cyrus now supports Cursor as a first-class agent option. To use it, set `[agent=cursor]` in the issue description or apply a `cursor` issue label; either selector runs end-to-end with the Cursor runner and posts the final response back to the issue thread. Cursor runs now map Cyrus tool permissions into project-level Cursor CLI permissions, pre-enable configured MCP servers before run, and refresh permissions between subroutines so permission changes take effect without restarting the issue flow. Cursor sandbox is enabled by default for tool execution isolation; set `CYRUS_SANDBOX=disabled` to disable. Before each run, Cyrus validates that the installed `cursor-agent` version matches the tested version; a mismatch posts an error to Linear. Set `CYRUS_CURSOR_AGENT_VERSION` to your installed version to override. Assembled cursor-agent CLI args are now logged to console and session log files for debugging. Codex default runner model is now `gpt-5.3-codex` (configurable via `codexDefaultModel`). ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
 
 ### Fixed
 - Summary subroutines now properly disable all tools including MCP tools like Linear's create_comment ([#808](https://github.com/ceedaragents/cyrus/pull/808))
 - Procedures no longer fail when a subroutine exits with an error (e.g., hitting the max turns limit). Cyrus now recovers by using the last successful subroutine's result, allowing the workflow to continue to completion instead of stopping mid-procedure ([#818](https://github.com/ceedaragents/cyrus/pull/818))
+- **Codex usage limit errors now display full message in Linear** - When Codex hits usage limits or other turn.failed errors, the actual error message is now posted to Linear agent activity instead of a generic message. ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
+- **Cursor project .cursor/cli.json is now backed up and restored** - CursorRunner no longer overwrites the project's `.cursor/cli.json`. It temporarily renames the existing file before writing Cyrus permissions, then restores the original when the session ends. ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
+- **Cursor API key no longer in CLI args or logs** - The Cursor API key is now passed only via the `CURSOR_API_KEY` environment variable, so it never appears in spawn logs or terminal output. The `--force` option has also been removed from cursor-agent invocations. ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
+- **Cursor completed todos now display as checked in Linear** - Cursor API uses `TODO_STATUS_COMPLETED` for completed todo items; the formatter now recognizes this so completed items render as `- [x]` instead of `- [ ]` in Linear activity. ([CYPACK-804](https://linear.app/ceedar/issue/CYPACK-804), [#858](https://github.com/ceedaragents/cyrus/pull/858))
 
 ## [0.2.21] - 2026-02-09