Weavin

Code Agent

Hand your avatar a coding job the way you'd hand it anything else — in a sentence.

Starting a coding job

In chat, describe what you want built or fixed — or switch the composer into Code mode. The job becomes a project with its own tab in the Workbench.

Watching it work

The project tab is a stage, not a log file:

  • In progress — see activity as it works, with a live sense of where it is
  • It has a question — when it needs a decision from you, the stage turns into the question; answer and it continues. Questions left too long expire safely rather than guessing.
  • Done — what changed, summarized, with the changed-file count and the results in hand

Whose account it runs on

Coding jobs can run on Weavin's side (drawing on your plan's credits) or on your own key — your choice, switchable per job. There are two coding backends available; pick per project, or let the default carry you.

What you get

Results land where you can use them: files produced by the job are saved to your Library, and the project tab keeps the record of what was done. If your code host is connected, repository work — browsing, changes, pull requests — happens against your real repositories, with the same approval rules as everything else.

What's Next?