cohandry.YOUR FIRST TASK
Get your team moving.
Start with a small text assignment to learn the controls. Then use the coding tutorial to give an agent a real project folder and GitHub workflow.
1. Open Cohandry
Verify your email and download the preview for your platform. On Windows x64, run the single Setup EXE. On Apple Silicon Mac, extract the ZIP, move Cohandry.app to Applications and open it. The app bundles its runtime. The development preview is not Developer ID signed or notarized; use your system's supported approval flow only for a download you trust.
Windows x64 and Apple Silicon Mac have separate downloads. Windows may show an unknown-publisher warning for this unsigned development preview; verify the source and published checksum. Your project records stay in the local app; website email verification is separate from connecting a model.
2. Create a project
Choose Projects → New project. Give it a short name, such as “My first project”. In Project context, describe the purpose, audience and shared constraints once:
A small task-list app for personal use. Keep this milestone focused on a simple browser interface. Do not add accounts or a backend.
In Workspace, choose an existing folder, connect GitHub, or select Choose later. In Resources, upload documents or link selected repository paths. Choose a starting team and connection. Use Back or Edit in Review to make changes. Save: the project has an amber Paused pill and does not run work automatically.
3. Connect a model—or try Demo
Use Edit connection in project setup to select the provider and exact model and save its API key together. The badge beside the key field confirms when it is saved for the session. Keys must be re-entered after restarting the coordinator. Use Accounts & API keys for account authorization and reusable credentials. Test access with a small task. API use is separately billed; product signup does not provide model credits.
Choose Demo to explore the controls without model calls or tools. Demo results are simulations, not implemented code.
4. Write one clear assignment
In the project, choose New work → Direct task and select an agent. Keep the fields distinct:
- Task name: “Plan the first task-list feature”.
- Assignment: “Propose the smallest useful add-task feature. List the UI behavior and edge cases. Do not edit files or start implementation.”
- Success criteria: “A short plan covering normal input, blank input and keyboard use, with an explicit stopping point.”
The project context supplies background; the assignment states what to do now; success criteria define how you judge the result. The agent's responsibilities describe its ongoing role. See the full field reference. For more detail in the app, hover, focus or tap the ? icon beside a field. Short placeholders are hints, not saved instructions.
5. Start, inspect and review
Run Check setup, resolve configuration issues and choose Start new work. Watch Work for progress and queue explanations. Open Inspect task to read the result. If review is required, inspect the current revision before approving it or requesting changes.
Pause new work when you finish. Pausing prevents new tasks from starting; it does not undo an operation already running.
Check App settings → Application updates or Cohandry → Check for updates… for a new release. Quit after running work finishes before installing. On Windows, run the new installer over the existing installation; your app data is preserved.
6. Move from planning to code
Real file changes need a trusted execution host, a project folder and a real model connection. The next guide walks through that setup, command approvals, evidence, corrections and optional GitHub delivery.