A private local queue
Prepare jobs in a local SQLite database without requiring a hosted account.
Controlled AI work queueWindows release candidate
Easy Weekly
Queue the work. Choose when it runs.
Keep local AI jobs in a private queue and deliberately run one selected job at a time.
Ask about Easy WeeklyWhat it is for
Easy Weekly separates collecting work from running it. Jobs wait in a local SQLite queue until you select one to execute through the configured EasyRoute gateway.
This is a straightforward workflow for people who want to prepare tasks, inspect what is waiting and stay in control of execution. A failed job requires a manual retry, giving the owner an opportunity to inspect the failure first.
Read the product detail before committing. Requirements and boundaries are part of the product, not small print.
Designed around the work
One deliberate run
Run one selected job at a time through the documented EasyRoute endpoint.
Visible retry decisions
A failed task waits for an owner decision instead of replaying automatically.
A focused companion
Pair it with EasyRoute and an installed Ollama model for a coherent local workflow.
What you need
- Windows and Python 3.11 or later.
- EasyRoute configured at its documented loopback endpoint.
- Ollama with a suitable installed local model.
- Enough disk space and memory for the intended queue and model.
A good fit for
- Windows users preparing batches of local AI tasks.
- Owners who prefer manual execution and retry.
- Small local workflows that need a visible queue.
Typical workflow
- Start Ollama and verify EasyRoute.
- Add a small task to the local queue.
- Select and run that task.
- Review the result before running the next task or retrying a failure.
Boundaries to know
- The Windows package is a release candidate; clean installation and model calls need validation in the intended environment.
- It does not reset provider limits or measure a subscription allowance.
- The supported path has no cloud fallback or automatic replay.
Talk it through