# agnostic-ai v0.95.0: import keeps what your tools wrote

> Source: <https://agnostic-ai.org/updates/2026-11-15-v0.95.0/>
> Published: 2026-11-14 23:00:00+00:00

## Highlights

- `import` keeps native settings under`x-<target>` for seven tools, so`sync` no longer drops them. See[import](https://agnostic-ai.org/docs/cli-reference/import/) .
- `import kiro` reads`.json` agent profiles and agents in subfolders of`.kiro/agents/` . See[Kiro](https://agnostic-ai.org/docs/targets/kiro/) .
- `hook run` reads Factory 1.11 and Crush 0.101 replies the way those tools do.
- Re-importing an agent with a per-target `effort` or`model` map changes only the imported tool's value.
- A chat closed in its terminal moves to Archived as soon as you have seen its last reply. See [companion](https://agnostic-ai.org/docs/cli-reference/companion/) .

## Upgrading from v0.94.0

- **Antigravity agents imported before this release:** a spec may still carry a top-level`tools` list that import used to copy. Delete that key by hand, or delete the spec and run`agnostic-ai import antigravity` again. The native list now lives under`x-antigravity.tools` . See[Antigravity](https://agnostic-ai.org/docs/targets/antigravity/) .

Then follow the [upgrade page](https://agnostic-ai.org/docs/cli-reference/upgrades/#upgrade).

## What changed

### Import keeps what your tools wrote

Agent, hook and MCP keys that have no portable field used to vanish on import, so the next `sync` removed them from your native files. They now land under `x-<target>` for Antigravity, Copilot, Kiro, OpenCode, OpenHands, Windsurf and Zed. Delete a key from the native file and the next import drops it. Literal credentials are still left out, with a warning that names the server and field.

`import kiro` now reads JSON agent profiles and nested agent files. `team/planner.md` becomes the spec agent `team-planner`. Import prints a note to remove the original after `sync` writes the new file.

### Hook tests match current releases

`hook run` reads Factory 1.11 replies (`ask` allows, top-level `decision: "block"` denies) and Crush 0.101 replies (`continue: false` halts). Crush hooks get `CLAUDE_PROJECT_DIR`. Antigravity payloads add `lastUserInput`, `hookEventName`, `cwd` and `toolCall.id`. Codex `SessionEnd` handlers use Codex's 1s default and 3s maximum. See [hook diagnostics](https://agnostic-ai.org/docs/cli-reference/hook-diagnostics/).

### Agent settings per tool

- Re-importing an agent whose `effort` or`model` is a map per target updates only that tool's entry.
- Augment writes `effort` as the Auggie 1.x`thinking` key, and Qwen Code writes`readonly: true` as a`disallowedTools` list.
- CodeBuddy sub-agents can restrict tools to one MCP server with `mcp__docs` .

### Companion

A Claude Code, Codex or `cursor-agent` chat closed in its terminal moves to Archived once you have read its last reply, not a day later. Both menus offer Small companion, a 40px circle.

See the [release notes](https://github.com/Chemaclass/agnostic-ai/releases/tag/v0.95.0) for the remaining fixes.

## What changed in the targets

- **Factory CLI 1.11.0** gives hook exit codes and JSON output one meaning on every event ([release notes](https://docs.factory.com/changelog/release-notes.md) ), and its hooks take a per-entry`onFailure` ([hooks](https://docs.factory.com/harness/hooks.md) ). This release maps`failClosed` to`onFailure: "block"` and reads the new replies in`hook run` .
- **Crush 0.101.0** gives hooks`CLAUDE_PROJECT_DIR` , the same value as`CRUSH_PROJECT_DIR` ([hooks](https://github.com/charmbracelet/crush/blob/v0.101.0/docs/hooks/README.md) ).`hook run` now sets it and reads Crush replies the same way.
- **CodeBuddy Code 2.181.0** lets a sub-agent name an MCP server in its tools ([sub-agents](https://www.codebuddy.ai/docs/cli/sub-agents) ). Sync writes`mcp__<server>` for`can: [mcp:<server>]` .
- **Zed 1.28.1** skips worktree task hooks in restricted mode ([worktree trust](https://zed.dev/docs/worktree-trust) ). The Zed page now says a`WorktreeCreate` task needs a trusted project; no output changed.
- **Jules** has been read-only since November 12, 2026 ([changelog](https://jules.google/docs/changelog/#jules-turndown) ). The Jules page drops the step that needs a new task; output is unchanged.

Checked on November 15, 2026 against the linked vendor docs and releases; native behavior was not run.
