Support — Rscot Agent

Email the maintainer

academic686@163.com

Best for licensing questions, security disclosures, or anything you'd rather not post publicly.

Response time: within 48 hours (US Eastern). Weekends and US holidays push the clock.

GitHub Issues

github.com/Gocodecc

Best for bug reports, feature requests, and install problems. Public and searchable — your issue helps the next person too.

Triage within 48 hours. Severity labels applied, milestone assigned.

Open an issue →

01Before you write

Skim the docs — most install, auth, and tool questions are answered there.
Search open issues to see if someone already reported it.
Confirm you can reproduce on the latest desktop build (currently v1.3.5) — older builds may have known bugs already fixed.
Include OS, build version, and the last 20 lines of the agent log in your report.

02Frequently asked

Why does the agent ask before every file write?

Every mutation goes through a diff-approval queue by design. Most coding agents auto-apply changes; Rscot Agent does not. This is the "no surprise writes" guarantee — you see the diff, you approve the diff, the file changes. Never the other way around.

Can I use my own API key?

Yes. Settings → Providers lets you bring your own key for any supported LLM provider or point at a local Ollama runtime. Your key, your bill, your rate limits — we never see it.

Does the desktop app upload my code?

No. The desktop shell runs the agent loop locally against a folder on your machine. Only the LLM calls leave your machine, and those go directly to whichever provider you chose — they do not pass through learningfind.com.

What is RSANC-1.0 and why not MIT?

Source-available so anyone can audit; non-commercial so we can fund development through paid commercial licenses while keeping individual and research use free. Read the full license on the docs page.

How do I get a commercial license?

Email academic686@163.com with subject [COMMERCIAL] your-company-name. We reply within 48 hours with a one-page term sheet. Pricing is per-seat for teams under 50, flat-rate above.

Is there a self-hosted backend option?

Yes. The backend is open in the same repository. Self-host playbook is in the docs. You'll need Docker, Postgres, and Redis — one box handles a small team comfortably.

03Security disclosures

Coordinated disclosure

For security issues, please email academic686@163.com with subject [SECURITY] short-summary. Do NOT file a public GitHub issue for security reports.

We acknowledge within 48 hours, ship a fix in the next minor release, and credit you in the changelog (unless you prefer to stay anonymous). PGP key fingerprint below — full key on request.