Skip to main content

​
How integrations work

Earmark integrations are copy-and-paste by design. There are no OAuth flows, API keys, or third-party permissions to configure. Run a meeting, generate an artifact with the right template or prompt, and drop the output into the tool where the work happens. This means integrations work immediately for every team member, with no admin setup and no data leaving Earmark until you explicitly copy it.

​
Supported tools

Cursor

Turn meeting decisions into Cursor-ready specs and code prompts.

Linear

Generate tickets with titles, descriptions, and acceptance criteria.

v0

Convert design discussions into v0-ready UI prompts and component direction.

Codex

Package engineering decisions into Codex-ready task specifications.

​
Getting the best results

  • Pick the right template before the meeting starts. Engineering Specs, Ticket Generator, and Technical Architecture each produce output shaped for different tools.
  • Be specific in custom prompts. “Generate a Cursor prompt for the auth refactor focusing on the session token migration” produces better output than “Summarize the engineering discussion.”
  • Name owners and priorities out loud. Earmark captures what is said, so stating “Jane owns the auth migration, targeting next sprint” populates ticket fields more accurately.