Skip to content

Agent-aware branding + workspace writability defense#6

Merged
nprodromou merged 1 commit into
mainfrom
fix/agent-aware-bashrc-and-workspace
May 7, 2026
Merged

Agent-aware branding + workspace writability defense#6
nprodromou merged 1 commit into
mainfrom
fix/agent-aware-bashrc-and-workspace

Conversation

@nprodromou

Copy link
Copy Markdown
Owner

Two fixes:

  1. profile/.bashrc — prompt/banner/help text now driven off ${AGENT} instead of hardcoded codex@. Claude pod no longer shows codex branding (claude flagged this as P3 on WOVED-41).
  2. bin/entrypoint.sh — defensive mkdir -p ~/workspace + chmod u+rwX so the agent can write there even if PVC ownership got stale from a prior root-owned pod. Real fix is fsGroupChangePolicy=Always on the HelmRelease (separate apk8s PR follows).

profile/.bashrc:
- Drove the prompt, banner header, and help hint off ${AGENT} instead
  of hardcoding "codex@". Claude pod no longer shows codex branding.
- Identity banner reads ~/.${AGENT}-identity (matches what entrypoint
  writes).

bin/entrypoint.sh:
- Defensive workspace bootstrap: mkdir -p ~/workspace, chmod u+rwX if
  we own it. If not writable (stale PVC ownership from a prior root-
  owned pod), warn and fall back to /tmp/workspace so the agent can
  still operate. Real fix is fsGroupChangePolicy=Always on the
  HelmRelease securityContext (separate apk8s PR) — this block is
  defense-in-depth.

Picks up claude's review of WOVED-41 (P3): the pod was running the
new image but inheriting codex branding from the static profile.
@nprodromou nprodromou merged commit 1db5cae into main May 7, 2026
2 checks passed
@nprodromou nprodromou deleted the fix/agent-aware-bashrc-and-workspace branch May 7, 2026 06:57
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.

1 participant