Skip to content

托管实例把组织绑定写入 CLI profile 并区分两套工作区引导 - #68

Merged
earayu merged 2 commits into
mainfrom
feat/cli-workspace-identity
Sep 3, 2026
Merged

托管实例把组织绑定写入 CLI profile 并区分两套工作区引导#68
earayu merged 2 commits into
mainfrom
feat/cli-workspace-identity

Conversation

@earayu

@earayu earayu commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

组织 id 以前只活在进程环境里,bash 子进程 scrub 后 CLI 默认命名空间会变成个人空间。AGENTS.md 也不区分个人/组织。

这次把 org_idworkspace_kind 写进 CLI profile,另落一份不含密钥的 .apemind/workspace.json。组织/个人两套 AGENTS.md:组织实例说明平台 ro 不是组织权限、不要用 org role list 判断能不能写;个人实例不要传 --org-id。同时注入 APEMIND_INSTANCE_ID(值与现有实例键相同)。

镜像内置 CLI 钉到已发布的 v0.3.4(linux amd64/arm64 checksum 来自 apemind.ai 的 immutable release)。

Closes #67

…he right workspace.

Organization id used to live only in process env and got scrubbed, so collection create silently targeted the personal namespace. Write org_id and workspace kind next to the key, and tell agents that platform ro is not an org write ban.
…workspace identity.

The new CLI keeps the bound org on disk after env scrub. Pin the published checksums and move the documented image tag to the release this change ships with.
@earayu
earayu merged commit 0e07666 into main Sep 3, 2026
3 checks passed
@earayu
earayu deleted the feat/cli-workspace-identity branch September 3, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

托管实例把 org_id 写入 CLI profile 并区分两套工作区引导

2 participants