[Question]: env file

[wbuttigieg007]

What happened?

Do I need to edit any of the parameters of the .env file as there was not instructions on that?

APP_ENV=development
LLM_PROVIDER=ollama
DATABASE_PATH=data/jobs.db
OLLAMA_BASE_URL=http://localhost:11434
OPENAI_BASE_URL=https://api.openai.com/v1
OPENAI_API_KEY=your_openai_api_key_here
MODEL_NAME=qwen3-coder:latest
SMTP_HOST=your_smtp_host_here
SMTP_PORT=587
SMTP_USERNAME=your_email@example.com
SMTP_PASSWORD=your_smtp_password_here
SMTP_CC_EMAIL=your_cc_email@example.com
IMAP_HOST=imap.gmail.com
IMAP_PORT=993
IMAP_USERNAME=your_email@example.com
IMAP_PASSWORD=your_imap_password_here
JOB_APPLICATION_EMAIL=your_job_application_email@example.com
JOB_PORTAL_ACCOUNT_EMAIL=your_job_portal_email@example.com
JOB_PORTAL_ACCOUNT_PASSWORD=your_job_portal_password_here
US_WORK_AUTHORIZED=Yes
REQUIRES_SPONSORSHIP=
GOOD_JOB_EMAIL_THRESHOLD=0.82
CAREER_SITE_COOLDOWN_DAYS=0
CAREER_DISCOVERY_CACHE_DAYS=14
COMPANY_DAILY_TARGET_COUNT=200
OPENCLAW_GATEWAY_CMD=C:\Users\YourName.openclaw\gateway.cmd
OPENCLAW_UPLOAD_DIR=C:\tmp\openclaw\uploads
AUTO_APPLY_ENABLED=true
AUTO_APPLY_MIN_SCORE=0.75
AUTO_APPLY_MAX_PER_CYCLE=5

What did you expect to happen?

do parameters need to be edited?

Steps to reproduce

Which ATS / posting URL?

No response

Logs / error output

Instaply version

latest

Operating system

Windows

Python version

3.13 (64bit)

LLM provider you're using

Not sure / not relevant

[Aditya-00a]

Hey! Good question — no, you don't need to edit .env by hand. That file is a template. The setup wizard writes the real one for you:

cd Instaply/agent
python setup.py # picks LLM + writes config/.env
python setup.py profile --resume /path/to/cv.pdf # writes profile.json
python setup.py doctor # sanity check
python run.py
If you'd rather set it manually, here's what each block does:

Required

LLM_PROVIDER, MODEL_NAME, OLLAMA_BASE_URL — setup.py sets these based on your hardware. Defaults are fine.
DATABASE_PATH=data/jobs.db — leave as-is.
Optional (safe to leave as placeholders)

SMTP_* / IMAP_* / JOB_APPLICATION_EMAIL — only for mail-confirming that ATS received your application. App runs fine without them. For Gmail use an App Password, not your login.
JOB_PORTAL_ACCOUNT_* — only for ATSes that force a login (rare).
OPENCLAW_* — only if you have OpenClaw installed. Otherwise never touched.
OPENAI_* — only if you switch LLM_PROVIDER to openai. Ignored with Ollama.
CAPTCHA_SOLVER=none — leave as none unless you're bringing a 2captcha/CapSolver key.
Tuning knobs (defaults are sensible)

AUTO_APPLY_ENABLED, AUTO_APPLY_MIN_SCORE, AUTO_APPLY_MAX_PER_CYCLE
US_WORK_AUTHORIZED / REQUIRES_SPONSORSHIP — the profile wizard writes these into data/profile.json anyway; the .env values are just a fallback.
One heads-up on Python 3.13 — the QUICKSTART says "3.10+" but I'd recommend 3.12 for now. 3.13/3.14 have caused interpreter-level crashes in the Playwright + async loop. If doctor passes but run.py crashes, drop to 3.12.

I'll add a note to .env.example clarifying this so it's obvious next time. Thanks for flagging!

[wbuttigieg007]

Thanks for checking! I will try it out. Have not been successful On Jul 24, 2026, at 6:44 PM, Aditya Sakhale ***@***.***> wrote:Aditya-00a left a comment (Aditya-00a/Instaply#14) Hey! Good question — no, you don't need to edit .env by hand. That file is a template. The setup wizard writes the real one for you: cd Instaply/agent python setup.py # picks LLM + writes config/.env python setup.py profile --resume /path/to/cv.pdf # writes profile.json python setup.py doctor # sanity check python run.py If you'd rather set it manually, here's what each block does: Required LLM_PROVIDER, MODEL_NAME, OLLAMA_BASE_URL — setup.py sets these based on your hardware. Defaults are fine. DATABASE_PATH=data/jobs.db — leave as-is. Optional (safe to leave as placeholders) SMTP_* / IMAP_* / JOB_APPLICATION_EMAIL — only for mail-confirming that ATS received your application. App runs fine without them. For Gmail use an App Password, not your login. JOB_PORTAL_ACCOUNT_* — only for ATSes that force a login (rare). OPENCLAW_* — only if you have OpenClaw installed. Otherwise never touched. OPENAI_* — only if you switch LLM_PROVIDER to openai. Ignored with Ollama. CAPTCHA_SOLVER=none — leave as none unless you're bringing a 2captcha/CapSolver key. Tuning knobs (defaults are sensible) AUTO_APPLY_ENABLED, AUTO_APPLY_MIN_SCORE, AUTO_APPLY_MAX_PER_CYCLE US_WORK_AUTHORIZED / REQUIRES_SPONSORSHIP — the profile wizard writes these into data/profile.json anyway; the .env values are just a fallback. One heads-up on Python 3.13 — the QUICKSTART says "3.10+" but I'd recommend 3.12 for now. 3.13/3.14 have caused interpreter-level crashes in the Playwright + async loop. If doctor passes but run.py crashes, drop to 3.12. I'll add a note to .env.example clarifying this so it's obvious next time. Thanks for flagging! —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[Aditya-00a]

I would suggest drive it with codex or claude code and give them directions for changes. That would be the most optimal way for implementing this into workflow.