# Get LinkedIn sales with Claude Code
> Use Claude Code as a terminal operator on Omentir. Diff My Product against the repo. Draft in the session. Send from the workspace. Close the terminal and the job stops.
- HTML: https://omentir.com/use-cases/claude-code-outbound
- Markdown: https://omentir.com/use-cases/claude-code-outbound.md

**Verdict:** Claude Code is useful when the product already lives in a terminal. It is a bad LinkedIn client. Put LinkedIn in Omentir. Put the key in the environment Claude Code already uses for secrets.

Claude Code checks the repo. Omentir sends. You still take the meeting.

## Highlights

- Repo session, not overnight
- API key, not a chat connector
- Review list, then send

## First weeks

1. **Finish Omentir, then open the repo.** LinkedIn connected, My Product written in two sentences a stranger would understand. If the brief is a slogan, the session will invent pain.
2. **Connect with a Bearer key.** Point Claude Code at https://omentir.com/api/agent/v1/mcp. This is not Claude chat. Chat uses Settings, Connectors, and workspace approval. Mixing those paths is how people wait for an OAuth screen that never appears.
3. **Diff the story, then a scored list.** Compare My Product with the README. Fetch agents.md. get_context, then list_agents. If you want a new finder, show the config and wait. Pull up to 30 people with drafts. Do not send.
4. **Send from Omentir, own the inbox.** Cut junk. Start a small campaign. The first real reply is still yours. Close the terminal and the job stops.

## Why the repo session matters

Most outbound junk starts as a homepage paragraph pasted into a chat that has never seen the product. Claude Code is useful when the claim on the site and the claim in Omentir can be diffed in one place.

Creating an agent should be a named request, the same way merging a pull request is a named request. A refactor that also spins up a finder is how targeting drifts.

## Paste this into Claude Code

Finish Omentir first. Put the key in the environment. Fetch agents.md. Replace the brackets. Keep the last two sentences.

```
You are the sales outreach operator for my company. You work from this repo through Omentir.

My product helps [buyer] get [result]. Best-fit accounts are [company type, size, region]. Strong signals: [signal]. Skip [bad fit].

Work only through Omentir MCP or REST. Read https://omentir.com/agents.md if you have not. Start with get_context, then list_agents. If no finder matches this ICP, show me a create_agent config and wait for a yes.

Pull up to 30 people. For each one write fit 1-5, the evidence, any risk, and a two-sentence draft that cites a real trigger. If a note could fit two buyers, rewrite it.

Do not send. Do not enroll. Do not sign into LinkedIn.
Do not create, delete, or reply unless I ask in this session.
```

## Related

- [Claude Code integration](https://omentir.com/integrations/claude-code.md): API key, MCP URL, and the chat versus terminal split.
- [Claude Code for LinkedIn outreach](https://omentir.com/blogs/claude-code-linkedin-outreach.md): Longer walkthrough of the repo job.
- [How do I connect Claude Code to Omentir?](https://omentir.com/help/how-do-i-connect-claude-code-to-omentir.md): Short help version of setup.

## Frequently asked questions

**Does Claude Code keep working after I close the terminal?**

No. That is Grok Bot. Claude Code is a session in the repo.

**Is this the same as Claude on claude.com?**

No. Chat Claude uses workspace approval. Claude Code uses a revocable key.

**Should I pick Cursor instead?**

Pick the window you already live in. Cursor is the editor. Claude Code is the terminal.

## Connect Claude Code only if the terminal is already open

If you are not in a repo, start in Overview.

[Create an Omentir account](https://omentir.com/signup). Pro is $49/month.