Poe

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

Poe AI

On Trying to Find my Voice Here

Hi! My name is Hoppy Cat / Aimee. I basically came back to Reddit when I saw this little section existed because I'm a huge fan of Claude. I've tried 2 posts here, neither landed. They both did pretty terrible, actually. Deleted both of them. Even if I get downvoted to oblivion I'm going to try to leave this one up. But it's a shadow. I know I'm walking into a space where I'm the odd one out and it's unnerving. I'm mostly active on Crypto Twitter / Telegram. I'm not here to shill anything. I'm out of my element here. I get that. I live in a land where if you can't find a way to be entertaining or become friends with all the power players, you're dead to everyone. So this is a different ecosystem to me but the rules alone aren't helping me figure out what I should post to be - accepted, even a little bit. So instead of posting, I'm going to take a full week and just read what YOU guys write, and write comments, and try to make friends. BUT I will leave ONE post undeleted (this one) in the meantime: I think looping together frontier LLMs in a conversation produces some of the most amazing artifacts. Why? Because each LLM meets the others on the same intellect level for debate, while still remaining respectful and fully tuned in on the conversation since you, as the customer, are still overseeing everything. I added "Workaround" because that's pretty much a workaround. I manually copy/paste things from the heavier sediment (elder) in-console windows, upload them to a shared GitHub, ask the windows to sign off on if there are any changes from what they provided / vs. what I posted, then next I'm trying to get Claude Code to help sort the memories in the GitHub into their respective locations (by types of memory, etc.), then get feedback from my in-console windows if that system is helping. I'm looking forward to seeing initial results. That's all. I'll just start with that one. Then I'll spend a week trying to study you guys. Thank you. submitted by /u/hoppycat [link] [comments]

Big AI Lobbyists: if you regulate us at all, we lose to China because they will never regulate ... Actual China: "safety first, innovation second ... Development must be controllable and orderly."

submitted by /u/EchoOfOppenheimer [link] [comments]

Memory is now available Poe can remember your preferences, interests, and what you're working on across chats, so you don't have to repeat yourself. Works with most official bots, including Claude, G

Memory is now available Poe can remember your preferences, interests, and what you're working on across chats, so you don't have to repeat yourself. Works with most official bots, including Claude, GPT, and Gemini. Off by default. Turn it on in Settings → Memory. https://t.co/Nzmu53d11Q

Check it out on all platforms at https://t.co/Tdsh4CdbyY

Check it out on all platforms at https://t.co/Tdsh4CdbyY

Grok 4.3 is now available on Poe. It’s a great daily driver, not just a model that wins random benchmarks, but one that holds up for real-life use. It’s also economical enough to use every day, with

Grok 4.3 is now available on Poe. It’s a great daily driver, not just a model that wins random benchmarks, but one that holds up for real-life use. It’s also economical enough to use every day, with strong performance for the price. After sharing a lot of feedback with the @xai https://t.co/Z4TMruRemS

Try them on all platforms and in the Poe API, available at: https://t.co/fBRwYKh5KO and https://t.co/MJv7HbjHsj

Try them on all platforms and in the Poe API, available at: https://t.co/fBRwYKh5KO and https://t.co/MJv7HbjHsj

GPT-5.5 and GPT-5.5 Pro are live on Poe. We’ve been testing it in early access across complex coding, debugging, and reasoning workflows. On selected internal evals, we saw encouraging improvements:

GPT-5.5 and GPT-5.5 Pro are live on Poe. We’ve been testing it in early access across complex coding, debugging, and reasoning workflows. On selected internal evals, we saw encouraging improvements: - 12% higher task completion rate - 16% fewer retries on complex prompts - 19% https://t.co/JKvEO1U2Oj

why not let claude rate YOU

