Integrations

​

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, then start building instead of translating notes into engineering work.

1. Run a meeting with Earmark recording.
2. Use the Engineering Specs template, or a prompt like “Generate a Cursor-ready spec for the API changes we discussed.”
3. Earmark produces a structured artifact with requirements, acceptance criteria, and implementation guidance.
4. Copy the output into Cursor as your starting prompt.

Best templates: Engineering Specs, Technical Architecture, and Ticket Generator.

​

Linear

Turn what you just decided into Linear issues with titles, descriptions, owners, and acceptance criteria, so tickets are ready before the call ends.

1. Run a meeting with Earmark recording.
2. Use the Ticket Generator template, or prompt “Generate Linear tickets from this discussion.”
3. Earmark produces a table of tickets with titles, descriptions, owners, and acceptance criteria.
4. Copy each ticket into Linear, or export the full list.

Best templates: Ticket Generator, Sprint Planning Summary, and Topic Outcome Tracker.

​

v0

Skip the blank canvas. Turn design discussions into v0-ready UI prompts with component descriptions, layout requirements, and interaction details.

1. Run a meeting where UI or design decisions are discussed.
2. Use a prompt like “Generate a v0 prompt for the dashboard layout we discussed, including the data tables and filter sidebar.”
3. Earmark produces a prompt grounded in what was actually said.
4. Paste it into v0 and iterate from a real starting point.

Best templates: Engineering Specs for UI requirements, Topic Outcome Tracker for design decisions, or a custom prompt like “Write a v0 prompt for [specific UI].”

​

Codex

Package your decisions into Codex-ready engineering tasks with clear requirements, constraints, and context from the actual discussion.

1. Run a meeting with Earmark recording.
2. Use the Engineering Specs template, or a prompt like “Generate Codex-ready tasks for the backend changes we discussed.”
3. Earmark produces structured tasks with requirements, constraints, and implementation context.
4. Feed the output into Codex as your task specification.

Best templates: Engineering Specs, Ticket Generator, and Technical Architecture.

​

From Chat to Claude Cowork or Codex

Answers in Chat can go straight to your agent. Under any answer, click Handoff to Claude Cowork or Handoff to Codex to open your question and the answer in that app and keep working.

​

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.
• Describe UI in specifics. “The filter sidebar should have date range, status, and assignee dropdowns” gives v0 what it needs to generate useful components.
• Cover edge cases and constraints. Discussions that include them produce tasks Codex can execute with less back-and-forth.