Part 3 · Operate
The browser companion
It watches your LinkedIn outreach and captures what you mark. It never acts.
01What it is
A Chrome extension that records what you did on LinkedIn so accepted connections do not go quiet, and captures messages you deliberately select in any community you are in.
02Why it exists
Fifty connection requests become fifty tracked conversations rather than fifty silent ones. Nobody follows up by hand at that volume, and the follow-up is where the conversations come from.
What it will never do is act inside your session. Tools that click and type on your behalf hand you the ban risk on an account you cannot replace. That is a legal position, and it is asserted against the built bundle rather than promised in a readme.
03How to use it
- 01Install it and connect it from the panel.
- 02Use LinkedIn normally. It records what happened.
- 03To keep a message from a community, select it and press the shortcut, or use the button that appears.
- 04Read the confirmation. It quotes back exactly what left the page, with an undo.
04What good looks like
- You give it
- A connection request sent, accepted three days later.
- You get
- The acceptance is recorded and the first touch is queued with a due date.
- Why
- A pending request becoming a connection is the moment a cold contact becomes warm.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- Expecting it to send the connection requests.
- You get
- Nothing sends. It has no capability to click or type.
- Why
- The bundle test fails the build on any synthetic event dispatch, and the manifest asks for no permission that would allow one.
Derived from the rules in the code