jester/knowledge-base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update AI workflow - both Claude and GPT use same MCP, relay is a connector issue not a fundamental gap

Browse Source
This commit is contained in:
jester 2026-04-10 12:03:05 +00:00
parent ba029a24a5
commit 3623df6841
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
OWNER_PROFILE.md
View File

@ -120,7 +120,7 @@ James acts as **system architect**. He:
This is intentional and should be preserved. Claude should not drift into implementation mode. GPT should not make architectural decisions.
**Current workflow constraint**: James acts as manual relay between GPT and Claude for repo updates. GPT cannot currently write directly to Gitea or GitHub. This is a known operational gap — the intended fix is to give GPT direct Gitea API access with a scoped write token on `zlh-grind` only. Until then, Claude handles all knowledge-base commits and any cross-repo coordination GPT needs.
**Repo access**: Both Claude and GPT access Gitea via the same MCP server (`https://git.zerolaghub.com/mcp`). GPT's MCP connection has previously worked and lost access — this is a connector configuration issue, not a fundamental limitation. When GPT's MCP is connected, it can write directly to `zlh-grind` without James relaying through Claude. Claude handles `knowledge-base` writes as the architecture authority.
---