You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ee632a8
Browse filesBrowse the repository at this point in the historyBrowse files
docs: describe the fork as covering both Codex and Claude Code
The fork now manages Claude Code sessions as well, but its docs still
presented it as a Codex-only extension.
- README / README.zh-CN: retitle to "Windows Session Remote Management
Extension for Codex and Claude Code"; update the tagline, intro,
section headings and ownership diagram; mark /windows as Codex-only;
add the Claude flow to the typical workflow and the Claude profile and
release-agent steps to build and install.
- Move the screenshots back under "Remote session management". The
previous commit had left them nested under "Claude Code sessions",
though they show the Codex cards.
- local-docs/README*.md were verbatim copies of an older root README,
with every relative link broken from that directory. Replace them with
the documentation index the root README already calls them.
- local-docs/03: retitle to cover Claude Code, and say where its section
lives.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+40-28Lines changed: 40 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# lark-channel-bridge — Windows Codex Session Remote Management Extension
1
+
# lark-channel-bridge — Windows Session Remote Management Extension for Codex and Claude Code
2
2
3
3
**English** | [简体中文](./README.zh-CN.md)
4
4
5
-
> A Windows-focused downstream extension of **`lark-channel-bridge`** for discovering and monitoring local Codex CLIsessions, safely transferring session ownership between Windows and Lark, and remotely managing multiple Codex sessions from Lark Mobile App or Lark Web.
5
+
> A Windows-focused downstream extension of **`lark-channel-bridge`** for discovering and monitoring local **Codex CLI** and **Claude Code**sessions, safely transferring session ownership between Windows and Lark, and remotely managing multiple sessions from Lark Mobile App or Lark Web.
6
6
7
7
## Upstream project — `lark-channel-bridge`
8
8
@@ -20,17 +20,17 @@ This fork intentionally keeps the upstream project prominent in the documentatio
20
20
21
21
## What this fork adds
22
22
23
-
The upstream bridge already lets a Lark Chat / Group / Topic interact with a local coding agent. This fork adds a Windows-focused **Codex Session control plane** for Codex sessions that may have been started independently in Windows Terminal rather than created only through the current Lark scope.
23
+
The upstream bridge already lets a Lark Chat / Group / Topic interact with a local coding agent. This fork adds a Windows-focused **Session control plane** for Codex and Claude Code sessions that may have been started independently in Windows Terminal rather than created only through the current Lark scope. Each bot manages the agent its profile runs, with the same `/session` commands for both — see [Claude Code sessions](#claude-code-sessions).
24
24
25
25
| Area | Upstream `lark-channel-bridge`| This fork adds |
26
26
|---|---|---|
27
27
| Lark/Feishu ↔ Claude Code / Codex bridge | Core upstream feature | Reused as the foundation |
| Streaming and interactive cards | Core upstream feature | Extended with session-control actions |
31
-
| Windows Codex sessions started independently of Lark | Not the focus of the original Lark scope model | Automatic local discovery and monitoring |
32
-
| Windows runtime view | — |`/windows status`|
33
-
| Safe Windows writer release | — |`/windows release` with Release Agent |
31
+
| Windows Codex / Claude Code sessions started independently of Lark | Not the focus of the original Lark scope model | Automatic local discovery and monitoring |
32
+
| Windows runtime view (Codex) | — |`/windows status`|
33
+
| Safe Windows writer release (Codex) | — |`/windows release` with Release Agent |
| Windows → Lark ownership transfer | — |`/session handoff`|
@@ -42,7 +42,7 @@ The upstream bridge already lets a Lark Chat / Group / Topic interact with a loc
42
42
43
43
### Why these extensions exist
44
44
45
-
A common workflow is to start several Codex CLI sessions directly on a Windows workstation and later leave the computer. The additional Observer, monitor, release, and ownership layers let Lark become a remote control surface for those existing sessions:
45
+
A common workflow is to start several Codex CLI or Claude Code sessions directly on a Windows workstation and later leave the computer. The additional monitoring, release, and ownership layers let Lark become a remote control surface for those existing sessions. For Codex the path looks like this (Claude Code needs no Observer — it keeps its own process registry; see [Claude Code sessions](#claude-code-sessions)):
46
46
47
47
```text
48
48
Windows Terminal / codex3
@@ -66,14 +66,14 @@ Windows Terminal / codex3
66
66
67
67
From Lark you can inspect Windows sessions, safely release a waiting Windows writer, hand a session to the current Lark scope, use a detached session, and hand the current Lark-owned session back to Windows without requiring Remote Desktop.
68
68
69
-
## Remote Codex session management from Lark
69
+
## Remote session management from Lark
70
70
71
71
The UI follows the same three-layer model as the command set:
72
72
73
73
| Scope | Recommended commands | Meaning |
74
74
|---|---|---|
75
75
| Lark Scope |`/lark status`, `/lark new`, `/lark resume`| Current Lark Chat / Group / Topic binding |
76
-
| Windows Runtime |`/windows status`, `/windows release`| Windows Codex TUI, Observer, Release Agent, writer |
76
+
| Windows Runtime (Codex only) |`/windows status`, `/windows release`| Windows Codex TUI, Observer, Release Agent, writer |
77
77
| Global Session Manager |`/session list`, `/session use`, `/session handoff`, `/session handback`| Cross-runtime inventory and ownership transfer |
78
78
79
79
The interactive cards are especially useful on a phone:
@@ -99,6 +99,23 @@ Project names and working directories are shown as metadata, but are **not** use
99
99
100
100
`/session list` opens on category tabs — **Handoff**, **Use**, **Hand Back**, **All** — drawn from the 10 most recent Sessions, defaulting to the first category that has a Session in it. Each tab lists exactly the Sessions that render that action's button. Use `/session list <keyword>` to find an older Session.
This makes it possible to inspect and switch Codex ownership remotely from Lark Mobile or Lark Web while keeping the Windows/Lark single-writer rule explicit.
118
+
102
119
## Claude Code sessions
103
120
104
121
A profile runs exactly one agent (`agentKind` is `codex` or `claude`), so every `/session` command works on **that profile's agent**. The commands are identical on a Codex bot and a Claude bot — there is no agent parameter:
@@ -145,23 +162,6 @@ Codex does not need this step because `codex3` starts its Release Agent from the
145
162
146
163
Without the agent, elevated Claude windows are shown as **Running as administrator — Claude release agent not running** and offer no Handoff button. Claude windows started from a normal terminal can be handed off without it.
This makes it possible to inspect and switch Codex ownership remotely from Lark Mobile or Lark Web while keeping the Windows/Lark single-writer rule explicit.
164
-
165
165
## Compatibility aliases
166
166
167
167
Legacy commands remain available as compatibility aliases:
@@ -221,10 +221,16 @@ Then resume it on Windows with the command returned by the bridge:
221
221
codex3 resume <Session-ID>
222
222
```
223
223
224
+
With Claude Code the flow is the same, in the Claude bot's group: start `claude` on Windows, then use `/session list` / `/session handoff` (there is no `/windows` step), and resume on Windows after a handback with:
225
+
226
+
```powershell
227
+
claude --resume <Session-ID>
228
+
```
229
+
224
230
## Ownership model
225
231
226
232
```text
227
-
One Codex Session
233
+
One Session (Codex or Claude Code)
228
234
│
229
235
├── Windows writer
230
236
├── Lark scope
@@ -268,8 +274,14 @@ pnpm build
268
274
npm install -g .
269
275
.\scripts\windows\Install-CodexBridgeScripts.ps1
270
276
277
+
# Once, from an elevated PowerShell, if you start Claude as administrator:
278
+
.\scripts\windows\Register-ClaudeReleaseAgent.ps1
279
+
280
+
# Restart each profile you run:
271
281
lark-channel-bridge stop --profile codex
272
282
lark-channel-bridge start --profile codex
283
+
lark-channel-bridge stop --profile claude
284
+
lark-channel-bridge start --profile claude
273
285
```
274
286
275
287
Do not replace the local build with `npm install -g lark-channel-bridge@latest`; that installs the upstream registry package and removes the local session-management extensions.
@@ -279,7 +291,7 @@ Do not replace the local build with `npm install -g lark-channel-bridge@latest`;
> -**Project observations** from Windows + Codex CLI 0.155.x with an isolated `CODEX_HOME`.
10
10
> -**Public Codex implementation/documentation** from OpenAI's Codex docs and the `openai/codex` repository. Internal storage formats can evolve and should not be treated as permanent public APIs.
11
+
>
12
+
> Most of the document is the Codex reference. The Claude Code side — its transcripts and process registry, the Claude Release Agent, and how both agents bind to a Lark scope — is covered under `/session list` in section 28.
11
13
12
14
---
13
15
@@ -16,7 +18,7 @@
16
18
17
19
```text
18
20
Lark Scope → /lark status | /lark new | /lark resume
19
-
Windows Runtime → /windows status | /windows release
21
+
Windows Runtime → /windows status | /windows release (Codex only)
20
22
Global Sessions → /session list | /session use | /session handoff | /session handback
0 commit comments