From a request
to real work.

Explore what Eydra can do across your desktop.

One agent.
Different workflows.

Three independent examples.
One connected workspace.

Jump to the results

Organize the everyday.

Bring a file task into focus. Ask Eydra to rename, move, or inspect the files you choose.

Navigate your apps.

Follow the visible cursor and action trace in a guided web pilot demonstration, including approval controls.

Build in your tools.

A separate Blender session turns a reference into an editable scene. Connected tools bring specialist work into reach.

Organize the everyday.

Bring a file task into focus. Ask Eydra to rename, move, or inspect the files you choose.

Eydra request bar with attached reference files and a selected model
Actual Eydra interface · sample task

Navigate your apps.

Follow the visible cursor and action trace in a guided web pilot demonstration, including approval controls.

Guided demonstration with sample data.

Build in your tools.

A separate Blender session turns a reference into an editable scene. Connected tools bring specialist work into reach.

Detailed workshop scene recreated in Blender by Eydra using the selected model
Blender output from an actual Eydra session

Ideas leave
the chat.

Here are two that already did.
Actual artifacts from Eydra sessions.

Eydra-generated Blender workshop with a circular window, hanging lights, desk, shelves and a small robotExplore the render
Blender

A reference.
A whole new dimension.

A workshop recreated as an editable Blender scene: geometry, materials, lighting, and a camera. Built through the connected tools, with the selected model doing the planning.

Actual Blender render · Eydra + Astra

An actual recreation from a reference image. Results depend on the reference, model, and review.

Connect Blender in Settings

Open Settings → Knowledge → Connected tools. Identify your add-on first: Blender Lab and the community MCP for Blender use different servers. Choose Local executable and use the matching executable and arguments from the guide. Keep Blender and its add-on running.

See every field and the Settings screenshot →
Autodesk

From a drawing
to something tangible.

A dimensioned reference becomes an editable Fusion model. Work with explicit units, inspect geometry, and export files for the next step.

Fusion output · F3D, STEP, and STL

Blueprint ambiguities remain assumptions. Always verify dimensions, tolerances, and print suitability.

Connect Fusion in Settings

Install the Fusion MCP server and add-in, then use Settings → Knowledge → Connected tools → Local executable. The server arguments must match the add-in’s port.

See the Fusion values and connection check →
CAD flange created in Autodesk Fusion during an Eydra blueprint modeling session
32.34 mm14.76 mm6.00 mm

Dimensions recorded from this example model.

Powerful.
Still yours.

Your model. Your tools.
Your call when it matters.

Choose the intelligence.

Use OpenRouter or a compatible local model server. Switch models as the task changes. Your provider key stays in your OS keychain.

Set up a model in Settings →

See what happens next.

Visible actions, approval controls, and a task history. Sensitive UI decisions are handed back to you. Broader tools run with the permissions you grant.

Go beyond clicking.

Read and edit files, run Python, Node, and PowerShell, use installed programs, and connect specialist tools through MCP.

Configure runtimes and folders →

Bring the right context.

Bundled skills and local guides help Eydra approach specialist work. Enable integrated Context7 documentation or connect its MCP server when a task needs current library references.

Set up Context7 and its API key →

Be in the meeting.
Keep the meaning.

Capture a conversation, revisit its transcript, and turn it into notes and next steps. Eydra's meeting mode makes room for the part only you can do: being there.

Recording availability varies by platform. Meeting services and your chosen provider process the content you send.

Eydra meeting notes with summary, decisions, action items and transcript citations, using sample data

A few things
worth knowing.

What is Eydra?

Eydra is a desktop agent for Windows, macOS and Linux. You describe a task and choose a model. Eydra can read app interfaces, use local development tools, work with enabled files and call the MCP connectors you configure. What it can complete depends on your model, installed tools and permissions.

Do I have to use a specific AI model?

No. Connect your own OpenRouter account or use a compatible local server such as Ollama, LM Studio or llama.cpp. Model availability and image support vary. Cloud model usage is billed by your provider.

Does Eydra have a browser extension?

Yes. Eydra browser companion connects Chrome, Edge or Brave to the desktop app. Choose one tab or the current browser profile, read pages and group tabs opened for a task. The preview is currently installed unpacked; the homepage links to the extension and its setup guide.

Does it work with Blender and Autodesk Fusion?

Yes, through configured MCP servers. Blender also supports separate background Python execution and read-only geometry inspection. Fusion needs its application and MCP add-in installed. CAD measurements and manufacturing assumptions still need your review.

What stays on my computer?

The desktop app stores your provider key in the operating system keychain. When you choose a cloud model, task context and any supported images are sent to that provider. Local model servers can keep inference on your machine; external tools and connectors have their own network behavior.

How do permissions work?

Eydra shows its work and exposes approval settings. Its UI-action guards hand sensitive decisions back to you. General execution and connected tools have wider capabilities and run with the permissions you grant; they are not a filesystem sandbox. Stop ends local execution, but cannot undo external changes that already happened.

What should I know before installing?

Download the latest release from the homepage and check its signing status in the release notes. Manual releases require installing the downloaded package. Linux desktop actions require X11. Review the release notes and published checksums before installing.