gonuGonu Worker
Bring an authorized local repository into a task with file access, diffs and approved checks.
WHEN IT HELPS
Put it to work.
Use Worker when you need Gonu to inspect actual project files, prepare edits and run local development checks.
Before you begin
- An available installer for your operating system and architecture.
- A Gonu account, an authorized project folder and the project’s normal build/test dependencies.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Choose an available build on Download. Install with normal OS protections and sign in to the same account used on the web.
Open the project and begin in Ask mode. Allow relevant repository excerpts to be used, then check the returned file references.
Use Plan before Build/Debug. Review requested writes and commands, inspect the final diff and check real build/test results.
Worker / Setup
A REQUEST TO START WITH
Explain how this repository handles sign-in. Point to the relevant files and tests. Do not change files yet.
THE USEFUL RESULT
What you should leave with.
A local engineering task whose file actions, approvals and validation results can be inspected.
Know the boundaries.
- Installer availability is live on the Download page. A published file alone does not establish signing or notarization.
- Selected context and history can pass through Gonu even when inference is local. Terminal actions run with the local user’s permissions.
IF SOMETHING DOESN’T WORK
A build is missing or the OS rejects installation.
Check platform, architecture and release notes. Use a publisher-verified build and contact support for a verification warning; do not disable OS protections.
Contact support