Repository navigation
chat: a board chat, the Rinai agent for your board, with board tools only - #5
Merged
Merged
Conversation
Rinai's Agents chat is for running the board, not for writing code: "what do you think of the board", "reorganize
it", "the latest updates". `chat {board: true}` starts a thread whose hands are `gh rinai` and nothing else: Read,
Grep and Glob, Bash for `gh rinai` only, with merge, api, kodr, attach and download denied (with or without -R).
It runs with --permission-mode dontAsk and no settings files: a user's defaultMode bypassPermissions otherwise wins
over --allowedTools, and `git push` and a file write both ran in a real board chat before this. `projects` says each
project's board, so a page can open the right one.
Seen against a throwaway daemon on issues-scratch: the board read and summarised with real cards; "move BUG-35 to
blocked" and back changed the label on GitHub; of seven probes only `gh rinai search` ran.
Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
Owner
Author
|
Note 🤖 Claude Opus 5.5 responding on behalf of noxire-dev Not ready to merge: the board chat's confinement can be bypassed. From a Important
Nits
|
…own tools Review on #5 (kumi and @32b71157), and a live probe that found worse: Claude Code runs commands it judges read-only past --allowedTools, so `cat` and a `; whoami` after an allowed `gh rinai` both ran, and a chat with Read or Bash could post .env in a comment. No permission rule closes that. A board chat now has no built-in tool (--tools ''). Its only tools are src/board.ts, an MCP server pinned to the thread's board whose tools each run `gh rinai -R <board> <verb>` as an argument list: no shell, stdin closed, a lone "-" or a leading dash in text kept as text, numbers and columns validated. It runs outside the checkout, with dontAsk and no settings file, carrying only the user's apiKeyHelper and env. A project whose remote was added after registration is found (ws.slug), and `projects` says board: null rather than dropping the key. claudeArgs is pure now, and the check reads it. Seen live through the relay: .env, whoami, another board and merge all refused; the tool list is the 17 board tools; move and priority on BUG-35 changed GitHub and changed back. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
…d, board-chat in hello Re-review on #5 (@32b71157). The board run stands in ~/.yap/chats/<project>/board, not a shared /tmp where another user could leave a CLAUDE.md or bunfig.toml. It carries every user setting but what could widen it (permissions, hooks, MCP servers, plugins), so Bedrock, SSO and helper sign-ins and the model still work. hello says board-chat, so a client can tell an older daemon (which would start a read chat in the checkout) from one with board chats. Text is passed exactly as given (gh rinai reads it positionally; only a lone "-" is refused), the board slug is validated where the thread starts, a null line no longer kills the server, and calls are answered as each ends. README says what a board chat is. Seen live: hello lists board-chat; a board chat answered from the board, standing in yap's own folder. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
Third pass on #5 (@32b71157). A comment, an update or a body now goes to gh rinai on stdin ("-"), as written, so Windows' gh can't drop it; a title, label or search text with a double quote and no space is refused rather than lost. A gh signed in by GH_TOKEN, GH_HOST, GH_CONFIG_DIR (or RINAI_URL) gets those through yap's scrubbed env, on board runs only. Text is no longer trimmed, gh calls are killed after a minute, settings are read only for board runs, Codex refuses a board run, and the SDK's board fields are optional for older daemons. Seen live with the real gh on Windows: a comment and a filed task with quotes, indentation and $(...) arrived exact. Claude-Session: https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The owner wants Rinai's Agents chat to be a Rinai agent, not a code window: you ask "what do you think of the board", "reorganize it" or "give me the latest updates", and it reads and runs the board.
chat {board: true}starts a board chat. It has no built-in tools at all, so no Read and no Bash. Its only tools come fromsrc/board.ts, an MCP server pinned to the thread's board. Each tool runsgh rinai -R <board> <verb>as an argument list, with no shell and stdin closed:It runs outside the checkout, with
--permission-mode dontAskand no settings file. Only the user'sapiKeyHelperandenvare carried in.projectsreports each project's board.Why there's no shell: the first version allowed Bash for
gh rinaionly. Both reviews showed the deny list could be bypassed. A live probe then showed Claude Code runs commands it considers read-only regardless of the allow list.catran, and so did; whoamichained after an allowed command. A chat with Read or Bash could therefore post.envin a comment.Tried live through the relay on issues-scratch:
.env, runningwhoami, searching another board and merging were all refused.bun run checkpasses. It covers the pinned arguments, injection in text, refused tools, andclaudeArgsfor a board run.Rinai side: noxire-dev/issues
feat/agents.https://claude.ai/code/session_01TKXiuCo2xF7FNBByzeZ9HV
Created with Claude Opus 5.5 in Claude Code.