Integration

Give Cursor the task before it writes the code

Bring the goal, constraints, links, comments, and acceptance notes from One Horizon into Cursor through MCP or a local agent run.

AI assistants and coding agents

CursorCursor
One Horizon
Code from the reviewed scope
Choose editor chat or local execution
Bring completed work back

Code from the reviewed scope

Cursor can read the full work item instead of relying on a title or a prompt reconstructed from memory

Choose editor chat or local execution

Use MCP inside Cursor or let a local Cursor agent run assigned work from One Horizon

Bring completed work back

Capture the result against the original task so the rest of the team can see what changed

Connect Cursor to the decisions behind the task

The editor gets product context before implementation, and the workspace keeps the outcome after the coding session.

Ask Cursor about assigned work

Find today’s issues and todos, then pull the selected item into the editor conversation.

Assigned issue context surfaced inside Cursor

Run a task through the Cursor CLI

Assign work to a local Cursor agent when you want One Horizon to start and track the run.

Task running through the Cursor CLI inside a One Horizon workflow

Capture the finished result

Summarize completed work back into One Horizon instead of leaving the outcome in editor chat.

Completed workflow run with review loops and linked pull request

For teams that already build in Cursor

Keep the editor while adding a shared brief, tracked execution, and a result the rest of the team can follow.

Feature implementation

Bring the accepted scope and supporting product links into Cursor before coding

Local agent task

Assign a focused todo to the Cursor CLI and follow the run from One Horizon

Completed-work capture

Record what Cursor changed so recaps and initiative progress reflect the result

Put the whole task in Cursor

Connect the editor to One Horizon and keep the brief, code, and completed result tied together.