Skip to content

Point at any dev site, prompt your agent.

Tencil runs in the browser, on top of whatever renders the page. For Rails, Laravel, Django, Phoenix, a static site or anything else, one script tag in your development HTML is the whole integration.

npx tencil

  • layout.html

    <script src="http://localhost:4747/tencil.js" async></script>

    One script tag

    Load the overlay from the daemon on your machine, in development only. npx tencil prints the tag when it finds neither Next.js nor Vite.

  • Nothing without the daemon

    The script comes from localhost. For anyone without the daemon running, it does not load and nothing appears. Keep it in your development layout anyway, so production pages never ask for it.

  • What the agent gets

    On any page, your agent gets your prompt, the page, the markup of what you clicked, a selector, its visible text, its size and position, and a screenshot if you attach one. It then searches your repository for the template that renders it.

  • Found from the port

    The daemon matches the page to its project through the port your dev server listens on. Behind Docker or a proxy, the overlay asks once which project the page belongs to and remembers your answer.

Frequently asked questions

Using Tencil with Any dev server.

Not by itself: the component and source file come from React. On other stacks the agent gets the markup, selector and text, which is usually enough for it to find the template.

Yes. The overlay sits on top of the rendered page, so it does not matter what rendered it. Your agent edits the template in your repository.

Yes: start the daemon with --port, or set TENCIL_PORT, and load the script from that port.

All questions

More integrations

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