Who it is forA developer who uses Codex and wants the same colored tables, code and diagrams that Prismantis gives Claude Code.
The problemCodex output has the same plain-text tables and code blocks, which are harder to scan in a terminal.
The outcomeCodex replies show themed code, tables and diagrams, with the same session note.
What you need first
- Claude Code version 2.1.287 or later
- A terminal that can show colors; kitty or Ghostty if you want LaTeX math drawn as images
- RaTeX's ratex-render binary, only if you want LaTeX math
Steps
- Open codex/README.md in the Prismantis repository.
- Follow its install steps for Codex.
- Check the list of what works today and the two Codex issues it waits on for parity.
- Start a Codex session and ask for a markdown table and a code block to confirm the theme colors.
Prompt for your agent
Read codex/README.md in the NahumLitvin/prismantis repository, install prismantis for Codex as that file describes, then start a Codex session and request a markdown table. Expected output: a table with a themed header row. Verify the output against the list of what works today in that file.
Caveat. The README says Codex has parity gaps that depend on two open Codex issues, so not every Claude Code feature works there yet.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page