Kryden Agent

Install

Desktop app

Use the Kryden downloads page for the current macOS desktop build and platform notes. After installation, open Kryden Agent and follow the first-launch setup flow.

Kryden is designed to keep setup language plain inside the app. If setup needs deeper inspection, use Diagnostics after the app opens.

Download Kryden Agent

First launch

First launch should get Kryden ready to work on this computer. Choose local setup if this Mac should run Kryden. Use the connection path only if you already control another Kryden Agent.

1. Open Kryden Agent The desktop app is the place to start work, review progress, approve actions, and see the context Kryden is using.
2. Choose how this computer should participate Choose local setup if this Mac should run Kryden. If you already control another Kryden Agent, use the connection path instead.
3. Connect an AI account Follow the guided sign-in or account setup flow. Kryden will confirm when it is ready to accept requests.
4. Start with a specific goal Give Kryden the outcome, important constraints, and the files or background it should use. Kryden works best when the target is concrete.

Core concepts

These are the practical product surfaces you will see while using Kryden.

Chats

Focused surfaces for a goal, project, investigation, draft, review, or follow-up thread.

Shared context

Useful background Kryden can carry across work so you do not have to restate the same projects, preferences, files, or constraints every time.

Approvals

Plain-language review gates for actions that need permission. Kryden should explain what it wants to do and wait for your decision.

Brain Dump

A place to turn loose notes into saved actions or documents before you decide what to do with them.

Routines

Recurring checks, reminders, briefs, or follow-ups that should keep moving without starting from a blank chat each time.

Diagnostics

A troubleshooting area for setup, account, connection, and deeper activity details when the normal product path is not enough.

Example requests

A good Kryden request names the outcome, useful background, and any boundaries Kryden should respect.

Research the best three options for [goal]. Use recent sources, explain tradeoffs, and recommend one path for my situation.

This project is [project]. We care about [constraints]. Start by reading [files or links] and tell me the current state.

Audit this folder and propose the smallest real fix. Do not edit files until you show me the plan and the risks.

Every weekday morning, check [thing], summarize what changed, and flag anything that needs my attention.

Routines

Routines are for work that should come back on a schedule: follow-ups, checks, summaries, briefs, reminders, and recurring reviews.

• Name the thing Kryden should check and how often it should run.
• Say what should count as important enough to interrupt you.
• Use Briefs for scheduled results you want to review later.
• Keep credentials, private links, and sensitive data in the app's secure setup flow.
• Review recurring work periodically so stale instructions do not keep running.

Security

Kryden can help with powerful work. Treat actions that touch files, browser sessions, credentials, commands, schedules, or other agent connections as review-worthy.

• Keep secrets in the app's credential flow or environment, never in source files, public docs, screenshots, or logs.
• Review actions that can change files, send data, use credentials, run commands, schedule work, or connect to another agent.
• Only connect to Kryden Agent addresses you control or trust.
• Use Diagnostics when setup, account, connection, or permission state needs closer inspection.

Diagnostics

Diagnostics are for setup and troubleshooting. Use them when the normal product path does not explain account state, connection state, approval state, or why a task did not continue.

Everyday work should stay in the normal chat and routine surfaces. Diagnostics are there when you need closer inspection.

Troubleshooting