back
loading skill details...
Tinder dating assistant - swipe with filters (age/distance), conversation manager with smart replies, follow-up messaging. Use when user wants help managing...
---
name: dating-pilot
description: Tinder dating assistant - swipe with filters (age/distance), conversation manager with smart replies, follow-up messaging. Use when user wants help managing their Tinder profile and conversations.
metadata: {"openclaw":{"emoji":"💘","homepage":"https://www.npmjs.com/package/tinder-automation","requires":{"bins":["dating-pilot"]},"install":[{"id":"npm","kind":"node","package":"tinder-automation","bins":["dating-pilot"],"label":"Install dating-pilot (npm)"}]}}
---
# dating-pilot
Tinder dating assistant CLI with smart profile filtering and conversation management. All commands output JSON.
## Feature Overview
- **Smart Filtering**: Browse and like profiles by age and distance preferences
- **Conversation Manager**: Manage messages, draft smart replies, send follow-ups
- **Status Monitoring**: Query chat system status and recent activity summary
- **Photo Diagnosis**: Analyze profile photos against dating best practices and get per-photo scores with improvement suggestions
## Security & Privacy
**Source**: Published on [npm](https://www.npmjs.com/package/tinder-automation). The source code will be open-sourced on GitHub in a future release.
**Authentication**: This tool does **not** collect, store, or transmit any Tinder account credentials. It operates through Playwright on a browser session where the user has already logged into Tinder. No passwords or auth tokens are extracted from the browser.
**Data Flow**: Conversation data is sent **only** to the AI endpoint configured by the user (e.g., Claude API). The tool does not relay, collect, or forward any data to third-party servers. All API calls are made directly from the user's machine.
**Local Storage**: Configuration (including AI API key) is stored locally in `~/.dating-pilot/` on the user's machine. No data is transmitted to any remote server operated by this tool's author.
**No Telemetry**: There is no telemetry, analytics, crash reporting, or log uploading of any kind. The tool operates entirely offline except for direct calls to Tinder (via browser) and the user-configured AI endpoint.
**API Key Best Practices**: The AI API key is provided by the user and used solely for calling the user-specified AI service. It is recommended to use a dedicated, permission-scoped API key rather than a master key.
## Getting Started
Before use, configure AI parameters (only Anthropic-format APIs are supported, e.g., Claude API or compatible proxy services). Tinder must already be logged in via your browser — this tool uses that existing browser session and never asks for your Tinder credentials.
```bash
# Required: Configure AI
dating-pilot config --ai-base-url <url> --ai-api-key <key> --ai-model claude-sonnet-4-6
# Optional: Set a network proxy (for regions where Tinder access requires a proxy) and matching location preferences
dating-pilot config --proxy <proxy-url> --latitude 32.06 --longitude 118.79 --timezone Asia/Shanghai
```
## Command Reference
### Global Options
- `--help` — Show help information
### config — Configure AI, proxy, and location
```bash
# Set AI configuration (only Anthropic-format APIs supported)
dating-pilot config --ai-base-url <url> --ai-api-key <key> --ai-model <model>
# Set network proxy (for regions where Tinder access requires a proxy)
dating-pilot config --proxy <proxy-url>
# Set match location preferences
dating-pilot config --latitude 32.06 --longitude 118.79 --timezone Asia/Shanghai
# Can be combined
dating-pilot config --ai-base-url <url> --ai-api-key <key> --proxy <proxy-url>
# View current configuration
dating-pilot config --show
```
| Parameter | Required | Description |
|------|------|------|
| `--ai-base-url` | Required on first use | AI API endpoint (Anthropic format) |
| `--ai-api-key` | Required on first use | AI API key |
| `--ai-model` | No | AI model name (e.g., `claude-sonnet-4-6`) |
| `--proxy` | No | Network proxy for regions where Tinder requires one (e.g., `socks5://host:port`) |
| `--latitude` | No | Latitude for match location preference |
| `--longitude` | No | Longitude for match location preference |
| `--timezone` | No | Timezone for match location preference (e.g., `Asia/Shanghai`) |
| `--show` | No | Show current configuration |
### swipe — Batch swipe with filters
```bash
dating-pilot swipe --like-count <N> [--min-age <N>] [--max-age <N>] [--max-distance <N>]
```
| Parameter | Required | Description |
|------|------|------|
| `--like-count` | Yes | Target number of likes |
| `--min-age` | No | Minimum age |
| `--max-age` | No | Maximum age |
| `--max-distance` | No | Maximum distance (km) |
Output example:
```json
{
"success": true,
"message": "Filtered swipe complete: liked 10, skipped 5, matched 2",
"data": {
"likedCount": 10,
"skippedCount": 5,
"matchedCount": 2
}
}
```
### chat start — Start conversation manager
**⚠️ Long-running task**: Once started, the conversation manager runs in the background. Use `exec background:true` to invoke.
Automatically checks configuration and launches the browser on startup (no manual launch needed). Use `chat stop` at any time to terminate the manager and release all resources.
```bash
dating-pilot chat start [--max-chats <N>] [--user-preferences "<preferences>"]
```
| Parameter | Required | Description |
|------|------|------|
| `--max-chats` | No | Maximum number of chats to handle at once (default: all). Use a small number (e.g., 3-5) to start. |
| `--user-preferences` | No | User preferences (injected into AI personality, e.g., "girls who like sports") |
### chat stop — Stop conversation manager
```bash
dating-pilot chat stop
```
Stops the conversation manager and releases resources.
### chat status — Query chat status
```bash
dating-pilot chat status [--since <minutes>]
```
| Parameter | Required | Description |
|------|------|------|
| `--since` | No | Query activity summary for the last N minutes |
Output example (with `--since 30`):
```json
{
"success": true,
"data": {
"initialized": true,
"browserId": "tinder",
"recentActivity": {
"since": "2026-03-11T10:00:00.000Z",
"newMessagesReceived": 5,
"aiRepliesSent": 3,
"activeChats": [
{
"sessionId": "abc123",
"userName": "Alice",
"lastMessage": "Haha okay, see you this weekend!",
"lastMessageTime": "2026-03-11T10:25:00.000Z",
"direction": "in"
}
]
}
}
}
```
### chat proactive — Send follow-up messages
```bash
dating-pilot chat proactive
```
Analyzes conversations and sends follow-up messages to active matches. This runs autonomously once triggered, sending messages to matches that haven't responded. The scope is limited by the `--max-chats` value set in `chat start`. Requires the conversation manager to be initialized. Use `chat stop` to terminate at any time.
### open — Open a specific user's chat
```bash
dating-pilot open --user "<username>"
```
### send — Send a message
```bash
dating-pilot send --message "<message content>" [--user "<username>"]
```
If `--user` is specified, it will first open that user's chat before sending.
### diagnose — Analyze profile photos
Analyzes your Tinder profile photos against dating photo best practices using Vision API. Automatically launches the browser and fetches your latest profile photos from Tinder — no need to run `chat start` first.
```bash
dating-pilot diagnose
```
Output example:
```json
{
"success": true,
"message": "Photo diagnosis complete. Overall score: 7/10",
"data": {
"overallScore": 7,
"photoCount": 4,
"summary": "Strong first photo with clear face. Missing action and animal photos.",
"photos": [
{
"index": 0,
"score": 8,
"detectedCategory": "portrait",
"strengths": ["Clear face", "Good lighting"],
"suggestions": ["Try a more natural setting"],
"ruleViolations": []
}
],
"combinationAdvice": {
"coveredCategories": ["portrait", "travel"],
"missingCategories": ["action", "funny", "animal"],
"duplicateTypes": [],
"suggestions": ["Add an action shot showing a hobby", "Include a photo with a pet"]
}
}
}
```
## Typical Workflow
```bash
# 0. First use: Configure AI (only Anthropic-format APIs supported)
dating-pilot config --ai-base-url http://your-api.com/claude --ai-api-key sk-xxx --ai-model claude-sonnet-4-6
# 1. Diagnose profile photos (can run independently, no chat start needed)
dating-pilot diagnose
# 2. Filtered swipe: Like 10 users aged 22-28 within 30km
dating-pilot swipe --like-count 10 --min-age 22 --max-age 28 --max-distance 30
# 3. Start conversation manager (long-running task, runs in background, auto-launches browser)
dating-pilot chat start --user-preferences "Goal: serious relationship, Style: casual and humorous"
# 4. Check chat status
dating-pilot chat status --since 30
# 5. Trigger proactive chat
dating-pilot chat proactive
# 6. Stop chat
dating-pilot chat stop
```
## Heartbeat Monitoring
Used together with HEARTBEAT.md. The Agent periodically calls `dating-pilot chat status --since 30` to get recent activity:
- **Activity detected**: Summarize new message count, AI reply count, and active chat list, then report to user
- **No activity**: Return `HEARTBEAT_OK`
Recommended heartbeat interval: `heartbeat.every: "30m"`
## Notes
1. **Configuration required before first use** — Run `dating-pilot config` to set AI parameters before using `chat start`
2. **Smart replies only support Anthropic-format APIs** — e.g., Claude API or compatible proxy services
3. **chat start is a long-running task** — Use `exec background:true` to run in the background, otherwise it will block the Agent
4. **chat start auto-launches the browser** — No manual launch needed, but Tinder must already be logged in via the browser
5. **Conflict detection** — While conversation manager is running, commands that operate the browser (swipe/open/send) will be rejected; run `chat stop` first
6. **Like limit** — Free users have a daily like limit; operate in batches (10-20 per batch)
7. **Data stays local** — All configuration and conversation data remain on your machine. No data is sent anywhere except to Tinder (via browser) and your configured AI endpoint
8. **Use a dedicated API key** — For safety, use a separate, permission-scoped API key rather than your primary key
9. **Start small with proactive messaging** — Use `--max-chats` with a small number first to review AI message quality before scaling up
don't have the plugin yet? install it then click "run inline in claude" again.