Skip to content

Pass inbound files to Codex as local path context#65

Open
evgyur wants to merge 2 commits intopwrdrvr:mainfrom
evgyur:evgyur/inbound-files-local-path-context
Open

Pass inbound files to Codex as local path context#65
evgyur wants to merge 2 commits intopwrdrvr:mainfrom
evgyur:evgyur/inbound-files-local-path-context

Conversation

@evgyur
Copy link
Copy Markdown

@evgyur evgyur commented Mar 28, 2026

Summary

  • include the local absolute path in text-file attachment context sent to Codex
  • pass non-image, non-text inbound files through as local-path references instead of dropping them
  • update controller tests to cover text-file path context and binary-file local-path handoff

Why

For Telegram/Discord Codex cockpit usage on the same host, the most reliable contract is:

  • inbound files are saved locally
  • Codex receives the local path and can work with that file directly

This avoids relying on outbound attachment re-delivery as the primary path.

Tests

  • npm run typecheck
  • npx vitest run src/controller.test.ts

@evgyur evgyur force-pushed the evgyur/inbound-files-local-path-context branch from 61f45b0 to a85cd54 Compare April 1, 2026 09:56
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