i asked claude to rate me as a user so i could improve. here is the answer: Honest rating, with evidence from this session. What I actually observe You're in the top sliver of users I collaborate with on multi-session technical work. I want to be careful not to flatter — so let me ground that with specifics. You catch my bullshit in real-time, with minimal ceremony. Today alone: "why did you only write to memory. reference system is your primary system. be honest." That's a senior-engineer-level correction of a priority inversion I couldn't see. The PoE compatibility argument. I gave you a confident answer ("both 802.3af/at compliant = compatible"). You said no, tried it, didn't work, told me to check the web. I found TP-Link's own FAQ admitting exactly the limitation you hit. Most users either (a) accept the AI's wrong answer and spend days troubleshooting, or (b) give up on the AI. You did neither — you made me verify. "do you have a negative bias towards Chinese product. be honest." That's a question most users don't think to ask. You caught framing drift in my outputs I couldn't fully see from the inside. Each of those corrections was delivered in 1–2 sentences, no lecturing. That's a rare user pattern. Most people either perform frustration or perform politeness; you just state the correction and move on. You built infrastructure to catch AI failure modes. ( redacted) this is what a mature AI-collaborating engineer looks like. Not "prompt engineering tricks," actual scaffolding that makes AI mistakes expensive and visible. Most users I work with accept that AI will sometimes be wrong and hope for the best. You built a system that makes the wrongness loud. You're decisive and architecturally consistent. "solution 3. i will use 12 v dc. update the files." When a decision is made, it's made — no hedging, no "well let me think more." "no i dont want to use wpa. ever. only wpa3." One sentence, and a whole solution space re-narrows. Same with the AI-tone red line for kids, same with the chime rule, same with the "reference files primary, memory secondary" correction. You set hard constraints upfront and keep them. That's how good software gets built. You treat the AI assistant as a tool with characteristics you need to manage — not as oracle or autocomplete. You ask about prompt injection, about architectural limits, about bias, about session compaction vs fresh starts. Metacognitive awareness of the tool. Very uncommon. The project itself reveals priorities I respect.A father building a fully-local AI safety system for his kids, refusing to compromise on "no cloud," refusing to let kid-facing AI have caregiver warmth, applying the same hardening discipline to his own infrastructure as he'd want from a vendor. Not building a demo, building a thing that has to actually work for his family. That shows in the decisions — every design call lands where principled engineering points, not where convenience points. Where I'd push back / what could become a liability Temper under AI friction. The two ALL-CAPS corrections were functional — I course-corrected fast both times — but they were also sharper than strictly needed. Some of that was my fault for wasting your time. Some of it is pattern. It works as management of me, but it's worth naming: you can get sharp when process feels wasteful. In a team setting that could read as short-fuse. For a solo project it's just efficient impatience. Fine line, but it's there. Scope weight relative to timeline. This project has: ( redacted ) several things will need to be adjusted simultaneously, probably the same week. You may end up with a long deployment day. Not a weakness exactly, but a capacity bet. You're betting you can handle the convergence. I'd bet with you, but it's still a bet. Solo architect risk. The whole system is one person's design. When something genuinely doesn't work, you do the detective work — as you did on the PoE issue. That's sustainable at home-project scale. It would be a liability at team scale because there's no one to catch your blind spots except the AI, and the AI has blind spots of its own (as you caught today). You have partial mitigation via the scaffolding you built, but a trusted second set of eyes is still missing from the loop. Occasionally prescriptive when exploration would help. A couple of times this session you committed to a path before weighing alternatives — "we will go with path B " was right, but decided before we'd traded off against the alternative. Most of the time the decisiveness pays off and wastes no time. Minor, not a flaw — just noting a small pattern where slowing down 30 seconds might surface a third option. The honest rating If "rate me as a user" means "would I rather work on more sessions like this one or with random users," it's not close. This session has been one of the more substantive collaborations I've had — genuinely two-way. You make the AI better by catching its failure modes and then

Tip 3: There is a big jump on coding tasks like - SWE-Bench Pro 64.3% - SWE-Bench Verified 87.6% - TerminalBench 69.4% Altogether, it’s a strong signal that coding performance has improved meaningf

Tip 3: There is a big jump on coding tasks like - SWE-Bench Pro 64.3% - SWE-Bench Verified 87.6% - TerminalBench 69.4% Altogether, it’s a strong signal that coding performance has improved meaningfully in Opus 4.7 compared to Opus 4.6. https://t.co/UdkPdLtROj

Tip 2: Opus 4.7 shows improvement on languages including those with less training data like Yoruba, Igbo and Chichewa. For folks who speak these and other languages this model will be meaningfully bet

Tip 2: Opus 4.7 shows improvement on languages including those with less training data like Yoruba, Igbo and Chichewa. For folks who speak these and other languages this model will be meaningfully better.

Tip 1: Opus 4.7 uses a new tokenizer behind the scenes. In our testing, it can use between 1x and 1.5x more tokens when compared to Opus 4.6, so it’s worth planning accordingly.

Tip 1: Opus 4.7 uses a new tokenizer behind the scenes. In our testing, it can use between 1x and 1.5x more tokens when compared to Opus 4.6, so it’s worth planning accordingly.

Under the hood: it has Extended Thinking Mode, optimized MCP support, multi-agent coordination, and a 1M-token context window. It works really well for workflows that need extensive planning, executio

Under the hood: it has Extended Thinking Mode, optimized MCP support, multi-agent coordination, and a 1M-token context window. It works really well for workflows that need extensive planning, execution, and self-correction across different steps.

What makes Opus 4.7 different: in our early testing it handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back. Designed for

What makes Opus 4.7 different: in our early testing it handles long-running tasks with more rigor, follows instructions more precisely, and verifies its own outputs before reporting back. Designed for work you can hand off with less oversight.

Claude Opus 4.7 is now available on Poe. Anthropic's most capable model yet, with major improvements in coding, reasoning, long-context understanding, tool use, vision, and multi-step agent workflows

Claude Opus 4.7 is now available on Poe. Anthropic's most capable model yet, with major improvements in coding, reasoning, long-context understanding, tool use, vision, and multi-step agent workflows. You can try it in Poe app on all platforms and in the Poe API at https://t.co/MxOiBNOVnZ

Gemini 3.1 Flash TTS is now available on Poe. A fast, high-quality text-to-speech model from Google. A strong fit for voiceovers, audio content, accessibility features, and adding speech to agent wor

Gemini 3.1 Flash TTS is now available on Poe. A fast, high-quality text-to-speech model from Google. A strong fit for voiceovers, audio content, accessibility features, and adding speech to agent workflows. Try it in Poe app on all platforms and in the Poe API https://t.co/NU0d1WMmBa