Browse guides
Set up Tawdheef with your agent
Start the app, copy the setup request into your agent, then choose companies and actions.
Content reviewed
On this page
Your existing Codex or Claude Code client owns the model, sign-in and external tools. Tawdheef keeps your companies, selected actions and recorded outcomes locally.
Install
These steps match the current Native source. The older v0.1.2 download uses a different connection flow.
Extract the source, install Node.js 26 LTS, then run in the app folder:
npm startThis starts the tracker, not job-search work. Verified platform packages include their runtime; check desktop release status before choosing one.
Connect your agent
- Open Connections → Assistant and choose Codex or Claude Code.
- Use Copy setup request and paste it into that client.
- Reuse existing tools and connections. Complete project/server trust, sign-in and consent in the client.
Set up Tawdheef in this local workspace using the Codex or Claude Code client I am using. Read AGENTS.md and docs/FIRST-RUN.md. Reuse working project settings and my actual client tools. Connect the local tracker MCP, then call get_agent_context, get_capabilities and get_native_readiness. Check the intended mailbox against the actual signed-in account, read my selected CV and identify a real upload file through your supported tools. Reuse the same working browser session and any supported password-manager access. Report only dated non-secret metadata, then check readiness again and guide only the missing step. Let me complete any required sign-in, trust, consent or unlock in the actual client. Do not copy credentials, browser profiles, vault contents or CV text into Tawdheef. Do not submit applications, create profiles, share a CV, send messages, change calendar events or create schedules during setup.
If you prefer the terminal
The copied request is the main path. Manual source connection:
npm run agent -- codexUse npm run agent -- claude-code instead for Claude Code. These configure tracker MCP and its skill, not provider authentication. Packages use their setup request's exact bundled-runtime paths.
Connect your CV
Open Connections → Tabbio CV. Create a CV if needed or reuse your account. Copy the request into your agent. It connects Tabbio and reads your real authorized CV through its own tools. Complete sign-in in the client, not a second tracker credential form.
Email, Calendar, Browser & computer use and Passwords have separate requests. Add only what you need. Unknown and Needs you are valid states; a dated Client reported observation is not independent proof of access.
Workflow
Review companies and jobs. Choose Run actions and targets, then paste its copied request into the selected client. It uses its own tools and records outcomes in Tawdheef. Applications, career profiles and optional CV-only emails are distinct choices.
Run does not launch another assistant. Stop revokes tracker authority; stop remaining work in the client too.
Use
Already connected? Install just the skill
npx skills@latest add ahmedaldhraif/tawdheef-auto-apply-jobs --skill tawdheefThis adds instructions only. It does not install the app, connect accounts or authorize applications.
Prompts
Read AGENTS.md and call get_agent_context and get_capabilities. Use my actual client's real CV and preferences to suggest a shortlist. Do not send or submit anything.
Permissions
Only your explicit selected Run actions authorize submissions. Sign-in, CAPTCHA and provider approvals may need you. LinkedIn actions remain manual. Record real receipts, not assumed success.
Privacy
Private tracking stays locally. External access stays in your actual client. Tawdheef stores references and dated observations, not copies of hidden client sessions or CV text. Keep credentials and private records out of GitHub.
See the actual app

GitHub issues are public. Leave out CVs, credentials and account details.