spyden
Spyden is an office helper. You describe a task in email or on this website. Spyden does the work, then emails you the result. It never starts a task until you type a confirmation code (like a banking OTP).
On this page
There are three kinds of job. Pick the one that matches the request. If you are unsure, use a code job for “please change our app/website”, and a research job for “please look this up on the internet”.
Use this when someone wants Spyden to edit software in a folder that the office has already approved (called a root or project name, for example beit_bid). You write the request in plain English. After you confirm, Spyden’s coding assistant works in that folder and emails a short summary of what changed.
On the website: choose job type code, pick the project from the Root dropdown, and type the prompt. By email: subject line starts with JOB, and the body includes root: and prompt:.
Use this when you need a summary from public websites (tenders, release notes, documentation). Spyden searches, opens pages, and writes a summary with source links. It does not change any office software.
On the website: choose job type research, type the question, and optionally paste extra website addresses. By email: subject starts with RESEARCH (or the older word SCRAPE), plus a prompt:.
Use this when someone supplies a short Python snippet (totals, a list, a conversion) and you only need the printed result. After confirmation, Spyden runs that snippet in a locked-down folder. It does not receive mailbox passwords or API keys.
On the website: write the request in Instructions and paste the Python under optional extras. Spyden infers a script job when a script is supplied. By email: subject starts with JOB and the body has a script: block. A project root is optional for script-only mail.
Both paths create the same kind of job. You can start on the website and confirm from email, or start by email and watch progress on the website.
JOB, RESEARCH, or CONFIRM.Step-by-step examples (copy-and-paste mail, and website clicks) are on How to use Spyden.
When you create a job, Spyden emails a one-time code (usually six digits) to the office’s OTP mailbox. The job sits at waiting for confirmation until that code is used. The code expires after a few minutes (often ten) and can be used only once.
You can confirm in any of these ways:
CONFIRM plus the job id, and the digits in the body.The Jobs table and each job page show a status. In everyday language:
pending_otp — created, waiting for the confirmation code. Nothing has run yet.queued — confirmed, waiting for a free worker. Spyden only runs a few jobs at once.running — Spyden is working now. Progress bars show stages: confirm → look up past work → do the task → tidy the answer → send mail.needs_input — the agent emailed a question. Reply with a new JOB in the same thread (still needs OTP).done — finished. You should have a completion email. The page shows the summary.failed — something went wrong. You should have a failure email. The page shows the error.If two jobs are already running, a third confirmed job waits in the queue. That is normal. Refresh the job page after a short while.
If you want Spyden to continue the same conversation (“same as last time, now wrap the table”), start a new job and point it at the previous job id. That is a thread. Spyden will re-read the earlier messages, not only a short search snippet.
On the website, put the previous job id in Continue thread on the new-job form. By email, add a line thread: job-… (or job: without a code). Replying to a Spyden mail that contains the job id can also attach the thread.
You may attach files to a JOB email (spreadsheets, PDFs, images, notes). Spyden keeps a copy with the job (a small number of files, each under a size cap). Text from those files is included when the coding assistant runs.
When the written answer is long, Spyden may attach a PDF to the completion email. The same files appear on the job page for download after you log in.
Finished jobs are filed so later requests can stay consistent. Spyden stores a notes file per job, a search index, and simple labels (project name, tender numbers, places). The next similar question can pull in a short excerpt from earlier work.
A thread (above) is stronger than that search: it pastes the actual previous back-and-forth into the new job, with a length cap so the message does not grow forever.
thread:.If the subject includes [degraded], Spyden used a backup local model because the usual remote assistant was busy or unavailable. Treat the answer as a draft and ask a technical colleague if the change looks risky. Code jobs that fall back this way are marked failed and should not be treated as live website edits.
Your username is created on the server (there is no default admin password). Log in at Log in. Settings (mailbox, allowed email senders, API keys) are on Settings. Those values live in the office database and apply on the next mail check — no restart. Passwords and keys are never shown after you save them.
Only email addresses on the operators list may send JOB / RESEARCH / CONFIRM mail. If a message is ignored, the From address is probably not on that list.
Ready to try it? Open How to use Spyden for click-by-click website steps and copy-and-paste email examples.