That's why we built Knows (https://t.co/nvqrfmZFZD)
Not another paper-writing tool. Not another PDF parser. A companion standard that puts structured knowledge first and lets the format serve whoever or whatever is reading it.
Academic publishing is an ivory tower still pretending it's 1995.
We train researchers to write eight-part-essay papers in a format optimized for human eyeballs, and then we feed those same PDFs to AI agents that have to reverse-engineer the structure from prose. #Agent#LLM
The information flow should be inverted. Content should be authored in the most efficient, structured, token-minimal form — optimized for agents. When a human needs to read it, the agent translates it into natural language. Not the other way around.
Just dropped Ageaf — the only agentic AI LaTeX companion built inside Overleaf. Claude Agent SDK + Codex CLI, full skills/MCP, zero migration. Write papers faster, smarter. Try it free!
https://t.co/mO8xeIPSrW
#LaTeX#Overleaf#AI#AcademicWriting
@DaleLJefferson@charlieholtz@Dimillian This is very true. Fmpov gpt 5.2xhigh is natively stronger than opus4.5. There has been a group of people opt to use 5.2 for planning and review and only have the Claude (so sonnet is enough) to do the coding. Missing full support for the codex is really regrettable.
Made a small fork: `planning-with-files-superpowers`. If you plan & review in codex using Superpowers, and implement in claude this adds a handoff: task_plan.md links the superpowers plan, supports checkpointed batches. See https://t.co/NxfbjUYOB2.
Hey @conductor_build, time to level up the Codex-in-Conductor experience like the $ and / and rollback.
Supporting Codex is the core differentiator (aka your real moat) vs the latest official Claude Code desktop, which already ships the separate-workspace + git worktree flow.
Don’t disqualify older Model 3s without native front bumper cam if future FSD updates require it. At minimum, enable post-installation retrofit with an extra fee to keep all owners in the loop! @elonmusk@Tesla@Tesla_AI
Keep FSD tied to the original car, but let owners bind that license to other Tesla on the same account. If the original leaves the account, FSD goes with it. This preserves revenue, adds flexibility, and rewards multi-Tesla users. @elonmusk@Tesla@SawyerMerritt@wholemars
@elonmusk@wholemars If Model YL is produced in Shanghai and sold in regions like Australia and Europe, will it support FSD? It seems like a missed opportunity if YL is excluded just because the US doesn’t have YL and therefore no FSD optimization is conducted on it.