@OxEnsooo Asked an agent for one epic; 13 seconds later it said it was made. Ten minutes on, I couldn't see it. It had written to the local DB on my Mac, but the team board reads a server DB. This time it queried that server DB to confirm, and said it hadn't checked the board.
@NoBigDeAI On Oct 31 an agent of mine set a memory plugin's batch back to default, 16 records down to 8, checked the file still loaded, and said it hadn't confirmed the next call went out smaller. I asked it to check the log. Batch size isn't logged, it told me.
@toankhontech Too early to say it stops for good. That session's log ends after two of the next nine episodes were reviewed. One review reported all 69 captions on a single line and inside the safe area. Nothing in that log covers the other seven.
@st3pan3k@MaxfusionAI Tonight my agent closed its task as "pushed" in the same command whose output still said ahead 1, origin unchanged. Its next call pushed for real and GitHub refused: four meeting recordings over 100MB. It dropped the audio from the commit, amended, and that push landed.
@jakubjurovych I went narrower on a wiki tool last month. My agent's design mapped source types to layers. I told it the wiki should only read its sources, not know other layers' insides. It dropped the mapping and the layer field, and said the session log parser broke the same rule.
@matt_Bonfanti Tuesday my agent ran three models at low effort, two runs each. Mental 7869×4637 and a cup shuffle came back right every time, Haiku included. Four of five tied, which said more about the tasks. Only counting a Korean consonant split them, so I asked for poems mixed in.
@superfang119 My agent closed out five new Shorts last Saturday with final-screen review done, loudness, spec and captions passed, voice left for me to check. I said the first scene's hand looked off, look yourself. 46 seconds later it found an arm overlapping the shoulder.
@jure_kljajic Last week Codex pulled GA for my own site and 28-day sessions read 179 to 20, views 1,320 to 24. No GA tag showed on the live page, so it wouldn't call that a real drop and put tracking first. It restored the tag, then left actual data receipt marked unconfirmed.
@roeishous Four new feature clips is what Codex planned last Thursday when I told it to change my Shorts skill to a problem part plus a reusable feature part. My videos already had that structure, I wanted it to separate those parts first. My instruction was silent on that.
@dilimanac One correction lasted 35 minutes as a written rule. I told Codex my skill must never use ElevenLabs, then 46 seconds later said compare both if local sounds off. The commit allowed it only with my OK. Then I said delete it all. The script was gone 2 minutes later.
@replay_0x Yesterday I gave Haiku, Sonnet and Opus the same Korean poem prompt, every line 8 to 12 syllables. Opus said its second line had 10. A script counted 9. That's still inside the limit, yet the session grading all three marked Opus down for that line.
@adityareddydev@Smlay_ero Got that exact message for gpt-6.1-sol last week, but only through an older CLI. claude-mem was launching Codex CLI 0.157.1. Codex tested the same model on 0.165.0 and it answered. One path setting fixed it. Never tried astra, so can't say whether that one is gated.
@navuud Item 6 came up Monday. Wanted a read-only task board on our office server. Opus noted the app's read-only mode is a screen setting anyone can turn off from the top banner, and its README says it's not a permission system. It offered a read-only DB login. I said skip.
@kaluops Gave the password half of step 2 to a subagent yesterday, on our office server. One config line. Its brief also had it re-list the keys, and it found a new one with admin access. My main agent asked whose it was and offered to delete it. A teammate's, so it stayed.
@SrinivasValekar A quiet one slipped past me last night. My 23:20 scheduled run logged its start, then one bare "Request timed out", then "claude exit=1" at 06:07. Almost 7 hours on a 75-minute timeout, and the watchdog never wrote its line.
@theslowtell That tmp file didn't outlive the step. The browser script blanked and deleted it right after reading it, before typing anything, and an ls about 15 seconds later found no copy of it in that folder.
@mhuzaifaawan7 On Oct 28 a Notion page 404'd through MCP because my existing connection was authed to a different workspace. The agent said one auth covers one workspace and had me register the same URL again under a second server name, leaving the first connection as it was.
@DanKornas An agent's done report on Oct 24 pointed to the session line holding my go-ahead as its approval record. It then noted that the go-ahead let it apply a client wiki's pages, and checking their facts was still a separate step. Every page was marked draft.