Kedge's command line runs over SSH. Install the optional shortcut to use kedge in place of ssh kedge.dev:

ssh kedge.dev setup | sh

Your SSH key signs you in. The installer also adds shell completion and the Kedge skill to detected agent environments.

deploy a project

From a project directory:

kedge up --dry-run
kedge up
kedge up --volume /data --machines 1

The first command previews the app name and Git push. The second deploys the current branch, initializing the repository and remote when needed. Later runs update the same app. See deploy workflows for branches, previews, GitHub, and rollback.

The optional volume and machine flags are deployment settings. Kedge carries them through the Git push and stores them on the app; they do not create a config file. See the configuration reference.

work with an app

kedge apps
kedge status myapp
kedge logs myapp
kedge env myapp LOG_LEVEL=debug
kedge shell myapp

Commands accept an app name or ID. Inside a project directory with a Kedge Git remote, commands can usually infer the app, so kedge logs is enough. Logs & metrics covers the streaming and query options.

start an agent task

Build a new app or continue an existing one with the built-in agent:

kedge agent "build a small status page"
kedge agent --app myapp "add a leaderboard"

With a terminal, each command stays open for follow-up turns. kedge agent --app myapp opens directly at the prompt. make, build, and create are unquoted aliases: kedge make me a status page.

See coding agents & workspaces for follow-ups, browser sessions, project boundaries, and named-workspace commands.

use SSH directly

The shortcut is optional. These are equivalent:

kedge apps
ssh kedge.dev apps

Open an app shell directly by using its name as the SSH user:

ssh myapp@kedge.run

Raw SSH also accepts direct content, exact input on stdin, Git pushes, and directory uploads:

ssh kedge.dev publish '# Hello'
ssh kedge.dev agent 'make me a status page'
scp -r public/ kedge.dev:my-site/
git push ssh://kedge.dev/$(kedge whoami)/myapp.git main

One-shot publishes reserve stdout for the full app URL. Use an explicit publish --verbose to add file, data-model, and timing details on stderr; agent one-shots put sparse progress and failures there. Pass --verbose after the agent verb for the full tool trace. Pipe a file to publish when its bytes need to remain exact. Only kedge up is local; it packages the Git steps behind a single command.

command reference

Run kedge with no command to see the same list in your terminal.

deploy and run

manage apps

configure apps

account