Review a feature in the browser.
Before a feature ships, you walk through it and note what to change. With Tencil those notes are pins on the elements themselves, and your agent works on them while you keep going.
npx tencilNotes on the element
A pin sits on the element it is about, not in a list somewhere else. Pins show their state: spinning while the agent works, blue when done, amber when it waits for approval, red on errors.
A review you can come back to
Pins are kept per project on your machine and come back after a reload. The inbox lists them, filtered by page, with resolved ones hidden until you ask for them.
Continue in your agent
Every pin is a thread in T3 Code or a Claude Code session, so a change that turns into real work moves into your agent with the whole conversation.
Frequently asked questions
What to know before you start.
No. They live in ~/.config/tencil/projects/, outside your code.
Not yet: Tencil runs on your machine, and pins stay there.
More use cases
Tencil works the same everywhere: point at an element, say what should change.
- UI polishSpacing, alignment, colors and states: click the element that looks off, say what should change and your coding agent edits the right component.
- Copy editsSelect the words on your running app, type the new ones and your coding agent edits the right string, component or translation file.
- Visual bugsOverflowing text, a broken layout at one width, a misaligned icon: pin the bug on the element and your coding agent gets the markup, size and viewport to fix it.