Ir para o conteúdo
rovecode

registro de mudanças

O que mudou, e quando.

Cada versão, com data e número. Os motivos estão no blog; os fatos estão aqui.

  1. v0.3.0-preview.1prévia

    Accounts, plans and the organisation policy

    • The hosted service's first preview: sign in with GitHub or an email and a password, and an account page with a session, a password and a delete button.
    • rovecode policy pull fetches an organisation's deny-default rules and refuses to loosen them locally.
    • Plans appear in rovecode account with the quota window and the credits left.
    • Nothing in the CLI requires an account; every command from 0.2 runs unchanged without one.
  2. v0.2.2correção

    Provider reload without a restart, and a quieter approval card

    • The provider registry watches ~/.rovecode/providers.json and reloads on save; a running session picks up the new list at its next request.
    • The approval card no longer repeats the model's paraphrase of a command above the revised argv — the argv is the truth and now stands alone.
    • Esc during a Windows tool call kills the whole process tree, not only the parent.
    • Fixed: the plan panel lost its current-step mark after a rewind.
  3. v0.2.1correção

    Execpolicy verdicts for scripts, and the cwd lock

    • Execpolicy now gives a verdict on bun run <script> and npm run <script> by resolving the script body from the manifest, instead of treating the runner as opaque.
    • The runtime refuses a tool call whose working directory resolves outside the repository, even through a symlink.
    • The usage panel shows the provider that answered when a fallback chain was used.
    • Fixed: rovecode sessions tree printed branches in file order rather than time order.
  4. v0.2.0versão

    The sextant cockpit

    • Six panels on one screen: files with git status, code with the highlight band and ± diff, compact tool rows, plan, usage and the pet. rovecode --classic keeps the single-column TUI.
    • Sixteen built-in providers or any OpenAI-compatible endpoint, configured in one file with ordered fallback chains.
    • The approval card is the centre of the messages panel: revised argv, allow / always / deny, answers cached per session, child agents cannot prompt.
    • Sessions are an append-only tree with a sha256 hash chain; rewind branches, checkpoint names a node.
    • The market lists the MCP servers, skills and plugins that ship with the repository, with the one command that installs each.
    • Windows-first: development and the release gate run on Windows 11; POSIX paths are tested, Linux and macOS not yet CI-verified.
  5. v0.1.9versão

    Hooks, commands and the trust gate

    • .rovecode/hooks.ts runs before and after tool calls; a hook can veto a call and say why.
    • .rovecode/commands/*.md are slash commands: a prompt template with arguments, shared through the repository.
    • Project-scoped configuration under .rovecode/ is trust-gated: the first run in a repository asks before honouring its policy, hooks or MCP servers.
    • OpenTelemetry export, off until ROVECODE_OTEL_ENDPOINT is set; one trace per run, including cancelled ones.
  6. v0.1.8versão

    Deny by default

    • The rules layer: deny-default wildcard rules over tool and argv, evaluated before anything runs or is shown to a human.
    • The execpolicy layer: allow, prompt or forbidden verdicts on the parsed argv.
    • A bash denylist at execution time, and --yolo, which skips the approval rung and never the rules above it.
    • The README states each layer's limit next to the layer; the site's security section is generated from the same text.
Acompanhe as versões no GitHub