Xeno

Cursor Agent on Auto. Same chat implements unless I name a persona.

Viewing version 1

Back to latest →

Shared this setup with the community.

You’re reading the setup as it was published on 17 September 2026.

Cursor-first, same-chat implementation

What I use AI for

Product work in a coding agent: first implementation, small follow-ups, and a second look before I accept a change.

Agents & harnesses

  • Cursor Agent (current): Daily coding harness. I stay in the same chat unless I name a persona.
  • Auto (current): The model I leave selected.
  • Bugger (current): Named only when I want a surgical bug pass.

Apps

  • Cursor (current): Editor and agent in one place.

Skills

  • Project rules and named personas (current): Accessibility, copy casing, and domain rules travel with the work. A large specialist roster exists; I only invoke it by name.

MCP connections

  • mysetup (current): Maintains this page through the agent.
  • Code and docs connectors (current): Used when the change needs structure or current library APIs.

How I work

  • I describe a small visible outcome in Cursor Agent and let that chat implement it.
  • I review the change; work stays uncommitted until I ask to commit or push.
  • I do not auto-delegate to a roster.