Install support

Bring Bardeen into a controlled agent workspace

This page is a practical starting point, not a sales form. Review the operating notes, prepare a test environment, and use the exact command when you are ready.

Prepare the runtime

Choose an AI agent environment where package execution, tool permissions, and logs are visible. Begin outside production. Confirm that you can inspect added files and reverse the installation according to the runtime's package guidance.

Scope connections

Decide which research or enrichment capability the first task needs. Store API keys in the runtime's secret manager, grant minimal access, and avoid enabling CRM writes or outreach actions during the initial verification.

Define success

Use a narrow ICP and a short result set. Check qualification evidence, contact status, unresolved fields, and provenance. Treat coverage, match rate, latency, and bounce outcomes as measurements from your environment rather than assumed guarantees.

Terminal and agent workspace prepared for a controlled Bardeen installation

Before the first run

Keep outreach sending disabled until a person approves the target and message.
Confirm provider terms and applicable regional privacy or anti-spam obligations.
Do not paste secrets into prompts, result exports, or shared logs.
Record how to rotate credentials, update the package, and uninstall the skill.

Copy the installer when your workspace is ready

The button copies the command only. Run it yourself, inspect the output, configure approved tools, and verify a small first result.

Write down the expected output schema and the person responsible for review. If the task discovers accounts, define what qualifies and what must be excluded. If it enriches contacts, decide which verification states are acceptable. If it drafts copy, identify who can approve content and keep the actual send action outside the test. Compare the result with the original brief instead of judging success by list size alone.

npx -y @okki-global/okki-go-taroball