agy-mcp-bridge 0.1.25 → 0.1.26

package/README.md

@@ -90,12 +90,12 @@ Four rules about these ids are easy to get wrong, all measured rather than infer
 
 - `agents.enabled` must list **every profile id** you declare, not just the adapters. A profile missing there is silently disabled, and a pool of such members then refuses with `Unknown agent "<pool id>"` — a message that names the pool while the broken line is `enabled`. Omitting `enabled` entirely enables everything; the example keeps the key so you can see it exists, which means a new profile has to be added to that list too.
 - A `codex` profile also needs the base `codex` id in `enabled`, because that is what makes the bridge probe the codex CLI at all. Without it the profile is unavailable **and reports no warning**, so `agents_list` shows a dead agent with no reason.
-- `model` on a profile is read only for a `codex` profile.
+- `model` on a profile is read only for a `codex` profile; an `antigravity` profile runs with the model you choose in the web UI.
 - `priority` and `enabled` accept a pool id without complaining, but the default agent is matched against agent ids only — a pool there silently selects nothing. Name the pool in the `agent` argument of a task instead.
 
 `agents.pools.<id>` groups profiles for quota handling. Delegating to a pool id picks the first healthy member. When a member stops with something that reads like an exhausted quota or rate limit, the bridge marks it cooling for `quota_cooldown_seconds` and re-runs **the same task** on the next member — each member at most once per task, after which the task fails instead of looping. The replaced attempt is kept on the record as `attempts[]` (agent, error, exit, log tails) so a reviewer can still see why the first CLI stopped, and the retry keeps holding the execution lock rather than releasing and re-taking it, so no second ordinary task slips into the gap.
 
-An `antigravity` **profile** also runs with the CLI's own defaults rather than the owner's web-UI settings: the model choice, the permission level (`--mode`), the soft-deadline log file and its extended `--print-timeout` are applied to the id `antigravity` only. The omission fails closed — with no `--mode` flag Antigravity soft-denies anything that needs approval — so a profile task is more restricted than the same task on `antigravity`, never less.
+The owner's Settings reach an `antigravity` **profile** exactly as they reach `antigravity`, because they key on the adapter behind the id, not on the id: the model, the permission level, the effort, and the soft deadline with its `--log-file` and its extended `--print-timeout` are all on the command line of a profile task. Read that as a widening, not a cosmetic fix — before, a profile was locked to the CLI's own defaults and could not be given `--dangerously-skip-permissions` at all; now your permission level applies to its tasks too, so a profile is no more restricted than the agent it comes from.
 
 Two knobs are opt-in because they widen what the bridge can reach. Neither is reachable from a task, and neither stays invisible: the codex pair is reported in `agents_list` warnings, and the XERJ pair in `/api/xerj/status` plus the refusal `code_search` gives while it is off.
 

package/dist/src/agents/antigravity.js

@@ -6,6 +6,7 @@ export function antigravityAdapter(executable, defaultTransport, options = {}) {
     return {
         id: options.id ?? 'antigravity',
         label: options.label ?? 'Antigravity',
+        family: 'antigravity',
         capabilities: CAPABILITIES,
         buildInvocation(task) {
             const transport = task.promptTransport ?? defaultTransport;

package/dist/src/agents/codex.js

@@ -9,6 +9,7 @@ export function codexAdapter(command, options = {}) {
     return {
         id: options.id ?? 'codex',
         label: options.label ?? 'Codex',
+        family: 'codex',
         capabilities: CAPABILITIES,
         buildInvocation(task) {
             const resultFile = path.join(task.stateDirectory, 'results', `${task.taskId}.txt`);

package/dist/src/tasks/manager.js

@@ -183,7 +183,7 @@ export class TaskManager {
                 context: input.context === undefined ? null : redact(input.context), timeout_seconds: timeout,
                 client: meta.client ? redact(meta.client).slice(0, 100) : null,
                 agent: task.agent, isolation: input.isolation, owns: input.owns, autonomy,
-                model: agent?.adapter.id === 'antigravity' ? await readModel(this.runtime.stateDirectory) : null,
+                model: agent?.adapter.family === 'antigravity' ? await readModel(this.runtime.stateDirectory) : null,
                 permission: permissionState(this.runtime.stateDirectory).level,
                 effort: readEffort(this.runtime.stateDirectory)
             }
@@ -312,7 +312,7 @@ export class TaskManager {
                 entry.request.permission = permission;
             // Soft deadline (owner setting, off by default): agy gets the absolute limit as its own print timeout and a log file whose growth shows it is alive.
             const soft = readSoftTimeout(this.runtime.stateDirectory);
-            const antigravity = agent.adapter.id === 'antigravity';
+            const antigravity = agent.adapter.family === 'antigravity';
             const absoluteLimit = Math.max(timeout, soft.limit_seconds);
             let logFile;
             if (antigravity && soft.enabled) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agy-mcp-bridge",
-  "version": "0.1.25",
+  "version": "0.1.26",
   "description": "Local loopback HTTP MCP bridge that delegates bounded coding tasks to multiple agent CLIs (Antigravity, Codex) with optional parallel git worktrees",
   "license": "MIT",
   "keywords": [