Getting Started
Prepare a project for the planned Eudorian Code developer workflow.
Before You Begin#
Eudorian Code is not yet distributed as a public CLI. This page establishes the intended setup sequence so package, authentication, and project contracts can be filled in without restructuring the docs.
- Use a source-controlled project with a clean recovery path.
- Review tool permissions before allowing file edits or commands.
- Treat every command below as a placeholder until a release note marks it available.
Install the Client#
Final package names and installer URLs are intentionally omitted.
Development placeholder
# Package and installer URL are not published yet
echo "Eudorian Code CLI coming soon"Open a Project#
The intended client flow begins in a local project directory, loads project-level instructions, and asks for permission before executing tools with material side effects.
Intended shape
# Placeholder command name
eudorian-code open .Verify the Session#
A future status view should identify the active project, model profile, granted tools, network state, and whether work is local or using cloud capacity.
TODO: status contract
The exact fields and command names will be documented after the client protocol is finalized.