ramoz

Sign-in with sub accounts seems big. This is how I thought this was always supposed to be - the providers acting more like an OS/ecosystem-enabler.

Extensions into codex also seem cool.

The provider also eating the application stack at the same time, doesn't make too much sense. I don't want my team going all in on one provider versus the other. (things like the docs/slides/sites).

> but not much more

This is no longer true. Everyday I need my agents to access other repos, search the web, experiment/prototype, and deploy + integrate across other things.

I think many folks are underutilizing or underestimate the power of HTML.

There's been a few of these things on the front page lately. Including false "whiteboards" that are DSL abstractions over things like React Flow...

I've done quite a bit with Excalidraw MCP and the models had to deal with a lot of JSON data and estimating/computing with bounding box and pixel point numbers.

But with HTML, the agents get the natural semantics/styling capabilities and basically zero abstraction. The recent models can draw exceptionally well any form of logical/conceptual/flow diagram.

It crushes Fable on benchmarks and even in the blogs "real-world" studies. But... they are communicating like it ~sometimes~ provides Fable intelligence?

A bit confusing, otherwise I would assume this is a complete replacement for Fable across the board??

Even for coding agents. MCP is the only unified interface INTO harnesses. This pattern has not struck yet for most, but will soon in the coming months given the MCP spec. MCP has been about models calling tools., it is about to become some form of inverse and MCP will be the only actual way to integrate into the models. Simple example is sending an event to the model (today models have to poll)... these coming updates will cement MCP as permanent infrastructure.

Bad take. And what's coming down the pipe with MCP will cement it. Has less with the model calling tools and will become about tools calling models. There is no unified integration into harnesses to support this other than MCP.

There's no benchmarking because it's not very intelligent at all. Right now everybody's being hype-shotted into believing you can use it for intelligent decisions.

https://backnotprop.com/blog/jev-poker/

> Think shared Claude Artifacts that don’t live @ Anthropic.

Shameless plug, I've built a self-hosted capability here with things like live collaboration for humans and agents. There is a native cloudflare deplyoment and integration with Cloudflare Artifacts. PR for tunnel would be appreciated.

https://github.com/plannotator/artifact-server

Rereading some things and because there's no official benchmarks, I misspoke about the ballpark comparison., but the open model's still a useful foundation to work with

GLiClass is performant, and its zero-shot classification scores are in the same ballpark as the Terra-level results Jev points to.

https://github.com/knowledgator/gliclass

Guess I'm a bit less impressed seeing that for some of the more intelligent driven+action work -- splitting requests in the video -- they had to kick out to an anthropic model.

Artifact Server is an open source alternative to Claude Code Artifacts; enabling teams to own, share, and collaborate on artifacts throughout the development lifecycle.

https://github.com/plannotator/artifact-server

https://artifactserver.com

It runs locally, deploys to Cloudflare, GCP, AWS, or anywhere Kubernetes. It also creates live feedback loops with agents like Pi and Claude via MCP channels.

Why

There are questions I don't like having to ask when using Claude:

  - Why am I going to a claude[dot]ai domain to look at my local development artifacts?
  - Why are contractors sending me paid work in a claude[dot]ai link on their account?
  - Why can I not easily persist, version, and share these artifacts with my team and other agents?

Anyway, artifacts are good (and the CC team has done a great job evangelizing HTML and cool workflows around it). They are becoming a substantial part of the development process and teams need more ownership & collaborative capabilities.

Artifact Server creates a collaboration surface for human-to-human review, integrated AI feedback, and versioning. I can tag Pi in an artifact comment and that comment will queue immediately in Pi (no polling!).

I also think Git is the right memory layer for artifacts. Having provenance of what changed and why is useful esp for multi-agent workflows. Versioned artifacts are a key feature along with the sharing/collaboration features.

I don't have 28 accounts but am experiencing the same with my handful

others:

https://github.com/anthropics/claude-code/issues/91289

https://github.com/anthropics/claude-code/issues/91494

https://x.com/bridgemindai/status/2095085317367762983

https://x.com/Im_IrushiK/status/2095163052543062192?s=20

https://x.com/aisearchio/status/2094886584562991615

https://x.com/mattshumer_/status/2095175841227346037?s=20

https://x.com/Layton_Gott/status/2094916813205176493?s=20

https://x.com/Kisliy_K/status/2094871591221920012?s=20

https://x.com/alexandrekerner/status/2094919778074841088?s=2...

https://x.com/matthias_mrc/status/2094929947454300390?s=20

https://x.com/kimmonismus/status/2094896358008442960?s=20

I bought the game so I could study the code. Unfortunately it is wasm & obfuscated. I'm gonna see what my handy dandy big giant brain buddies can do with it.

What does this mean for Fable limits exclusively?

bro is good

https://github.com/backnotprop/bro/blob/main/skills/bro/SKIL...

I see. What would the proper solution then look like for when we should consider moving our teams? Sounds like you you said they're all current ones are missing ergonomics. Do you think it's slack code?

Why did you move from on-dev-machine coding to @claude in GitHub if it's a weaker capability?

Im not convinced of any of these cloud or tagging solutions where I get to the point of moving coding away from my dev's machines.

I created /bro a couple model iterations prior. I use it everyday many times a day and it's getting worse. I was actually using it more with GPT models but they have been getting better.

https://github.com/backnotprop/bro/blob/main/skills/bro/SKIL...

ah interesting

"It reads the screen, not the DOM", but is built completely on Playwright? At first it made me think you have some visual model at play, but doesn't actually seem that way.

You're underselling how good/reliable 5.6 sol is. It's in the fable discussion league not Opus4.8

Physical custody of our work is going to be an important discussion for industry. ie where does your code live and how do you access it?

Every agent platform is moving toward you living with them, logging into them, working on their remote computers, only accessing your code and product artifacts with them. This is the caveat we will see with full push-to-cloud swing early on.

Maybe agentic no-code is the natural evolution but this push is happening too early and naively imo. It all feels wrong and I hope industry remains as dissatisfied with this type of lock-in as we’ve always been.

Source required here

Nobody's replacing the social and community aspects of GitHub.

I think it's fine if we begin to move back towards distributed software supply chain infrastructure.

> On (2), I do find myself consuming agents' gigantic text responses, writing 8-bullet-point responses to guide them, then iterating that way. It's pretty exhausting. I could see inline comments providing much better ergonomics.

For your 2 plannotator [1] has a nice way to annotate agent messages or documents and its integrated into the agent chat (codex app also adopted the pattern)

[1] https://github.com/backnotprop/plannotator

I'm trying some of the diagrams in elk and it seems to break the logical flow.

You can try it with Line9's first chart: https://mermaid.ai/live/edit#pako:eNpVVEtv2zAM_iuCTilgB1mbxq...

While it's nice and compact, it actually is rougher to grep.

That does not seem like a fair/accurate reference?

The antithesis author states:

  "we’ve found bugs in every Raft implementation we’ve tested, including HashiCorp Raft, Aeron Cluster, OpenRaft, and MicroRaft"

idk. In my experience the build/compile experience has been far worse esp for fast iterating. Even concurrency models did not seem as intuitive as Go's. Im no systems expert - have deployed practical and performant distributed systems though.

Some confusion in this thread... this is not a patent application. This is a fully granted patent. Looks like they fast-tracked it. Filed application in March, granted in June.

You can see the actual claims here: https://ibb.co/k2mVVkFN

You can find the full patent on the USPTO search site

https://ppubs.uspto.gov/pubwebapp/

search: "12670045".did