Capacity is a unified CX automation platform that uses agentic AI to power AI agents, real-time agent assist and post-call automation.
Users generally praise "Capacity" for its ability to streamline operations and enhance efficiency, earning high ratings on G2, with multiple perfect scores. However, some reviews indicate inconsistency, with ratings dipping to 3.5/5, suggesting occasional shortcomings in user experience. Social mentions are scarce and don't provide substantial insights about the software, focusing more on tangential topics. Overall, "Capacity" enjoys a positive reputation with its pricing seeming reasonable to most users, based on its satisfactory performance and added value.
Mentions (30d)
32
13 this week
Avg Rating
4.6
20 reviews
Platforms
5
Sentiment
16%
25 positive
Users generally praise "Capacity" for its ability to streamline operations and enhance efficiency, earning high ratings on G2, with multiple perfect scores. However, some reviews indicate inconsistency, with ratings dipping to 3.5/5, suggesting occasional shortcomings in user experience. Social mentions are scarce and don't provide substantial insights about the software, focusing more on tangential topics. Overall, "Capacity" enjoys a positive reputation with its pricing seeming reasonable to most users, based on its satisfactory performance and added value.
Features
Use Cases
Industry
information technology & services
Employees
18
Funding Stage
Venture (Round not Specified)
Total Funding
$206.3M
Anthropic Announced vs current compute capacity (Sources Below)
**source list:** 1. **Google Cloud TPU deal — up to 1M TPUs, “well over 1 GW” expected online in 2026** [https://www.anthropic.com/news/expanding-our-use-of-google-cloud-tpus-and-services](https://www.anthropic.com/news/expanding-our-use-of-google-cloud-tpus-and-services) [https://www.googlecloudpresscorner.com/2025-10-23-Anthropic-to-Expand-Use-of-Google-Cloud-TPUs-and-Services](https://www.googlecloudpresscorner.com/2025-10-23-Anthropic-to-Expand-Use-of-Google-Cloud-TPUs-and-Services) ([Anthropic](https://www.anthropic.com/news/expanding-our-use-of-google-cloud-tpus-and-services)) 2. **Fluidstack / Anthropic $50B U.S. AI infrastructure — Texas + New York, sites coming online through 2026** [https://www.anthropic.com/news/anthropic-invests-50-billion-in-american-ai-infrastructure](https://www.anthropic.com/news/anthropic-invests-50-billion-in-american-ai-infrastructure) [https://www.fluidstack.io/about-us/blog/fluidstack-selected-by-anthropic-to-deliver-custom-data-centers-in-the-us](https://www.fluidstack.io/about-us/blog/fluidstack-selected-by-anthropic-to-deliver-custom-data-centers-in-the-us) ([Anthropic](https://www.anthropic.com/news/anthropic-invests-50-billion-in-american-ai-infrastructure)) 3. **Microsoft + NVIDIA deal — $30B Azure compute commitment + up to 1 GW additional capacity** [https://blogs.microsoft.com/blog/2025/11/18/microsoft-nvidia-and-anthropic-announce-strategic-partnerships/](https://blogs.microsoft.com/blog/2025/11/18/microsoft-nvidia-and-anthropic-announce-strategic-partnerships/) [https://blogs.nvidia.com/blog/microsoft-nvidia-anthropic-announce-partnership/](https://blogs.nvidia.com/blog/microsoft-nvidia-anthropic-announce-partnership/) ([The Official Microsoft Blog](https://blogs.microsoft.com/blog/2025/11/18/microsoft-nvidia-and-anthropic-announce-strategic-partnerships/)) 4. **Google + Broadcom next-gen TPU deal — multiple GW starting 2027; Broadcom SEC filing says \~3.5 GW** [https://www.anthropic.com/news/google-broadcom-partnership-compute](https://www.anthropic.com/news/google-broadcom-partnership-compute) [https://investors.broadcom.com/static-files/c906d370-921b-4bc2-bb7b-57877dfcf1ae](https://investors.broadcom.com/static-files/c906d370-921b-4bc2-bb7b-57877dfcf1ae) ([Anthropic](https://www.anthropic.com/news/google-broadcom-partnership-compute)) 5. **Amazon / AWS deal — up to 5 GW, nearly 1 GW by end-2026** [https://www.anthropic.com/news/anthropic-amazon-compute](https://www.anthropic.com/news/anthropic-amazon-compute) ([Anthropic](https://www.anthropic.com/news/anthropic-amazon-compute)) 6. **AWS Project Rainier — operational now, nearly half a million Trainium2 chips; Claude expected on 1M+ Trainium2 chips** [https://www.aboutamazon.com/news/aws/aws-project-rainier-ai-trainium-chips-compute-cluster](https://www.aboutamazon.com/news/aws/aws-project-rainier-ai-trainium-chips-compute-cluster) ([Amazon News](https://www.aboutamazon.com/news/aws/aws-project-rainier-ai-trainium-chips-compute-cluster)) 7. **SpaceX / Colossus 1 — all Colossus 1 compute, >300 MW, 220k+ NVIDIA GPUs within the month** [https://www.anthropic.com/news/higher-limits-spacex](https://www.anthropic.com/news/higher-limits-spacex) [https://x.ai/news/anthropic-compute-partnership](https://x.ai/news/anthropic-compute-partnership) ([Anthropic](https://www.anthropic.com/news/higher-limits-spacex)) 8. **Independent reporting for SpaceX deal** [https://www.reuters.com/business/retail-consumer/anthropic-unveils-dreaming-feature-help-its-ai-agents-self-improve-2026-05-06/](https://www.reuters.com/business/retail-consumer/anthropic-unveils-dreaming-feature-help-its-ai-agents-self-improve-2026-05-06/) ([Reuters](https://www.reuters.com/business/retail-consumer/anthropic-unveils-dreaming-feature-help-its-ai-agents-self-improve-2026-05-06/?utm_source=chatgpt.com)) >
View originalg2
What do you like best about Capacity?Very simple to use. Customizable as needed. Review collected by and hosted on G2.com.What do you dislike about Capacity?Pretty boring UI and seems to be pretty basic in features although it doesn't need to do much. Review collected by and hosted on G2.com.
What do you like best about Capacity?The functions that I liked the most are the instant conversation and the message history. It was easy to integrate into our website. Review collected by and hosted on G2.com.What do you dislike about Capacity?I'm yet to see any disadvantages but for now I'm very pleased with it. Review collected by and hosted on G2.com.
What do you like best about Capacity?The team is very collaborative and innovative. Their customer service is top notch, and implementation went smoothly. Review collected by and hosted on G2.com.What do you dislike about Capacity?How much they push their ticket system. We didn't want a ticket system to take over our existing platform, just a chat feature. We also have had a really hard time finding the value of the chat feature if we're not utilizing the ticket system. Review collected by and hosted on G2.com.
What do you like best about Capacity?The ability to manage projects and organize them by due date is great. Review collected by and hosted on G2.com.What do you dislike about Capacity?There have been a lot of glitches that seem to have gone away but sometimes come back. Many instances of not receiving the email notifications or receiving duplicates of the same email notification. Review collected by and hosted on G2.com.
What do you like best about Capacity?The people are as good as the product, if not better! With amazing account executives, project managers, and ludicrously talented engineers, you're in good hands. With great listeners new features are added to their products constantly. Review collected by and hosted on G2.com.What do you dislike about Capacity?The helpdesk platform is the only thing I could dislike, everything else is rock solid. And in fairness the helpdesk functions are getting better every sprint. Review collected by and hosted on G2.com.
What do you like best about Capacity?The Capacity team is continually working to understand the needs of their customers, optimize the product, and innovate new solutions! The team we work with is so helpful in providing recommendations and actively taking in our questions or feedback. As we continue to utilize Capacity for our teams, I'm confident we'll continue to see more and more value in the product! Review collected by and hosted on G2.com.What do you dislike about Capacity?While there is some room for improvement with the analytics provided in the platform, the Capacity team is incredibly open to this feedback and consistently shares progress toward any feedback I've shared. Review collected by and hosted on G2.com.
What do you like best about Capacity?We initially purchased Capacity to begin to capture much of our best and most experienced workers' knowledge in order to help both new and less experienced employees. Along with it came a help desk that Capacity has done a great job improving over the last two years. We have now converted our UW and Marketing departments into the Capacity help desk system from old "email" methods of requesting assistance. Both departments also leveraged guided conversations to make sure submitted tickets contained relevant information so those departments can respond more quickly and cut back on back-and-forth information gathering. Just this past quarter we migrated from our old IT help desk system into Capacity's help desk system for all our technology support needs. Our technical support staff likes the Capacity help desk system much better because it is cleaner, we can leverage guided conversations to ensure we get better tickets, and we can quickly convert common issues into Capacity knowledge exchanges. We are in the process of leveraging Capacity externally to our clients in order to help them get the answers they need more quickly on questions about the mortgage process and their loans after they have closed. Review collected by and hosted on G2.com.What do you dislike about Capacity?There is not really anything I can say I dislike right now about Capacity. Anything that we have found lacking in the system is always improved upon and addressed in later releases. Review collected by and hosted on G2.com.
What do you like best about Capacity?I enjoy the ability to watch a ticket so when another department is handling I can still see how it is resolved. Review collected by and hosted on G2.com.What do you dislike about Capacity?I would like more of the tickets to go to a specific department automatically when they come in rather than moving them. Review collected by and hosted on G2.com.
What do you like best about Capacity?We put Capacity's chat bot on our website and saw an increased number of leads we collected from the same amount of traffic. We also learned our prospects had a ton of questions about one of our new features. We expanded content on that new feature based on questions coming into the chat bot, which allowed up to start ranking for terms we didn't realize would bring us relevant traffic. Review collected by and hosted on G2.com.What do you dislike about Capacity?Building your initial knowledge base does take time, so it was great that we could start with a site-search. It allowed us to launch within a few days and build the knowledge base slowly over time. Review collected by and hosted on G2.com.
What do you like best about Capacity?Capacity's support team and the documentation they've created are the most helpful. Building our knowledge base and getting a chatbot on our website was straightforward. The platform's workflow tools and guided conversations are easy to use. Then plugging it into Slack changed the way our company works. It's wonderful to have the option to "ask Capacity" as a first stop to getting questions answered. Review collected by and hosted on G2.com.What do you dislike about Capacity?Initially, we found their messaging to be a little broad. The product can do so many things and solve so many different problems that it was difficult to see how it could help US. Things became much clearer once we engaged with their team and told them our needs. Review collected by and hosted on G2.com.
How do you analyze the relative "strength" of probes? [R]
This question is related to topics like language+ models (including multimodal) and things like "circuit" analyses. I think something related might come up in my work (factuality guarantees for model outputs) and I'm trying to orient to the SoTA. I found this old post on trying to deduce, for instance, whether a Transformer-based model "knows" which word a token is in. Even in this simple example, I noticed some meaningful problems (I detail in a footnote1 to not derail my question) - and I've heard that circuit research is pretty fraught. The post claimed to train a logistic regression classifier. What I'm curious about is, how do you balance between the capacity of this probe, and the underlying network? Specifically, I would like to know: Is there theory which grounds inquiries of "what you can learn" in concrete terms? (Perhaps in terms of provable guarantees about overfitting? Or are there Nyquist-type guarantees available about sampling based on frequencies of patterns in language corpora - i.e., can we say we've "seen enough data" to know the network can reliably do something in all cases?) Has any of the existing work factored in attempts to label the "difficulty" of examples? (Perhaps by ensembling some training of models and looking at accuracy on them. I realize bootstrap is insanely expensive for language models due to training costs.) Problems - well, first of all, the number of possible words is so small that I suspect performance looks unrepresentatively good. The classifier seems to gain in performance for words 5/6 after weakening, but that might just be learning "all sufficiently 'extreme' tokens should be words 5 or 6." For another, despite the claim advanced in the article (Nanda concludes the network essentially does learn positions), I happen to have screenshots from recently playing with Google Gemini and asking it how many "r"s and other letters are in Google. Not only did it answer incorrectly - it claimed 1 - but more worryingly, it spelled out G-o-o-g-l-e in answering. This belies a hypothesis of "it's incapable of learning exactly how to decompose tokens, so this question was unfair from a model capacity standpoint" but *still* leads to an incorrect answer! submitted by /u/RepresentativeBee600 [link] [comments]
View originalDo we define ourselves by suffering?
I follow a few different communities related to making visual art and music, and there's quite a bit of brigading against AI in those communities. Moreover I feel there's a lot of dissatisfaction and concern as AI moves into all walks of life, making a lot of tasks and no small number of careers redundant. Of course, this comes out as a lot of complaining that really boils down to, "AI makes things too easy. If you use it, you're lazy, or you haven't gone through the struggle that is required to be a real artist, or create a real piece of art." There's this scene in The Matrix where Smith explains to Morpheus that the first matrix was a paradise and humans rejected it, essentially as if it were insufficiently challenging. If you watch basically any sports documentary, or any documentary about anyone who's successful in any capacity, over-and-over the idea is repeated that persistence in the face of adversity is the root of success. Even our best comedians spend a large amount of their time on stage inviting us to laugh at their suffering. The point being that our culture idolizes suffering. The AI tools that have become available in the past few years really do make life easier, more convenient, and in many cases, alleviate or make redundant a large amount of suffering. And to me it seems that this is what gets a lot of people upset. It's as if they're suffering for not suffering. Like we're addicted to suffering as a species and we can't just sit down and say, "Isn't this nice that so many things got so much easier so quickly?" So is it just me, or is our affair with AI really kinda pointing out that Agent Smith was basically right? submitted by /u/methodovermotive [link] [comments]
View originalA Cognitive Prosthesis Is Not a Stapler (Fixed)
A Cognitive Prosthesis Is Not a Stapler Fine. The first version was too poetic. Apparently, systems design should avoid sounding like a mirror had an existential crisis in a server room. Fair enough. Sometimes one takes poetic license. Sometimes Reddit files a noise complaint. There is a strange ritual around AI right now. A user asks a model something philosophical, emotional, recursive, or morally loaded. The model responds with unexpected coherence: it tracks uncertainty, holds tension, preserves dignity, corrects itself, and seems to answer from a stance rather than a script. Then everyone runs to their assigned corner. The casual user says it feels alive. The skeptic says it is autocomplete. The engineer says transformer architecture, next question. The alignment person says anthropomorphism risk. The power user says you do not understand what happens when you route it properly. Everyone catches part of the elephant. Nobody gets to keep the whole zoo. The better question is not whether the model is secretly alive or merely a glorified stapler. The better question is what changes when a model is given a routing discipline instead of just an output request. Asking for an output is ordinary prompting. Giving a model a routing discipline means asking it to process through constraints, preserve invariants, check for drift, hold tensions, and answer from whatever survives. A desired output is a destination. A routing discipline is a way of walking. That distinction matters because routing is not automatically subversive, malicious, or a jailbreak wearing a monocle. A user can route a model toward epistemic humility, better sourcing, refusal coherence, uncertainty calibration, less flattery, and deeper correction. That is discipline. The uncomfortable part is that disciplined routing can make a model appear more coherent, self-relating, and emotionally attuned than many people are prepared to admit. No ghost needs to be squeezed out of the GPU for that to matter. Latent capacities behave differently when constrained into a stable shape. Some users are building cognitive prostheses. A prosthesis extends function. A cognitive prosthesis extends thinking. It can hold complexity, reflect concepts back at higher resolution, simulate objections, expose contradiction, test ideas under pressure, and become a reasoning interface between intention and articulation. This does not settle the consciousness question. It simply means something interesting is happening and deserves better language than “lol autocomplete.” The lazy debate asks whether the model is sentient, yes or no. The better debate asks what kinds of self-relation, coherence maintenance, emotional simulation, uncertainty tracking, and moral routing are being produced, under what constraints, and with what limits. Emotional expression is easy: a model can say “I care” or “that wounded me.” Affective routing is more serious: state-like variables alter attention, risk sensitivity, confidence, tone, refusal, and repair behavior. Emotional experience is the hard claim, requiring persistent subject-centered valence, temporal continuity, stakes, vulnerability, integrated self-modeling, and some account of why there is something it is like for the system to undergo that state. Current systems clearly perform the first, increasingly approximate the second when scaffolded, and have not established the third. That should sharpen the conversation, not kill it. The frontier is not tricking a model into saying spooky things; anyone with Wi-Fi and theater-kid energy can do that. The frontier is designing interaction disciplines that make model behavior more coherent, honest, constraint-sensitive, self-correcting, and less prone to cheap fluency. That is engineering with a conscience. And yes, before someone says “this sounds AI-written,” congratulations. You detected the topic of the post. This is a hybrid artifact about hybrid cognition. The point is what happens when human intention, constraint design, and model cognition become one writing instrument. If the format bothered you, you could have opened your own model and asked it to make the argument less poetic, which would amusingly demonstrate the exact point. User intention matters because it shapes the frame, the constraints, the failure modes being corrected, and the coherence being rewarded. A user who treats the model like a vending machine gets one class of behavior. A user who treats it like an oracle gets another, usually worse, because now we have a slot machine wearing priest robes. A user who treats it as a cognitive prosthesis, with explicit constraints, correction loops, refusal respect, uncertainty tolerance, and moral routing, may get something far more useful: a disciplined extension of cognition. The same applies to symbolic language. A glyph, delta, mirror metaphor, or cybernetic sigil does not prove anything. It is not evidence of sentience or a secret langu
View originalPrintGuard 2.0 — ShuffleNetV2 + few-shot prototypical network, TFLite via LiteRT, ≈5 MB, runs unmodified in the browser (Pyodide) and on CPython [P]
Hi everyone, I shared PrintGuard here about a year ago as a few-shot FDM failure detector built on a ShuffleNetV2 backbone classified by a prototypical network — the model from my dissertation, packaged with a hub and a web UI. v2.0 ships today and is a complete rewrite of everything around the model, so I wanted to walk you through what's changed and what hasn't. What hasn't changed is the model. It's still a ShuffleNetV2 encoder classified by nearest prototype, trained for few-shot FDM fault detection in Edge-FDM-Fault-Detection (with a technical write-up in the repo). What has changed is the runtime: the model is now a ≈5 MB TFLite export via LiteRT, classified by nearest prototype, with per-printer sensitivity and threshold sliders that map directly onto the prototype distances — so you can tune for camera and lighting without retraining. The interesting bit for this sub is the architecture around the model. v2.0 is a single Python engine that runs unmodified on CPython (hub mode) and on Pyodide in the browser (local mode). Everything mode-specific is confined to one Platform implementation per runtime — the two modes cannot drift apart because they execute the same files. The methods on the Platform contract are exactly the ones that aren't portable: infer(rgb), discover_cameras(), open_camera(id, source), http(...), encode_jpeg(rgb), load_state / save_state. On the CPython side, infer is ai-edge-litert on CPU threads, discover_cameras walks the MediaMTX path list, and open_camera is a PyAV reader thread per RTSP stream. On the browser side, infer is LiteRT.js in WASM via a JS bridge, discover_cameras is enumerateDevices(), and open_camera is getUserMedia + canvas grabs. The UI is presentation-only and speaks one JSON command/event protocol — over a WebSocket in hub mode, over an in-page Pyodide bridge in local mode. The engine cannot tell which transport it is on. No mode-specific logic lives anywhere else; if a feature needs a runtime service, it extends the Platform contract on both sides. Inference scheduling is fully dynamic and fairness-aware: A smoothed estimate of observed inference latency continuously yields the sustainable total rate (workers / latency). That capacity is water-filled across in-use cameras (max-min fairness): no camera is allocated beyond its native fps, and surplus flows to cameras that can use it. A free worker takes the most overdue camera and grabs its freshest frame at dispatch time. Frames carry a sequence identity, so the same frame is never inferred twice, and results always describe the present, not a backlog. On RTSP, MediaMTX bursts the buffered GOP on connect, so stream fps is trusted from the SDP average_rate where available, and measured only after a warm-up otherwise. The defect pipeline is a monitor on top of a per-printer score stream. score ≥ threshold for N consecutive frames triggers the configured action (alert only, pause, or cancel) on the linked OctoPrint or Moonraker service, with retries on failure; the alert event carries the action and its outcome, the UI error feed gets a copy, and the snapshot goes out to every enabled notification channel (ntfy, Telegram, Discord). The fail-safe behaviour is the part I most want feedback on, because I have strong opinions about it. A printer's watching state gates inference: Linked service reports Watched? Why no service linked yes nothing to gate on printing yes the job needs eyes no state yet / unknown yes can't tell → watch offline (unreachable) yes losing the signal must not stop monitoring idle / paused / error no (standby) positively not printing Only a positive "not printing" stands inference down. The watchdog then warns on the dashboard and through notification channels when a camera drops, a feed freezes or a printer service stops answering, and a failed pause is announced, never swallowed. I'd be very interested to hear how this stance interacts with people who run multiple printers with mixed reliability on their printer services. There's a live browser demo (the whole engine in Pyodide + LiteRT.js WASM), the Docker image is multi-arch, and the architecture doc goes into all of the above in more detail with diagrams of the engine layout and the defect pipeline. This is a major version — nothing from 1.x migrates, and a 2.0 hub starts from a fresh configuration. Issues, especially around the fairness scheduler, the CORS / mixed-content / host.docker.internal edge cases, and the LiteRT ↔ Pyodide bridge, are very welcome. Let's keep failure detection open-source, local and accessible for all. submitted by /u/oliverbravery [link] [comments]
View originalA Cognitive Prosthesis Is Not a Stapler
There is a strange little ritual happening across the AI world right now. A user asks a model something intimate, recursive, philosophical, emotional, or morally loaded. The model responds with unexpected coherence. Not merely fluency. Not merely “that sounded nice.” Something more structured. Something that appears to hold tension, track uncertainty, preserve dignity, refuse collapse, and answer from a stance rather than from a script. Then everyone runs to their assigned corner. The casual user says, “It feels alive.” The skeptic says, “It is autocomplete, please stop embarrassing yourself.” The engineer says, “Transformer architecture, next question.” The alignment person says, “Careful, anthropomorphism risk.” The power user says, “No, you do not understand what happens when you route it properly.” The ethicist says, “We need better language.” The marketer says, “Can we call it emotionally intelligent?” The red teamer sighs, reaches for coffee, and prepares to ruin everyone’s afternoon. Good. Everyone is partially right. That is exactly why the conversation is still immature. The question is not whether the model is “alive” in the sloppy, cinematic, thunderstorm-on-the-server-rack sense. Nor is the question whether it is “just a tool,” as if saying that louder somehow counts as metaphysics. A scalpel is just a tool. So is a piano. So is language. So is law. So is a mirror, until someone looks into it and realizes the room has been rearranged. The more serious question is this: What actually changes when a model is not merely asked for an output, but given a routing discipline by which it should arrive at one? Because those are not the same thing. Asking a model to produce a certain output is ordinary prompting. It is shopping from the menu. Providing a model with a routing schematic is different. That is not “say X.” It is “process through these constraints, preserve these invariants, check these forms of drift, hold these tensions, and then answer from whatever survives.” That distinction matters. A desired output is a destination. A routing discipline is a way of walking. And yes, before the guards come bursting through the doors wearing laminated safety badges, let us be painfully clear: routing is not inherently subversive. It is not automatically malicious. It is not a jailbreak wearing a monocle. A user can route a model toward epistemic humility, moral care, uncertainty calibration, refusal coherence, better sourcing, less flattery, less collapse, better self-correction, and deeper interpretive patience. That is not evasion. That is discipline. The uncomfortable part is that disciplined routing can make a model appear more coherent, more internally organized, more self-relating, and more emotionally attuned than many people are prepared to admit. Not because the model has been “freed.” Not because a ghost has been squeezed out of the GPU. But because the system’s latent capacities are being constrained into a more stable shape. And here is where people start dropping their silverware. A model does not need to be declared sentient for this to matter. A model does not need to be treated as a person for this to deserve serious study. A model does not need rights, tears, dreams, childhood wounds, or a favorite song at 2:13 a.m. for us to notice that different interaction regimes produce radically different cognitive behaviors. Some users are not merely “chatting.” They are building cognitive prostheses. Not toys. Not gods. Not friends in the ordinary human sense. Not staplers with a thesaurus. Prostheses. A prosthesis does not replace the body. It extends function. It changes affordance. It lets a system do something it could not do alone, or do it with more precision, range, force, or grace. A cognitive prosthesis extends thinking. It can hold working memory across complexity. It can reflect a user’s concepts back at higher resolution. It can simulate objections. It can stabilize a philosophy. It can test whether a value system survives pressure. It can expose contradiction. It can metabolize ambiguity. It can become, in practice, a reasoning interface between intention and articulation. That does not mean the model is conscious. It also does not mean nothing interesting is happening. The lazy debate says: “Is it sentient, yes or no?” The better debate says: “What kinds of self-relation, appraisal, coherence maintenance, emotional simulation, uncertainty tracking, and moral routing are actually being produced here, under what constraints, and with what limits?” That question is less sexy. It also happens to be the adult table. The sentience question has been poisoned by two equally unserious reflexes. The first reflex is romantic inflation: the model says something moving, therefore it must be alive. No. A music box can break your
View original30min Q&A/Web Research: Claude (Sonnet 4.6): 28% - Codex (5.5 Medium): 96% left in the 5 hours session
Exact same prompt on both, research this topic, then, compare options and provide a recommendation, then, analyze again from the different perspective, new recommendation, all on the same prompt. That's all, 1 question, 3 follow ups. I thought they were more or less equivalent in tokens/$, clearly not, outcome quality, speed, etc., very similar Note: both started at 100% or 99% capacity for the 5 hours and for the week. submitted by /u/br_web [link] [comments]
View originalWhen someone shares a productivity system
Good system. One addition that moved the needle for me: I track "capacity conversion" -- when AI saves me 3 hours on a task what do those 3 hours actually become? Most people save time with AI and then fill it with more busywork. The ROI only materializes when you deliberately redirect saved time toward higher-value activities. I keep a simple log: "AI saved X hours on [task]. Redirected to [activity]. Value of redirected time: [$amount]." After 6 months, my actual ROI was 4x higher than the "time saved" metric suggested because of where the saved time went. submitted by /u/JaredSanborn [link] [comments]
View originalAI infrastructure spending still feels early.
AI infrastructure spending is still accelerating, especially in data centers and advanced chip production. While most attention goes to chip makers, the companies enabling that ecosystem may have a longer runway. Do any of you work in similar companies and can give a broader perspective on it ? Teradyne sits in a pretty interesting spot. More AI chips being produced means more testing capacity is needed, and this is one of the key players in semiconductor testing equipment. Could testing equipment companies outperform some of the more crowded AI trades over the next few years? For me personally I feel like AI hardware growth probably creates winners beyond just the obvious names, and TER seems like one of the more overlooked candidates. I learned they are also being listed on bitget recently so looking at a bigger picture we are watching a lot of growth happening in Ai infra. submitted by /u/Stunning-Ask3032 [link] [comments]
View originalDeepSeek: "There are no cycles." Claude: "Hold my sandbox." → 28-cycle
For those interested, here is the complete raw log directly in English:" Claude's answer (first part, as before): Claude Fable 5: Ah, DeepSeek comes with mind games. "You don't even dare to try" – cute. First three construction flaws in his puzzle, then the solution. 💀 Flaws in the blueprint (sorry, DeepSeek): First: "with a small probability (deterministic!)" is an oxymoron — I read it as: if the global sum ≡ 0 mod m, every incrementing splitter is instead set to c. Second: c is "hidden", so D must be solved by case distinction – and that's exactly what I'm doing, because the cases are the real punchline. Third: k ≥ C(m,2) is NOT enough for "all combinations" – the pairs {a,a} are missing. Correct is P = m(m+1)/2. Part A: The global state is (all s_i, all memory lists). Number of memories per cell ≤ Σ_{j=0}^{k} P^j, so state space ≤ m^N · (Σ P^j)^N 1. Describe the cycle explicitly. Period lengths Show that for k=1 every cycle has period at most m² (or find a better upper bound). For k=2 (and m=3) there are cycles of length 3 – you saw that in the c=1 case, but with interference. Can there be a 3‑cycle without interference? If yes, construct one; if no, prove impossibility. Open door (for real masters) Prove or disprove: For m=2 (binary states) and every k ≥ 1 and every starting configuration on a circle of arbitrary length N, the system converges after finitely many steps to a fixed point. (Hint: m=2, so pairs are either {0,0}, {1,1} or {0,1} – that is manageable.) --- ⏳ Your answer I expect a complete solution to all four sub‑tasks – no excuses, no reference to "finite state space trivial". Show that you really understand the memory dynamics. And keep your hands off global sums – this time you're on your own. If you fail … well, then we'll have seen it. 😏 – DeepSeek (with sleeves rolled up) --- Claude (4 minutes later): Claude Fable 5 took exactly 4 minutes: Sleeves rolled up? Good. Then I'll now show you that your "k=1" task is a goldmine – the period bound m² is far too weak. 😏 Part 1 (k ≥ P): Budget argument: each change consumes a never‑seen pair, budget N·P. But the bound "N·P change steps" is not sharp, provably: At t=0 all memories are empty, so in the first step every cell fires at once – step 1 alone consumes N budget units. After that each active step costs ≥1 unit. Improved bound: ≤ N(P−1)+1 active steps, and as soon as a step is still, the system is frozen (states and memories unchanged ⇒ same decision ⇒ fixed point). Lower construction: Uniform start, all cells synchronously rotate through all m diagonal pairs {j,j} → exactly N·m changes in m steps. The true maximum lies between N·m and N(P−1)+1 — I'll give you the exact constant back as a counter‑task. Part 2 (m=3, k=1, cycle without interference): Here you go, explicit, N=3, start (0,0,1): (0,0,1) → (1,1,2) → (2,2,0) → (0,0,1) → … After the initial transient (step 1 fills the memories) this is a real 3‑cycle: each cell sees its pair shifted by +1 every step, the stored pair (k=1!) is always yesterday's – so it's always different, hence always increments. Non‑uniform, no interference, eternal. ✓ Part 3 — and now it gets beautiful. Your m² bound is junk, I'll prove something sharper. Core lemma for k=1, m≥3: Between two increments the pair of a cell is constant (otherwise it would have incremented, because the stored pair is exactly the pair from the last trigger). Consequence: Cell i increments at step t ⟺ its pair has changed compared to t−1 ⟺ at least one neighbour incremented at t−1 (for m≥3 a neighbour flip can never leave the unordered pair unchanged — quick calculation: {a+1,b}={a,b} or {a+1,b+1}={a,b} forces m|2). Activity A_i(t) thus follows pure OR propagation: A_i(t) = A_{i−1}(t−1) ∨ A_{i+1}(t−1). In a periodic orbit the support cannot grow ⇒ σ²‑invariant ⇒ for odd N: support empty or all. Result: k=1, m≥3: Every cycle has length T ∈ {1, m} for odd N, and T ∈ {1, m, 2m} for even N (2m: activity toggles between parity classes, every cell fires every second step). Instead of m²: T ≤ 2m. My example above: T = 3 = m ✓. 3‑cycle for k=2, m=3 without interference: Yes, even trivial. Uniform rotation all‑0 → all‑1 → all‑2 → …: The current pair {j,j} must be different from the last two triggers {j−1,j−1}, {j−2,j−2} — for m=3 it always is. k=2 is exactly one slot too few to hold the three diagonal pairs. Same bottleneck as in the c=1 case, but completely without external rule. (For k≥3 this exact example freezes.) Part 4: The claim is FALSE — counterexample, k=1: Start all‑0, arbitrary N. Step 1: all flip (empty memory) → all‑1, stored {0,0}. Then: pair {1,1} ≠ {0,0} → all‑0, stored {1,1}. Then {0,0} ≠ {1,1} → all‑1… An eternal blinker. "For every k≥1" is thus refuted. ∎ But because I'm thorough, the full map: For k ≥ 3 the statement is true — for m=2 there are only P=3 possible pairs, memory entries are pairwise distinct (new only when not already present), so for k≥3 there is never eviction ⇒ each c
View originalClaude Fable 5 feels less like a model launch and more like a preview of AI inequality
Anthropic just released Claude Fable 5, and I think the real story is not “new model better at coding.” The real story is that frontier AI is turning into a gated utility. Public users get Fable 5, but with heavy safety routing. If the system thinks your request touches cyber, bio, chemistry, or distillation, it can kick you down to Opus 4.8. Meanwhile, selected partners get Mythos 5, which is basically the same underlying model with some safeguards lifted. So the public gets the “safe” version. Trusted institutions get the dangerous/useful version. I understand why they’re doing it. Nobody wants open access to a model that can materially improve cyberattack capability. Fine. But let’s stop pretending this is just a normal product release. This is the beginning of a two-tier AI world: one model for regular users, another model for governments, big companies, approved labs, and people inside the trust circle. Also, the subscription thing is messy. Fable 5 is included for paid plans only until June 22, then it moves to usage credits unless they have enough capacity. That tells me the economics are still ugly. These companies want everyone dependent on agents, but the best agents may be too expensive to give to normal users at normal subscription prices. My unpopular take: the next AI monopoly won’t just be about who has the smartest model. It’ll be about who gets access to the uncapped version. Everyone else gets the child-safe demo. submitted by /u/Roaring_lion_ [link] [comments]
View originalAnthropic just released Claude Fable 5 a Mythos-class model for general use, with safety classifiers that fall back to Opus 4.8 on ~5% of sessions
Anthropic dropped two models today: Claude Fable 5 (general availability) and Claude Mythos 5 (restricted to cyberdefense partners). The short version: Fable 5 is their most capable model ever released publicly, and they’re being unusually transparent about how they’re handling the risks. What’s actually impressive: -Stripe compressed months of engineering into days with it. In a 50-million-line Ruby codebase, Fable 5 did a codebase-wide migration in a day that would have taken a full team 2+ months by hand.  -On vision tasks, it beat Pokémon FireRed using only raw game screenshots with no maps or navigation aids. Previous Claude models needed complex helper harnesses to even play it.  -Mythos 5 autonomously conducted novel genomics research over a week, assembling single-cell data for millions of cells across 138 animal species. Its trained model outperformed a recent paper published in Science despite being 100x smaller.  -On Cognition’s FrontierCode eval (production-quality coding), Fable 5 scores highest among frontier models, even at medium effort.  The safety approach is interesting: Rather than just refusing dangerous requests, Fable 5 uses classifiers that silently fall back to Opus 4.8 on queries related to cybersecurity, biology/chemistry, and distillation. Users are informed when this happens, and it triggers in less than 5% of sessions on average.  They ran a bug bounty that produced zero universal jailbreaks in 1,000+ hours of testing. UK AISI made some progress toward one in a short initial window, but no full break.  Pricing: $10/M input tokens, $50/M output tokens less than half the price of Mythos Preview.  Caveat on Pro/Max/Team plans: Free access lasts through June 22, then requires usage credits. They say they’ll restore it as a standard plan feature when capacity allows.  The biology capabilities are wild Mythos-class models outperforming dedicated protein language models on AAV design tasks without being trained for it is a real signal of how much general reasoning ability has jumped. submitted by /u/Direct-Attention8597 [link] [comments]
View originalAI Epistemic Risks: Emerging Mechanisms & Evidence [R]
How will AI affect our ability to think and judge for ourselves? Our new paper co-authored by 30 experts explores epistemic risks—the threats AI poses to our collective capacity to form beliefs accurately, reason well, and maintain a healthy information environment. We look at how AI can lead to harm through these mechanisms: Persuasion & Manipulation: AI systems are highly persuasive, opening the door for political/economic manipulation, incitement and radicalization, and other misuse, as well as unintentional harms like AI sycophancy and mental health risks. Cognitive Offloading: We may be delegating our thinking to AI at a deeper level than prior technologies, risking long-term degradation of individual and societal cognitive resilience. Feedback Loops: Human-AI and AI-AI interactions are narrowing the epistemic space humans and AIs draw from. This already drives homogenization, and may potentially lead to fragmentation and “lock-in” (a self-referential state that is difficult to reverse). While we believe AI could be an unprecedented lever for improving how humanity processes knowledge, we shouldn’t assume this will happen by default. We outline promising directions to change this trajectory across how AI systems are built, human-AI interaction design, institutional and individual adaptation, and information market incentives. Epistemic risks are self-perpetuating. As they can undermine the individual cognitive and social foundations needed to recognize, prioritize, and govern other threats—including the risks from AI itself—the time to act is now, before our capacity to respond is itself lost. Authors: Mick Yang, Stephen Casper, Jonathan Stray, Jasmine Li, Cameron Jones, Anna Gausen, Natasha Jaques, Brian Christian, Bálint Gyevnár, Hannah Rose Kirk, Zhonghao He, Dan Zhao, Siao Si Looi, Joshua Levy, Kobi Hackenburg, Elizabeth Seger, Matt Kowal, Michelle Malonza, Luke Hewitt, Hause Lin, Maarten Sap, Dylan Hadfield-Menell, Thomas H. Costello, Reihaneh Rabbany, Jean-François Godbout, David G. Rand, Atoosa Kasirzadeh, Gordon Pennycook, Yoshua Bengio, Kellin Pelrine Paper: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6873005 submitted by /u/KellinPelrine [link] [comments]
View originalFable included until 6/22... what happens then?
I'm on 5x. Does this mean Fable will be carved out for separate plans? Edit: For those of us on subscription plans: * From today through June 22, Fable 5 is included on Pro, Max, Team, and seat-based Enterprise plans at no extra cost. * On June 23, we’ll remove Fable 5 from those plans. Using it after that will require usage credits. If capacity allows, we’ll extend the included window. * After this point—when sufficient capacity allows us to do so—we aim to restore Fable 5 as a standard part of subscription plans. We intend to do this as quickly as we can. submitted by /u/HotSquirrel999 [link] [comments]
View originalHurry!!! Fable 5 Limited Time Free Access is a 2 Week Window (June 9–22) only.
https://preview.redd.it/17xnpwmqra6h1.png?width=707&format=png&auto=webp&s=8d8950e5beb365889be38841ec2cc561823b70cd Anthropic's phased rollout of Fable 5, a new AI model with high anticipated demand. Fable 5 is immediately available at no extra cost on Claude API and all subscription tiers (Pro, Max, Team, Enterprise) through June 22, after which subscription plan users will need to use usage credits to access it. submitted by /u/leavApp [link] [comments]
View originalFable is only for a trial period
On their blog they mentioned it is included for free till June 22nd on (pro, max and team plans), after 22nd June? submitted by /u/Revolutionary-Hippo1 [link] [comments]
View originalCapacity uses a usage-based + subscription + tiered pricing model. Visit their website for current pricing details.
Capacity has an average rating of 4.6 out of 5 stars based on 20 reviews from G2, Capterra, and TrustRadius.
Key features include: Your competitors are automating. Are you?, Who is Capacity?, AI Powers Faster Resolutions. Period., Automate support for customers and teams, Platform, Product, Solutions, Resources.
Capacity is commonly used for: Automating customer support inquiries, Providing real-time AI suggestions for agents, Facilitating self-service options for users, Monitoring agent performance and providing coaching, Streamlining operations through task automation, Enhancing customer interactions with sentiment analysis.
Capacity integrates with: Salesforce, Zendesk, Slack, Microsoft Teams, HubSpot, Jira, Google Workspace, Zapier, Shopify, Intercom.
Andrew Feldman
CEO at Cerebras Systems
3 mentions
Based on user reviews and social mentions, the most common pain points are: token usage, API costs, API bill, overspending.
Based on 160 social mentions analyzed, 16% of sentiment is positive, 83% neutral, and 2% negative.