Development preview · Updated November 6, 2026
Security and operating boundaries
Know what you are allowing.
Cohandry is an installed development-preview application for a trusted, single-owner workspace. The app coordinates agents; model inference may use external providers. It is not an operating-system sandbox and is not designed to safely run hostile projects.
Agents and tools
You choose agents, reviewers, connections, project folders and tools. Model output, imported templates and source documents cannot grant those permissions. Tools run with the execution host user’s operating-system privileges. A named tool allowlist limits what Cohandry offers to the model; it does not isolate an allowed program from your computer.
Command approval and review
Project commands are disabled until enabled by the owner. Configured commands can require task- and revision-scoped approval. Approval fingerprints directly named existing script/input files; it does not cover all transitive imports, dependency changes or filesystem races. Inspect the actual command and its inputs before approving. Code, UI, model review and publication are separate checks. A file list or an agent’s success claim is not a code review.
Keys and tokens
API keys entered for a running session are held in memory; environment keys are configured on the host. Starting with 0.1.14, the installed desktop app encrypts saved ChatGPT account profiles and Slack credentials using Electron’s OS-backed secure storage. The OS may request credential access or an unlock. This does not encrypt project records, worker pairing/configuration files, external tool credentials or environment variables. Successful migration removes the older plaintext credential file, but older backups may still contain it. If migration cannot complete, the app reports the problem; protect any retained legacy files. GitHub CLI manages its own credentials and may fall back to a plaintext host file when its credential store is unavailable. Local file permissions help limit accidental access, but do not protect against another program running as you. Protect your operating-system account, disks and backups.
Remote workers use scoped worker credentials; coordinator model credentials are not intentionally forwarded to them. Managed tool processes receive a reduced environment. Owner-configured environment grants can provide selected values to a trusted tool.
Community templates
Community submission CI validates bounded JSON using trusted validator code without executing candidate instructions or fetching their URLs. Website deployment checks the actual downloadable bytes and requires a hash-bound maintainer publication record for community templates. Static checks and a review are not a safety certification; imports stay paused and tool grants remain explicit.
Sharing PR evidence
In 0.1.14, owners can preview and explicitly publish selected evidence reports, logs and text/images to their connected GitHub repository. Nothing is shared automatically. Reports identify an exact code commit; new code needs fresh evidence. Repository owners can edit/delete evidence branches and comments, so this is not immutable storage. Inspect screenshots and metadata for private information.
What leaves the machine
Selected instructions, source material, messages and evidence can be sent to the chosen model provider. Enabled GitHub or Slack features send the data needed for those actions. Update checks contact cohandry.com. Manual private reports send only the fields and attachments you select. See the privacy notice for more detail.
Interruption and recovery
Cancellation cannot undo a command or provider request already delivered. Interrupted or ambiguous tool work may require you to inspect external effects before retrying. Keep backups of your projects and use Cohandry’s coordinator backup; working repositories and all external assets are not automatically included.
Preview limits
Mac builds are ad-hoc signed and unnotarized. Windows installers are unsigned. Stronger OS isolation, immutable execution snapshots and OS-backed credential protection remain improvement work. SHA-256 helps compare a file with published metadata; it is not publisher authentication. Do not expose local services publicly.
Report a concern
Email support@cohandry.com or use the private report form. Describe the issue without attaching credentials or confidential project material.