Local action layer for agent builders
Combine actions into governed workflows.
Turn isolated account tasks into inspectable loops: discover, enrich, plan, ask for approval, execute approved steps, and write outcomes to local history. Agents get tools; humans keep control.
- Validated registry
- 256 local actions · 10 MCP tools
- Read-only surface
- 162 safer discovery actions
- Risk-gated surface
- 94 mutations require explicit approval
- Action categories
- 12 jobs, feed, profile, network, messaging, more
- 134 read-only
- 7 low
- 12 medium
- 18 high
- 29 unsafe
What you can build by combining actions
The leverage is composition. A buyer can combine read-only discovery, profile/job/feed/message primitives, MCP calls, approval gates, and local run history into internal workflows instead of handing an agent uncontrolled browser access.
-
Recruiter loop with local memory
Source candidates, enrich profile facts, draft an outreach plan, pause for human review, execute only approved items, and write outcomes to a local CRM file so candidates move through a visible pipeline.
-
Agent tool surface with brakes
Let an agent list actions, inspect required inputs, run read-only steps, and stop when confirmation is required. The MCP layer gives a compact 10-tool interface instead of hundreds of exposed primitives.
-
Account operations review
Use read-only actions across jobs, feed, profile, network, settings, notifications, and organization surfaces to create internal review queues before any externally visible action happens.
-
Workflow prototype faster than from scratch
Start from a registry, CLI runner, MCP server, recruiter workflow, redacted logs, and local CRM shape instead of building every control surface yourself.
What ships in the handoff
Everything ships under a perpetual source licence: the working code, the demo data, the docs, and the limitations notes. Read it, modify it, run it on your own machines. One price, no subscription, no seats, no hosted dependency. The licence covers your own business use — it does not permit reselling or hosting the code for others.
included
- cliActions/ local action runner and registry
- MCP stdio server with 10 registered tools
- cliDiagnosis/ capture and HAR-import tooling (27 actions)
- Recruiter workflow prototype and local CRM file shape
components
- CLI action layer
- Manual login, session status, action list/show/run, smoke checks, run history, license status, doctor output, and redacted local run logs.
- Agent interface
- A compact MCP server exposes listing, description, execution, run history, license status, and recruiter workflow tools instead of hundreds of one-off tools.
How intent becomes output
The operator path, start to finish. Each step is a real command surface, not a promise.
- 01
Discover
List the available local actions, inspect categories, and keep read-only discovery separate from mutating execution.
- 02
Plan
Use the recruiter prototype to source, enrich, plan outreach, and write a local CRM record before execution.
- 03
Approve
Low, medium, high, and unsafe actions require confirmation; unsafe actions also require force.
- 04
Audit
Redaction is the default, not an option: results are scrubbed before anything touches disk, and only explicitly whitelisted fields on read-only actions are ever exposed. MCP responses are trimmed; the full redacted record stays local.
What's proven, what's excluded
The same diligence a technical buyer would run: what the code demonstrates locally, and what is deliberately left out of a clean handoff.
✓ proven
-
Registry validated
The shipped validator statically checks all 256 actions: unique IDs, and every declared input is provably consumed by its runner — the action interface can’t lie about what it needs.
-
Checks pass locally
Clone it and run one command: npm run check validates all 256 actions plus the 27-action diagnosis registry, and passes 12 selftests — errors, pacing, runner, network, notifications, organization, feed, profile, resolve, Easy Apply streaming, jobs, and redaction — reproducible on your machine, not just ours.
-
Risk posture is explicit
The code has confirm/force gates on every mutating action; marketing copy avoids promises about safety, compliance, production rate limits, or live freshness.
! excluded
-
Not a hosted service
No hosted SaaS, cloud billing, packaged installer, Stripe integration, marketplace listing, customers, or revenue are included.
-
Platform risk is real
Automating a professional network can violate the platform’s user agreement and risks account restriction, even run locally on your own session. Get counsel-reviewed terms and user warnings in place before any commercial launch.
-
Live proof needs refresh
Live behavior depends on account state, UI/API changes, permissions, locale, and rate limits.
-
Buyer controls use
Commercial launch should add counsel-reviewed terms, warnings, data disclosures, behavior safeguards, and fresh live testing.
-
What the licence grants
A perpetual, non-transferable licence for one business to run and modify the source internally — no seats, no subscription. It does not transfer ownership of the code, and it does not permit reselling, redistributing, hosting it as a service or API, or white-labelling it. The delivered LICENSE.md governs.
Build it yourself, or start from the source
Request handoff
Give agents useful actions without giving up control.
Request the handoff to review the registry, MCP surface, support window, and commercial-use boundaries before transfer.
Request handoffOpens your mail client. If it doesn't, write to [email protected] and mention the professional-network workflow kit.