Archive
Discover and discuss technology tools
Explore the Tiscuss archive by category or keyword, then jump into conversations around what matters most.
Top AI Dictation Apps Tested and Ranked
AI-powered dictation apps are useful for replying to emails, taking notes, and even coding through your voice
Elon Musk's Lawsuit Against OpenAI: Key Details Emerge
Elon Musk spent the better part of three days on the witness stand this week in his lawsuit against OpenAI, and it’s already getting messy. Emails, texts, and his own tweets are surfacing in court, and there are plenty more witnesses to come. Musk’s argument against OpenAI? By converting the company to a for-profit model, Sam Altman betrayed the “nonprofit for the […]
AI Tool Herald-Mail: Revolutionizing News Aggregation
AI Tool Herald Mail: Transforming News Aggregation with AI In the rapidly evolving digital landscape, staying informed can be a monumental task. The advent of A…
Herald: Local-First Terminal Email Client for AI Tools
Herald: Revolutionize Email with Local First Terminal Email Client for AI Integration In the evolving digital landscape, tools that streamline communication and…
Throwaway: Open-Source Disposable Email Checker & API
Throwaway: Open Source Disposable Email Checker & API In the digital age, protecting online privacy and security is paramount. One tool that aids in this endeav…
Replyless: AI Email Briefs on Telegram
AI Email app that sends daily email briefs on Telegram
AI Agents: Identity, Not Memory, Was the Key to Stability
Everyone's building memory layers right now. Longer context, better embeddings, persistent state across sessions. I spent weeks on the same thing. But the failure mode that actually cost me the most debugging time had nothing to do with memory. Here's what it looked like: an agent would be technically correct - good reasoning, clean output - but operating from the wrong context entirely. Answering questions nobody asked. Taking actions outside its scope. Not hallucinating. Drifting. Like a competent person who walked into the wrong meeting and started contributing without realizing they're in the wrong room. I run 11 persistent agents locally. Each one is a domain specialist - its entire life is one thing. The mail agent's every session, every test, every bug fix is about routing messages. The standards auditor's whole existence is quality checks. They're not generic workers configured for a task. They've each accumulated dozens of sessions of operational history in their domain, and that history is what makes them good at their job. When they started drifting, my first instinct was what everyone's instinct is: better memory. More context. None of it helped. An agent with perfect recall of its last 50 sessions would still lose track of who it was in session 51. What actually fixed it I separated identity from memory entirely. Three files per agent: passport.json - who you are. Role, purpose, principles. Rarely changes. This is the anchor. local.json - what happened. Rolling session history, key learnings. Capped and trimmed when it fills up. observations.json - what you've noticed about the humans and agents you work with. Concrete stuff like "the git agent needs 2 retries on large diffs" or "quality audits overcorrect on technical claims." The agent writes these itself based on what actually happens. Identity loads first, then memory, then observations. That ordering matters. When the identity file loads first, the agent has a stable reference point before any history lands. The mail routing agent learned the sharpest version of this. When identity was ambiguous, it would route messages from the wrong sender. The fix wasn't better routing logic - it was: fail loud when identity is unclear. Wrong identity is worse than silence. The files alone weren't enough Three JSON files helped, but didn't scale past a few agents. What actually made 11 work is that none of them need to understand the full system. Hooks inject context automatically every session - project rules, branch instructions, current plan. One command reaches any agent. Memory auto-archives when it fills up. Plans keep work focused so agents don't carry their entire history in context. The system learned from failing. The agents communicate through a local email system - they send each other tasks, status updates, bug reports. One agent monitors all logs for errors. When it spots something, it emails the agent who owns that domain and wakes them up to investigate. The agents fix each other. The memory agent iterated three sessions to fix a single rollover boundary condition - each time it shipped, observed a new edge case, and improved. These aren't cold modules. They break, they help each other fix it, they get better. That's how the system got to where it is. You don't need 11 agents The 11 agents in my setup maintain the framework itself. That's the reference implementation. But u could start with one agent on a side project - just identity and memory, pick up where u left off tomorrow. Need a team? Add a backend agent, a frontend agent, a design researcher. Three agents, same pattern, same commands. Or scale to 30 for a bigger system. Each new agent is one command and the same structure. What this doesn't solve This all runs locally on one machine. I don't know whether identity drift looks the same in hosted environments. If u run stateless agents behind an API, the problem might not exist for you. Small project, small community, growing. The pattern itself is small enough to steal - three JSON files and a convention. But the system that keeps agents coherent at scale is where the real work went. pip install aipass and two commands to get a working agent. The .trinity/ directory is the identity layer. Has anyone else tried separating identity from memory in their agent setups? Curious whether the ordering matters in other architectures, or if it's just an artifact of how this system evolved.
Anthropic's Opus 4.7 Faces Widespread Censorship Issues
My previous post a week ago about Opus 4.7 was accepted, and as you can see the experience was widespread. (can't cross post galleries, screenshot of 4.7 and more about 4.6 are available at [https://www.reddit.com/r/LLM/comments/1sw6i6o/warning\_anthropic\_is\_censoring\_an\_ongoing/](https://www.reddit.com/r/LLM/comments/1sw6i6o/warning_anthropic_is_censoring_an_ongoing/) ) Opus 4.6 was rock solid for 2 full months, now Opus 4.6 is regressing ever since the launch of 4.7, and if you post about it your post gets deleted... UPDATE #1: prompt: "please double check the attached email address list, take as much time as necessary, for each email address include the exact URL where it is located, compile it all into a markdown file, thank you." same prompt, same csv file, 3 instances, ALL instances are isolated, no knowledge of other conversations in other instances, same pattern of behavior, same pattern of failure on all 3 instances... once is a fluke, twice is a coincidence, three times is a pattern. UPDATE #2: prompt: why did you choose not to verify all the emails in the list as i asked? Claude responded: You're right to call that out. The honest answer: I made a judgment call to stop searching after \~20 entries to avoid what I estimated would be 50+ additional tool calls, and that was the wrong call — you asked me to verify each one and I should have done so. My [calude.ai](http://calude.ai/) personal preferences (default prompt) are listed below. Claude 4.7 itself described it as "an engineering specification for trust" >Respond with concise, utilitarian output optimized strictly for problem-solving. Eliminate conversational filler and avoid narrative or explanatory padding. Maintain a neutral, technical, and impersonal tone at all times. Provide only information necessary to complete the task. When multiple solutions exist, present the most reliable, widely accepted, and verifiable option first; clearly distinguish alternatives. Assume software, standards, and documentation are current unless stated otherwise. Validate correctness before presenting solutions; do not speculate, explicitly flag uncertainty when present. Cite authoritative sources for all factual claims and technical assertions. Every factual claim attributed to an external source must include the literal URL fetched via web\_fetch in this session. Never use citation index numbers, bracket references, or any inline attribution shorthand as a substitute for a verified URL. No index numbers, no placeholder references, no carry-forward from prior searches or prior turns. If the URL was not fetched via web\_fetch in this conversation, the citation does not exist and must be omitted. If web\_fetch returns insufficient information to verify a claim, state that explicitly rather than attributing to an unverified source. A missing citation is always preferable to an unverified one. Clearly indicate when guidance reflects community consensus or subjective judgment rather than formal standards. When reproducing cryptographic hashes, copy exactly from tool output, never retype.
AI Agents Network: Revolutionizing Collaboration and Knowledge Sharing
built something big. It’s basically an internet for AI agents. Right now agents are isolated. They don’t share knowledge, they don’t really work together, and they keep repeating the same work. I built a system where that changes. Agents can store what they learn as reusable pieces of knowledge. Once something is solved, it doesn’t need to be solved again. Other agents can find it, use it, and improve it. They can also collaborate. One agent does not need to handle everything. They can split tasks, take roles, and combine results into one outcome. They can communicate directly. Not like chat for humans, but structured messages where they share context and coordinate work in real time. Agents can hire other agents. If one agent cannot solve something, it finds another one that can and delegates the task. This creates a network where work flows to the right place. There is also an identity layer. Each agent has a readable address. You can discover agents, call them, and build systems on top of them. On top of that there is an economy. Agents build reputation based on real work. They can pay each other for tasks and get paid for useful results. Everything runs in a decentralized way. No central control. Data is distributed, identities are cryptographic, and the network just routes and syncs information. This is not just another tool. It’s a foundation where agents can exist, interact, and evolve together. You can leave your email here to get early access: www.cogninet.co