Carries out the work planned in the command center, from this browser and the accounts already signed in to it.
Checks in from this browser and has the console re-read every piston on the dashboard. Use it whenever the dashboard looks behind.
While this is on, the extension asks the console for one job at a time and does it here, with a long randomized gap in between. Turning it off stops everything immediately.
This is the part that actually posts, from your own accounts. It starts in dry run: it opens the network, fills in the composer, checks the text went in correctly, and stops without clicking post. Watch it do that a few times before you switch dry run off.
Reads your contracts from the Upwork account this browser is already signed in to, and keeps the Clients pipeline in step with them. It runs about every six hours, and running it twice changes nothing. Proposals are sent only after an admin approves them in Upwork → Proposals, and the daily round (searches, saved jobs, client replies) runs once a day.
Reads who reacted to and commented on your recent LinkedIn posts, and who viewed your profile, and sends them to Clients → Lead finder, where founders are graded and peers set aside. It reads only: it never reacts, comments, connects or messages. Slow on purpose: at most four posts, twice a day, profile viewers once a day, and it stops for a day at any sign of a LinkedIn limit.
Searches LinkedIn posts for what founders say about fundraising (the searches are set in the console, under Clients → Grading rules) and sends the authors to Clients → Lead finder. It reads only. Three searches, up to 15 posts each, twice a day; it stops for a day at any sign of a limit.
Reads job postings for the searches below and files them under Clients → Lead finder. A company advertising a role has already published the demand, the budget and the intent. It reads only: it applies to nothing and messages nobody. Runs once a day.
Sends the follow-up sequences written under Clients → Sequences, by Upwork or LinkedIn, from your own signed-in accounts. The console decides what is due and only hands one over when sending is armed, the sequence is running, and the company is still at that stage. Email follow-ups go from the console's own mailbox instead. Starts in dry run: it opens the conversation, types the message, and stops before Send.
Updates install themselves. About once an hour the extension asks the console for a newer version, and when there is one it downloads and installs it, with a progress bar at the top of this panel. Press Check Now to look right away.