Skip to content

Orca v0.52.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Oct 23:44
· 118 commits to main since this release
v0.52.1
a4befdc

Safer and more solid

We put the last few releases through a round of adversarial reviews: security, backend and app. This release fixes what they found.

Security

  • Your AI tools' config files stay private. Connecting Orca to Claude, Cursor, Codex and the others keeps each config file's permissions, keeps symlinked dotfiles as symlinks, and never loses a change the tool itself made at the same moment.
  • Codex's config.toml keeps its comments, and Orca writes it as valid TOML.
  • More secrets stay on your machine. Before the built-in assistant sends tool results to a cloud model, Orca now also blanks out:
    • Kubernetes Secret manifests
    • .env-style command output
    • every password in a URL
    • keys such as APP_KEY and *_PAT
  • The built-in assistant can't delete things. It runs tools without asking, so tools that remove containers, images, volumes, routes or projects, prune, or overwrite orca.yaml aren't available to it. Do those in Orca, or from an AI tool connected over MCP, which asks you first.
  • MCP clients ask before anything that changes state. Stopping a container, switching profiles, running a command or applying Kubernetes YAML is now marked destructive; only tools that add or start something aren't.
  • The compose file editor only edits YAML files inside the stack's own folder.
  • On Windows, Open in… refuses folder names that the command prompt would run as commands.

Fixes

  • Kubernetes port-forwarding works again. Every connection was refused.
  • Opening a folder:
    • It uses the compose files listed in the folder's orca.yaml.
    • It follows Compose's own rules for project names.
    • It warns you when another folder already runs under the same name, instead of replacing it.
    • Errors stay on screen, and Open tries again after you fix the problem.
  • A first compose.yaml is no longer refused because an .env file it mentions doesn't exist yet.
  • orca mcp answers batched requests and survives unreadable input.
  • On Windows, Orca's own orca command updates even while an AI tool is running it.
  • Gateway settings: if the gateway won't start with new settings, Orca puts the previous ones back instead of leaving it stopped.
  • In the app:
    • Shell works on the container you're already looking at.
    • Deploying a stack from the catalog opens its page.
    • The assistant settings no longer mix up one provider's models with another's.
    • The AI window says when no supported AI tool is installed.
    • A custom search URL you typed wrong stays in the field so you can fix it.
    • ⌘K keeps your selection in view.
    • A stack page's URLs refresh by themselves.
    • The Ollama container restarts with your computer as intended.
Assets 16
Loading