Skip to content
New: AI agents →
[ Solutions ]

Task management in VS Code, Figma, and Framer

File tasks from VS Code, Figma and Framer without switching tabs.

Start free
Book a walkthrough
  • 10+ editors, one extension
  • Figma and Framer plugins
  • Connect with an API key
/ first-party extensions
3
/ MCP tools for AI hosts
31
/ tasks retyped by hand
0
[ How it works ]

Install once, then file work from where you already are

One token, every extension.

  1. 01

    Install the extension

    Worksynk in the VS Code marketplace, or import the Figma and Framer plugins. Same account, same workspace.

  2. 02

    Paste an API key

    Create a personal access token under Settings → API keys and paste it once. The extension remembers your workspace and last project.

  3. 03

    Create from the selection

    Highlight code, or select a frame on canvas. The title, file path, and design link fill themselves in.

  4. 04

    Work it without switching

    Assign, set priority, move to review, mark done, and leave notes with @mentions — from inside the editor or the design tool.

[ Who it’s for ]

For the people who never wanted a project tool

Engineers and designers do not want another tab to maintain. The point of the extensions is that filing work costs nothing, so it actually gets filed.

  1. 01The bug occurs to you in the editor, and filing it means losing your place
  2. 02Design feedback lives in comments nobody converts into work
  3. 03Screenshots get pasted into chat instead of onto the task
  4. 04The task never links back to the frame or the file it came from
  5. 05You would rather ask your AI host than open a dashboard
  6. 06You want events in your own tooling, signed and verifiable
[ Compatibility ]

Where the extensions run

One VS Code extension covers every fork that loads a VSIX, and the design plugins install straight into Figma and Framer.

Editors

10 tools

Built against the VS Code extension API, so it runs anywhere that API does — including the AI editors people are actually moving to.

  • Visual Studio CodeVS Code Marketplacefulgid.worksynk
  • CursorMarketplace, or install from VSIX
  • Google AntigravityVSIX, or point it at the VS Marketplace
  • WindsurfMarketplace or VSIXFormerly Codeium; includes Cascade
  • VSCodiumOpen VSX Marketplace or VSIX
  • TraeVSIX, or marketplace where available
  • KiroOpen VSX or VSIXAmazon's AI IDE
  • VoidOpen VSX or VSIXOpen-source AI editor
  • Firebase StudioOpen VSXGoogle's cloud IDE
  • OVOther VS Code forksAny host that loads a .vsix

Design tools

02 tools

Dedicated plugins, not a generic embed — each one knows what you have selected and links the task back to it.

  • FigmaPlugins → Import from manifestIssues on the selected frame, section, or page
  • FramerPlugin, v1.2Templates, @mention notes, screenshot on create

Editors that default to Open VSX — Antigravity, Kiro, Void, Firebase Studio — may not surface Worksynk in search until you install the VSIX or switch the marketplace URL. Both routes are in the extension's install guide. JetBrains, Neovim, and browser-only IDEs have no dedicated extension; use MCP or the REST API there.

Coming next

Not shipped yet

Listed here so you know where it stands rather than finding out after you commit. Neither is built yet, and neither is a date.

  • WebflowA thin form and CMS bridge into tasks. Scoped, not scaffolded.
  • JAJetBrains and NeovimNo dedicated extension planned — use MCP or the REST API today.
[ Before / after ]

What stops being manual

None of these need a process change. They are what the extensions do once installed.

How it works now

  • You spot a bug mid-file, switch to the browser, find the project, and retype what you were looking at.

  • Design feedback sits in Figma comments that nobody turns into tasks.

  • A screenshot gets pasted into chat, and the task it belongs to never gets one.

  • Triage means opening the board, even for a status change or an assignment.

How it works on Worksynk

  • File a task without leaving the file

    Create it from the editor. The selection and file path attach themselves, and you never left the file.

  • Frames become linked issues

    Create an issue from the frame and it links automatically, so the work and the design stay attached.

  • Screenshot lands on the task

    Attach it on create from Framer — paste it, pick a file, or use the selected image layer.

  • Triage without the board

    Filter, assign, start, review, done, or leave a note with @mentions from inside the plugin.

