Skip to content

Point at UI elements for your coding agent.

Telling an agent which button you mean takes a paragraph. Pointing at it takes a click. Press C on your dev site, click the element and type what should change: Tencil hands your agent what you pointed at, and your dev server reloads the result.

npx tencil

  • Point instead of describe

    "The second card’s button on the pricing page, the one under the toggle" becomes a click. The agent gets the element’s component and owners with file and line in React 19, its markup, a selector, its text, its size and your viewport.

  • Prompt where you point

    The prompt box opens on the element. Select part of its text to say exactly which words you mean, and attach a screenshot when a picture says it faster.

  • With the agent you already use

    Tencil does not run a model of its own. It starts a thread in Claude Code or T3 Code, under your own login, and streams its progress onto a pin on the element.

  • One at a time, or a whole review

    Send a pin straight away, or switch to batch mode, leave comments on several elements and send them to your agent as one thread, numbered like their pins.

Frequently asked questions

What to know before you start.

No. npx tencil sets it up in your project, and the daemon runs on your machine. Tencil is free and open source under Apache-2.0.

Any. Tencil lives in your browser and talks to your agent, Claude Code or T3 Code, so you keep whatever editor you have open.

Next.js, any Vite app and, with a script tag, any dev server. Source files and line numbers come from React; other frameworks get the markup, selector and text.

All questions

More use cases

Tencil works the same everywhere: point at an element, say what should change.