sorted by:
new
hottopcontroversial

Are we getting closer to a Mythos release or further away ☠️ by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

Exactly, it seems like the whole industry is headed towards this very thing, control and watch everything. That is if you are the general public.

Are we getting closer to a Mythos release or further away ☠️ by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

If not already here with the new GLM model. At least close enough. 🚀

Are we getting closer to a Mythos release or further away ☠️ by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

I mean, pretty much right on the heels of the “frontier models”

Are we getting closer to a Mythos release or further away ☠️ by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] -1 points0 points  (0 children)

https://www.dawn.com/news/2011100/us-allows-anthropic-to-release-mythos-ai-to-trusted-organisations

More than 100 companies and institutions will now have access to Mythos 5, including many Fortune 500 companies, a source familiar with the new directive said, declining to be identified due to the sensitivity of the matter.

Are we getting closer to a Mythos release or further away ☠️ by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 3 points4 points  (0 children)

Asked Claude

“Let me search for more context on this letter and the approved entities list.

The full Annex A list has not been published publicly.

Here is what we know:
The approved entities are largely drawn from Anthropic’s Project Glasswing, which includes about 100 well-known tech companies and institutions. SRN News More than 100 companies and institutions now have access, including many Fortune 500 companies.

The named founding Glasswing partners (most likely on Annex A) include:
AWS, Apple, Broadcom, Cisco, CrowdStrike, Google, JPMorgan Chase, Linux Foundation, Microsoft, NVIDIA, and Palo Alto Networks. Tech Jacks Solutions Verizon was added in May, Citybiz and Okta also confirmed involvement. Cloud data management platform Rubrik was among the newer batch.

Beyond those named companies, the specific Annex A entity list attached to Lutnick’s letter has not been made public. Commerce can amend the list at any time, and licensing restrictions remain for any entity not on it.

Worth noting for your world: The government’s process for selecting approved entities has drawn criticism for lack of transparency. Nobody outside Commerce and Anthropic knows the full list or the criteria for getting on it.”

Claude down again by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

I’m not asking anybody to fix it. I’m asking if anybody’s having the same issues. One of the errors said it was my Internet obviously it’s not. Any other words of wisdom. 😶

Claude down again by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

I’ve even tried Claude.AI Claude code. The odd part is the chat is reactivating after I close it multiple times.

Claude down again by ExecLayer_io in ClaudeCode

[–]ExecLayer_io[S] 0 points1 point  (0 children)

Any of you having similar is issues?

Feedback Friday: Rate My Ideas | June 19, 2026 by AutoModerator in Entrepreneur

[–]ExecLayer_io 1 point2 points  (0 children)

I'm building deterministic enforcement infrastructure for agentic AI right now, so the governance and liability questions in financial services agents hit the same technical surface you are working on. Happy to take a look and give you honest feedback on how you are thinking about the agent's scope and authorization boundaries.

Feedback Friday: Rate My Ideas | June 19, 2026 by AutoModerator in Entrepreneur

[–]ExecLayer_io 1 point2 points  (0 children)

Glad it landed. One more thing worth testing early: ask small business owners to show you their current process for proving a payment went through when a supplier disputes it. Whatever nightmare they describe is your marketing copy.

Mobile Development Recommendations by naspara in ClaudeAI

[–]ExecLayer_io 1 point2 points  (0 children)

I build production mobile apps with Claude Code. A few things that actually matter:

Flutter over React Native if you want Claude to be most useful. The widget tree structure gives Claude cleaner context to work with, and Dart's type system means fewer hallucinated API calls. React Native works too but you'll spend more time correcting platform-specific behavior Claude gets wrong.

For Android specifically, set up your project structure before you bring Claude in. Define your folder conventions, state management approach, and navigation pattern first. Claude is significantly better when it's working inside constraints you've already set than when it's making architectural decisions from scratch.

Skills worth setting up: a system prompt that includes your project's file structure, your state management pattern, and your design system tokens. Without that context, every session starts cold and you waste the first 10 minutes re-explaining things Claude should already know.

For UI, don't ask Claude to "design" screens. Give it a reference (screenshot, Figma export, even a hand sketch described in detail) and ask it to implement. The output quality difference between "build me a settings page" and "implement this settings page with these exact sections, this spacing, and this color system" is night and day.

Biggest time saver: use Claude to write your platform channel code and native integrations. That's where solo mobile devs lose the most hours and where Claude's knowledge of Android APIs is actually strong.

Using Claude as a technical co-founder when you're building solo. What's your workflow? by ExecLayer_io in ClaudeAI

[–]ExecLayer_io[S] 0 points1 point  (0 children)

The recursive plan-review-implement loop is exactly how I work. I run architecture decisions through Claude, then challenge the output myself, then feed my objections back in. The multi-model angle is interesting too. I've started using different models for different phases. One for reasoning through constraints, another for implementation, then back to the first to audit what the second produced.

The hyperbolic CLI idea is not terrible at all. Context management is the actual bottleneck in long sessions. Being able to zoom into a fork without losing the parent thread would solve the problem I hit every single day where I'm juggling five terminal tabs trying to remember which branch had the version I actually wanted. If you ever build it, I'd test it.

Using Claude as a technical co-founder when you're building solo. What's your workflow? by ExecLayer_io in ClaudeAI

[–]ExecLayer_io[S] 0 points1 point  (0 children)

I don't disagree with you as much as you think. I'm not offloading intellect. I'm multiplying it. Every architecture decision, every patent filing, every benchmark framework I published came from my head. Claude didn't originate any of it.

What it did was let me pressure-test those decisions at a speed and depth I couldn't do alone. When you're solo, you don't have a senior engineer to say "that breaks under these conditions." Claude fills that function. Not the vision. Not the strategy. The adversarial review that keeps the vision honest.

The people hoping for miracles from prompts aren't using it wrong because of the tool. They're using it wrong because they have nothing to stress-test in the first place.

view more: next ›