[ Features ]

Three first-party extensions, not a REST tutorial

Built around what you were already doing.

  • 01

    VS Code extension

    Create tasks from code. Selection and file path attach automatically. Works in Cursor and Antigravity too.

  • 02

    Figma plugin

    Create an issue from a frame and it links automatically. See issues on the current selection.

  • 03

    Framer plugin

    Templates, notes with @mentions, screenshots on create, and the published design URL filled in for you.

  • 04

    MCP for AI hosts

    Separate from the extensions: point Claude, ChatGPT, or Cursor's agent at 31 tools over MCP.

  • 05

    Git activity

    Reference a task in a commit, branch, or PR title and it attaches to the work.

  • 06

    Signed webhooks

    Push events into your own tooling, signed so you can verify them.

[ Capabilities ]

What each extension actually does

All three use one personal access token.

VS Code: task from codeExtensions
Pick a project, set a title, choose an assignee. The highlighted selection and the file path are attached to the task without being asked for.
VS Code: editor coverageExtensions
Built against the VS Code extension API, so it runs in VS Code, Cursor, Antigravity, Windsurf, VSCodium, Trae, Kiro, Void, Firebase Studio, and any other fork that loads a VSIX.
Figma: issues on the selectionExtensions
List the issues linked to the current frame, section, or page; create a new one that links itself; or search and link an existing issue. Assign and mark done in place.
Framer: templates and captureExtensions
Task, Feedback, Review, Content and Polish templates set type, priority and title prefix. Attach a screenshot by paste, file, or the selected image layer.
Framer: notes with mentionsExtensions
Rich-text notes with @mentions that notify people, and reference tasks and projects as chips — the same behaviour as the portal.
[ Modules ]

The modules behind this page.

Worksynk ships as modules a workspace owner switches on under Settings → Modules. Most are off by default even when your plan covers them; pricing shows what each plan includes.

[ Questions ]

Common questions

Which editors does the VS Code extension work in?

VS Code, Cursor, Antigravity, Windsurf (formerly Codeium, including Cascade), VSCodium, Trae, Kiro, Void, Firebase Studio — and any other fork that loads a VSIX. Install fulgid.worksynk from the VS Code Marketplace or Open VSX, or import a VSIX directly. Editors that default to Open VSX may not show it in search until you do one of those.

Is there a Framer plugin?

Yes. It creates tasks from your canvas selection with templates for Task, Feedback, Review, Content and Polish, rich-text notes with @mentions, a screenshot attached on create, and the published design URL filled in automatically. It also has Tasks and Mine tabs so you can filter and action work without opening the portal.

How do the extensions authenticate?

All three use a personal access token from Settings → API keys — create one, paste it once, and the extension remembers your workspace and last project. That is separate from MCP, which uses OAuth and is aimed at AI hosts rather than editors.

What is the difference between the extensions and MCP?

The extensions are for you: create and triage work from the tool you have open. MCP is for an AI host acting on your behalf — it exposes 31 tools and runs under the permissions of whoever authorised it. Plenty of teams use both.

Do you support JetBrains, Neovim, or Webflow?

Not yet. Webflow is scoped as a thin form and CMS bridge into tasks, but it is not built — there is no plugin to install today. JetBrains, Neovim, and browser-only IDEs have no dedicated extension planned; use MCP or the REST API there. If either would change your decision, tell us, because that is what moves the order.

MCP support meant our own internal tools could talk to Worksynk on day one. No integration project required.
Devon Ariza / Staff Engineer, Cascade Robotics
[ Keep exploring ]

Where to go next.

/ Get started

Stop finding out about risk in the retro.

Score every project and catch scope creep early, without another status meeting.

Start free
Book a walkthrough
Free, full platform
90 days
Nothing up front
No card
Guided walkthrough
20 min