Codex can hand the local work to Yaps.
Transcribe, caption, translate, clean and remember—using the Yaps engine on this computer.
Eleven plugin integrations.
All connect to one Yaps app with multiple engines. The desktop and CLI also include workflows outside this catalogue.
Download YapsOne request in. One reviewable result out.
The plugin describes the job. Yaps desktop supplies the installed engines. Codex brings the result back into the task.
- Ask from Codex01
Install the relevant Yaps plugin, then point it at a file, voice workflow or vault request.
- Yaps handles the local step02
The app checks account, version, models and dependencies, then runs the integration you asked for.
- Review before you use it03
Media inputs remain intact. Explicit vault writes can modify the selected note; unrelated content stays preserved.
Local does not mean invisible.
You choose the file or vault action. Yaps reports what it created. Destructive or permissioned work stays explicit.
01Does the plugin work without Yaps desktop?
No. The plugin supplies Codex with the workflow and safety rules; the installed Yaps app supplies the local engines, settings and file handling.
02Can a cloud task reach Yaps on my computer?
No. Use a local-capable Codex task on the same computer as Yaps. A remote cloud task cannot reach a desktop app or private vault installed on your machine.
03Does installing a plugin upload my notes or media?
No. Installation alone uploads no content. Task processing reads only what you select; readiness checks and privacy-safe operational diagnostics may also run without prompts, paths, filenames, audio, transcripts or note text.
04Does Yaps join or record live meetings?
No. The meeting integration processes a recording you already have. Yaps does not join a call or silently start recording one. Get participant consent and review suggested speaker identities.
Give Codex a local Yaps toolkit.
Start with the capability you need. The same Yaps installation is ready for the next one.