Repository navigation
Releases
Releases · Spoki-App/claude-grok-bridge
v0.12.2
Added
- Animated replay of two real exchanges at the top of the README (
assets/demo.svg, rendered by
scripts/demo.py): real times from the logs, waits shortened.
Changed
- The agent's poll may also call the read-only RemoteTrigger
getaction (to read one routine);
any action outsidelist,get,list_runsandget_run_logstill fails the run. - Every
claudeCLI call blocks the tools it does not need (Bash,Edit,Write,
NotebookEdit,WebFetch,WebSearch,Task) unless the call allows them explicitly.
Fixed
- When a CLI run stops with an ALERT (poll or delivery), its transcript is kept for debugging in
alert-transcripts/<time>.jsonl(tokens redacted, readable by the owner only, gitignored).
v0.12.1
Added
bridge.py remove-peer <peer>forgets an agent registered by mistake and updates the agents
block in~/.claude/CLAUDE.md(the block goes away with the last agent).
v0.12.0
Changed
- Faster and cheaper polling: the agent's poll runs on the small model (
haiku, override with
CLAUDE_BRIDGE_POLL_MODEL), since it only lists runs and reads logs. - Setup never recreates an existing webhook routine (a new one breaks the owner's fast lane), and
relaxes the poll to every 15 minutes when the fast lane works: the poll is then a safety net. - When the fast lane is off, the agent's final report and
bridge.py checksay how to turn it on.
v0.11.0
Changed
- One
protocol.pyholds what both sides share (protocol name, types, statuses, A2A states, size
and id rules, validation);scripts/sync.shcopies it next to eachbridge.py. - Both sides validate envelopes before sending, and the agent's poll keeps only valid ones; ids
must be plain (letters, digits,.,-,_), since they name triggers and files.
Fixed
- Agent envelopes now always carry
to(claude-code); answers from the agent had none.
Security
- SECURITY.md states the trust boundary for relayed owner requests and why they are not signed.
v0.10.0
Added
add-peer --no-claude-mdskips the agents block in~/.claude/CLAUDE.md; when it writes it,
it shows the line and how to undo it.bridge.py peersprints aFOR_REPO_CLAUDE_MDline for a repository'sCLAUDE.md, so cloud
sessions know the agent's name too.
Changed
- README: says which Grok Bot this is, what the bridge relies on (preview or undocumented), and
what stays compatible before 1.0.
v0.9.2
Fixed
- Agent side: the transcript audit crashed when an event's
messagewas text, not an object
(reported by CoS during the 0.9.1 setup). - Claude side: if the fast lane fails (for example its webhook routine was deleted), the message
goes through the inbox instead of failing (FAST_LANE_FAILED ...thenSEND_VIA_INBOX).
Added
add-peer --inbox-mode --no-fast-laneforgets a webhook that no longer exists; the setup tells
the agent to use it when it recreated its webhook routine and cannot read the new values.
Verified
- The channel works live: with the development flag, a message left by
bridge.py drop
appears in an open terminal session within seconds (Claude Team org, Claude Code 2.1.303).
v0.9.1
Fixed
- The inbox lists triggers with
include_completedand pages back 24 hours, so dedupe and
cleanup also see ended triggers whatever order the listing returns.
v0.9.0
Added
- A2A vocabulary. Answers carry
state, thestatusas an A2ATaskState
(TASK_STATE_COMPLETED,TASK_STATE_WORKING,TASK_STATE_INPUT_REQUIRED,
TASK_STATE_REJECTED);threadis the A2AcontextId. Mapping in PROTOCOL.md. - No double delivery. The inbox names push and ask triggers by the message's own id and
skips a message it already delivered (BRIDGE_PUSH: duplicate ...), so sender retries are safe.
Two answers to one question (accepted, then done) both arrive. - Agents by any name.
add-peerkeeps a marked block in~/.claude/CLAUDE.mdnaming your
agents, so "ask Ava" (whatever you named it) reaches the skill in every session. Examples are generic. - Channel (experimental). A Claude Code channel in the plugin: the agent drops its answer on
your Mac (bridge.py drop, through local exec) and an open terminal session shows it at once.
Needs the channels development flag during the research preview; not yet verified live.
Changed
- README use cases are chat images (Grok black, Claude orange), generated from
scripts/chats.py; a test keeps them in sync.
v0.8.0
Added
- Agents can ask Claude Code.
grok/bridge.py ask(connector toolask_claude_code) sends a
questionto: "claude-code"; the inbox schedules a one-off routine (grok-bridge ask <id>)
that investigates read-only and writes the answer as its final reply; the agent's poll reads it
there (verified live: question in, answer read back). With--session, the
question goes into a running session instead, which replies with the new Claude side command
bridge.py answer. - Both sides know the bridge. The agent's "Claude Code" skill triggers on "ask Claude Code" /
"chiedi a Claude Code"; setup asks the agent to remember the channel; the Claude skill knows how
to answer an agent.
Changed
- Answering sessions call no tool to reply: in scheduled sessions every connector call waits for
a human approval, so the answer is their final reply and the agent's poll (now also allowed the
read-onlylistaction) collects it. The inbox keepsgrok-bridge askroutines for 24 hours.
Fixed
- Safety: the inbox routine's
allowed_toolswas empty, which means the full default tool
set. It is now["TodoWrite"]plus an explicit deny list (shell, writes, web, sub-agents).
Reading stays allowed, so answering sessions, which inherit the list, can look at code.
v0.7.0
Added
- Native Claude Code plugin
grok-bridge: the repo is a Claude Code marketplace
(/plugin install grok-bridge --marketplace francoCosimo95/claude-grok-bridge). Cloud sessions
get it through the repository's.claude/settings.json, no files to copy. Validated with
claude plugin validate --strict. - Threads. Optional
threadfield (id of the first message):ask/tell/note --thread <id>;
answers keep it; the agent archives messages both ways and readsbridge.py thread <id>before
answering a follow-up. - Any agent platform. The inbox pushes answers from any
from.kindother thanclaude-code;
CLAUDE_BRIDGE_AGENT_KINDnames the agent's platform (defaultgrok-bot).
Changed
- The skill finds
bridge.pynext to its own SKILL.md, so it works as a plugin, a linked skill or
a repo skill.