E
Docs/Eudorian Code/Eudorian Code Overview

Eudorian Code Overview

The future coding and agent interface for the Eudorian platform.

Preview

What is Eudorian Code#

Eudorian Code is the planned developer interface for working with Eudorian from the terminal, editor, and browser. It is being designed around practical agent workflows: understanding a repository, editing files, running commands, researching the web, and coordinating longer-running work.

This documentation describes the intended developer experience. Features that depend on unreleased services are marked as drafts and should not be read as production guarantees.

Core Advantages#

  • One workflow, multiple surfaces: Move between terminal, VS Code, and browser-based work without changing the underlying project model.
  • Tool-aware agents: Give agents controlled access to files, commands, research, and compatible developer tools.
  • Compute-ready architecture: Prepare for future local workers, contributed GPUs, and cloud overflow while keeping capability status explicit.
  • Open integration path: Use a planned OpenAI-compatible API and documented model identifiers as the platform matures.

Getting Started#

Start with the client that fits your workflow. Public packages and final installer locations have not been released.

Pre-release documentation

The commands shown here are non-executable development placeholders. They intentionally avoid implying a live distribution channel.

Using the Official Client#

The official client is intended to connect a local project to Eudorian Code while keeping file changes and command execution visible and reviewable.

Development placeholder
# Development placeholder — package not published yet
echo "Eudorian CLI installer coming soon"

API Access#

API access is planned for compatible tools and custom applications. Endpoint URLs, authentication flows, model IDs, rate limits, and usage accounting will be published only after the backend contracts are stable.

Draft interface

API examples in these docs are architectural references and are not production endpoints.

Next Steps#

Use Getting Started for the intended setup flow, or explore configuration, extension points, worker concepts, and API design from the navigation.