alexeygrigorev / alexeygrigorev/codex-zcode

bridge: explore permission mirroring (interaction/* callbacks) to replace --mode yolo

Open
#25 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Context

The desktop never lets the core approve risky actions on its own: the core must ask via interaction/requestPermission and the host mirrors the request to the UI as an elicitation event, then answers with respond(id, decision).

Our fork runs --mode yolo - no gate between the model and the machine. Codex already has approval plumbing on its side of the bridge, so the missing piece is a core surface that can ask.

Proposal

  • exploratory: drive a core surface with callbacks so each permission request becomes a Codex-side approval request
  • --mode yolo becomes the explicit fallback, not the default
  • likely depends on the warm-process experiment (#23), since the stream-json surface has no callback channel

Evidence

zcode-article/ui-core-interaction.md, "The host middleware around raw RPC" and "Ideas to borrow" item 2.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with zcode-article/ui-core-interaction.md, especially “The host middleware around raw RPC” and “Ideas to borrow” item 2. Compare the proposed callback surface with the warm-process experiment in issue #23 and determine whether permission requests can reach Codex-side approval; done means the feasibility, dependencies, and fallback behavior are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.