Document workspace Git status and connection steps

[csandanov]

The Workspace page is changing in several ways:

• It now has a live Git status panel and step-by-step connection instructions for popular tools.
• It warns you when you have no SSH key.
• It calls the dependency installation after cloning "setup" and lists its steps.
• Claude Code, Codex and opencode come with the workspace.
• git push works with the app's Git integration.

This update describes those changes, so the workspace docs match what you see.

Merge when the updated Workspace page, the workspace coding agents and integration Git access are live.

Changes

In apps/workspaces.md:

• Git status: the Workspace page shows the current branch and whether it is pushed, the latest commit and the uncommitted changes. Only the owner sees it, and Refresh reads it again.
• Setup:
  • Preparation is now called setup. Setup steps lists the steps in order, and each opens its command.
  • The retry button is Retry setup, and the section is renamed "Edit, reload and rerun setup".
• Connecting:
  • The SSH host is wodby-workspace-<app>-<environment>, the same name MCP returns.
  • Steps for VS Code or Cursor (Remote - SSH), Claude Code (including claude remote-control), Codex, opencode and Hermes Agent. Any SSH-capable tool still works.
• Agents:
  • Claude Code, Codex and opencode come with the workspace, so you only sign in. Claude Code downloads from Anthropic on its first run.
  • The tools update with Wodby, and Claude Code and opencode need an Alpine-based runtime image.
  • Hermes Agent runs on your computer over SSH.
  • Older workspaces get the tools after Restart SSH runner.
• Git access:
  • git push and git fetch for the app's repository use the app's Git integration.
  • Per provider: on GitHub the credential only reaches that repository. GitLab and Bitbucket credentials carry the integration's access, and a read-only GitLab token can't push.
  • The credential is removed while paused or when you lose access. Other repositories still need your own credentials.
• SSH keys: the app form and the Workspace page warn until you add a key, and a key added later works without restarting the workspace.
• Deployments: in a workspace, a deployment restarts the selected services from the checkout, without builds or post-deployment scripts.
• Lists: app and environment lists mark workspaces with a Workspace tag.

In dev/mcp/tools.md, the workspace tools say "setup", and get_workspace_connection also returns the agents ready in the workspace.

Validation

• mkdocs build --strict passes with local plugins. The Markdown-export hook was skipped because its bs4 dependency isn't installed locally, so CI will run it.