Use Dagweave Local with the Dagweave app

StarterProBusiness

Dagweave Local is free. On a Starter plan or above you can also sign your laptop in to the Dagweave app. Its runs then show up in the Runs panel with their step logs, and you can start runs on it from the editor.

dagweave login

It prints a link and a code, and opens the link in your browser if it can:

Open https://app.dagweave.com/device and enter BCDF-GHJK
Waiting for you to approve this machine in the browser...

On that page, click Approve only if you ran dagweave login yourself and the code matches your terminal. Otherwise click Deny. The command then finishes on its own:

dagweave: signed in to https://app.dagweave.com as 9f2c41ab7de05c83
dagweave: runs on this machine now show up in the dagweave UI

The code expires after ten minutes. If it does, run dagweave login again.

The machine runs workflows as you, so your role has to allow running workflows.
If your team requires Google sign-in, you have to approve with Google. The page offers Sign out if you signed in another way.
If there’s no Dagweave account for your address, dagweave login says so and stops. The Dagweave app is in early access.
The machine joins the team you were working in, under its hostname. Signing in again reuses it. Leaving the team removes your machines from it.

To sign out, run dagweave logout.

Start runs from the editor

On your laptop, run:

dagweave listen

dagweave: connecting my-laptop to https://app.dagweave.com
dagweave: listening. Pick this machine under Run in the Dagweave app and the run happens here. Ctrl-C stops listening

In the editor, open the menu next to Run and pick your machine, such as On my-laptop. The workflow runs there as dagweave run would, and its output prints in the dagweave listen terminal. The run bar says Running on my-laptop. A machine that isn’t listening is greyed out and marked offline.

Where this runs also lists your machines, each with Run here.

Only you see your machines in the Run menu.
Triggers, webhooks, schedules and CronWorkflows can’t run on a machine. They need a cluster that’s always on.
Stop run stops a run on your machine while it’s listening. Only you can stop it, even if you’ve shared the run.
If the machine can’t run the workflow (see Unsupported workflows), the run fails and the reason goes back to the app.

Runs you start with dagweave run show up in the app whether or not you’re listening.

Your runs in the Runs panel

Every run on a signed-in machine shows up in the Runs panel, marked Local with the machine’s name. Nobody else can see them, not even owners and admins. To show one to your team, open it and click Share with team. Stop sharing makes it private again.

Step logs

Step logs stay on your machine. When you open a step, the app fetches them live. If the machine isn’t listening, you see:

This step's logs are on my-laptop, which isn't listening right now. Run dagweave listen there and they show up here.

Once you’ve deleted the run or rerun the workflow, its logs are gone.

Before a run goes to a cluster

A cluster pulls every image from a registry, so a workflow that works locally can fail there. If you have a machine connected, Dagweave checks image names before a cluster run and asks first if any look local:

Images from localhost, 127.0.0.1, host.docker.internal or a .local host, or tagged dev, local, test, wip or snapshot. Push them to a registry the cluster can reach.
Images tagged :latest or with no tag, which might be a different image on the cluster. Pin a version or digest.

If the images are in a registry the cluster can reach, click Run on cluster anyway. It won’t ask again for those images until you reload the page.

Manage your machines

Settings > Clusters > Your machines shows each machine’s state, version and when it was last seen. Offline means it isn’t listening.

Remove disconnects a machine without deleting anything on it. Run dagweave login to reconnect.

Owners and admins also see Everyone’s machines and can Revoke one straight away, though they can’t see its runs. The owner can reconnect with dagweave login while still in the team. Approvals, removals and revokes go in the team’s audit log.

Plans

Local runs don’t count toward your team’s monthly run allowance. Your plan sets how many machines each person can connect:

Plan	Machines per person
Starter	2
Pro	3
Business	5

At the limit, approving a new machine fails. Remove one under Your machines to make room. Signing in a machine again doesn’t count as a new one.

If your team moves to a plan without Dagweave Local connections, each machine keeps working for 14 days from the first time it connects after the change, then stops connecting. Your machines shows the date. See Plans and billing.