v0.69.0

Added

• Markdown prompt commands in the Code composer, and Markdown agents listed in the app. Typing / lists the commands of the project, your own and those of active plugins; /name args expands on the server with the CLI's rules, nothing executes, built-in commands keep priority, and a plugin command marks the turn as tainted. Automation › Agents lists Markdown and plugin agents read-only with their source, model and effective tools; they still run from chimera solve --subagents. (#977)

• A Code conversation knows the repository and branch of its folder. At the start of each turn the conversation records its project (the repository's main checkout), branch and whether the folder is the main checkout, a git worktree or a plain folder, read from the git files without running git. The record survives the worktree's removal, and the session list exposes it so the sidebar can group a repository's worktrees under the repository. (#965)

• Chimera reads Claude Code plugins and marketplaces as data. chimera.plugins reads a plugin directory (.claude-plugin/plugin.json, skills, commands, agents, hooks, MCP and LSP servers) and a marketplace.json, and classifies each component by what it would do: text only, start a local process, reach the network, or run commands. Nothing is installed, imported, executed or downloaded; only pinned sources (a local path, GitHub with a commit sha, an https archive with sha256) are installable, and problems carry stable codes compatible with claude plugin validate. (#966)

• Clean up a project's finished worktrees from the Code sidebar. A dialog lists every worktree of the repository with the reason each one is kept (main checkout, in use, dirty, unmerged, created outside Chimera...), previews the removal and removes only what the preview listed, with git worktree remove without --force and git branch -d. Only worktrees Chimera created can be removed there; their conversations are archived, never deleted, and the MCP bridge can list but never prune. (#967)

• Code conversations get readable titles, and you can rename them. The title follows your own name for it, then a title the caller passed (the MCP bridge's desktop_send takes title), then the first # heading of a Markdown file the first message cites inside the workspace, and only then the first message. Rename with the pencil on the row or F2; an empty name returns to the automatic one. No title is generated by a model. (#968)

• Install Claude Code plugins — disabled until you switch them on. chimera plugin install takes a local folder, a GitHub repository pinned to a commit sha or an https archive with its sha256; the plugin lands in <home>/plugins as pending, and nothing reaches the agent until you run chimera plugin enable. Then its skills, commands and agents appear namespaced (plugin:name) as untrusted text: agents follow project-agent rules, Claude Code tool names are translated and can only narrow, allowed-tools and model are ignored, and expanding a plugin command marks the run as tainted. Hooks, bin/ and monitors stay inert; an MCP server is added only when you name it, through the pinned-manifest hold. An update that changes the manifest, hooks, servers or tools holds the plugin with the diff. plugin:<name> joins the deployment policy, and bots, cron, serve and guests get no plugin unless CHIMERA_UNATTENDED_PLUGINS lists it. (#971)

• The parallel-batch panel can be minimised, moved and closed, and each task's answer reaches you. "Gerenciador de Agentes" now uses the same panel frame as the side panels (drag, move to a dock or back to the main column, minimise to a summary, close to a "Batch" chip that reopens it); hiding it never stops the batch, only Stop and Stop all do. Each task's final answer and how it ended are shown on its card (an analysis task reads "answered, no edits"), and the finished batch is recorded in the Code conversation, fenced as an agents' report; an answer from a task that read untrusted content marks the next turn as tainted. (#974)

• The MCP bridge opens a conversation inside a project. desktop_send takes project (a registered project or a known repository), and worktree: "new" with an optional branch: Chimera creates and owns the worktree beside the repository (.chimera-worktrees/<repo>/, never the temp folder), the conversation groups under the project, and the cleanup dialog removes it after the merge. Unknown projects, paths outside the project and run-branch names are refused, and a new worktree does not inherit the project's shell grant. Conversation worktrees now survive restarts: the storage card's orphan sweep no longer removes them. (#975)

• Settings › Plugins: see, add and switch on plugins. Mine lists each installed plugin with its status, source and pin, a capability line (instructions only, starts N MCP servers, reaches the network, brings hooks: inert), its components, update with a diff and remove. Discover lists the marketplaces you added, with search and filters by category and by what a plugin runs; entries that are not pinned stay visible with the reason. + Add takes a GitHub marketplace pinned to a commit, a local folder or a .zip. Switching a plugin on shows what will reach the agent and asks for each MCP server separately, and only you can do it: the MCP bridge can list, validate and install pending, never enable, remove or add marketplaces. (#976)

Changed

• The Code sidebar groups conversations by project, like the Claude desktop app. A repository's worktrees fall under the repository (a switch turns this off), each project has a collapsible header with a + for a new conversation there, a ⑂ count of its worktrees and a ⋯ menu (open, collapse, rename, hide, delete, clean up finished worktrees). Rows show the title and, under it, branch and time; five per project with "show more"; a search over title, branch and project; status filters only when they have counts. (#970)

Fixed

• The Code screen's side panel shows only cards that have something to show. Tools, Tokens, Memory and Fusion used to draw an empty frame with a dash; they now appear when data arrives. Titles are no longer forced to upper case and are no longer cut, the move/maximize/minimize controls appear on hover or focus, and a layout that was never customised gets a new default order. (#964)

• Approving with a click works again after you reopen the app. A background service the current app did not start holds no screen credential, so every click was refused until you restarted the service from the tray. The app now restarts such a service by itself: at once when it is idle, and as soon as running work ends when it is busy, without asking. While it waits, the approval card says so and offers approving with the code from a terminal or an explicit "Restart now" that warns it stops running turns. (#972)