And the killer killer issue is that even if you would manage to talk to them, their opinion will be shaped but what AI told them and AI opinion will always be perceived as superior, your real world experience and instinct will be disregarded quickly.
For some people it becomes more like a ritual, some groups of friends do it together as something social to talk about football, I think it leads in some degree to people paying attention and talking about lower rank matches :D
I've played a couple of times solo and in group but never sticked to me.
No related to the point, but what it did stick to me for one season was La Liga Fantástica from Marca ( a fantasy league on paper) when I was a child, because it had the data component, you had a budget to pick players etc, This was before we had internet broadly, if I remember correctly the paper would publish huge lists with the teams ranking or the players stats. But what I do remember was some of my best players like Zalazar :D
There are things that you can only explore and learn in those places, for obvious reasons.
I don't know his personal life goals but he's a great communicator and educator, if this decision makes him more up to date, and allows him to create even more relevant content then is something everyone will benefit. I understand the risks of being bias toward one company and not the other, but if you look at the content he created so far, he always talk principle first and specific tool later.
I think people here should give him the benefit of the doubt.
Alright, is just that your previous comments and some others sounded to me a bit too judgy, I had to re read these with a new interpretation:
> i wouldn't be surprised if he just becomes a glorified marketer for anthro.
> im also going to guess that whatever research he does ...
At first sounded like unnecessarily prejudging a person and his future efforts.
But if you say you meant everything out of respect for him, then I have to re read what you said , more as skepticism towards Anthropic than picking up on him at a personal level.
I guess what's behind is the sentiment that big companies are going to (or have already) cross ethical lines when it comes to survive and making revenue, and I can share the same concern easily. I think in this forum the majority would do.
I would just make that more explicit and separate the person from his choice, and his future work from how the company could use it, that would be a more respectful way in my view.
But is just my opinion! and I'm aware I'm might be picking on nuances that don't matter or being overly polite :D
FYI they also released FP8 quants, and those should be faster on your setup (we have the same). As long as you keep kv at 16bit, FP8 should be close-to-lossless compared to 16bit, but with more context available and faster inference speed.
That's what I though too, maybe I'm missing something or I don't fully get it.
But the human is always behind what's the difference if they go and sign up or tell an agent that they must sign up for you ?.
My best guess is that this a way of making a system talk to your agent without you knowing what they are talking about ? As a way of not exposing the real sign up method ?
Since it’s just used once, you can also just have an agent solve the captcha and then use the returned api key yourself. This has to be engagement bait.
> This is the sort of heavy-handed, tech-illiterate, authoritarian.
Totally agree with this, it's ridiculous and a shame.
I personally don't use any infrastructure provider from Spain, but you wouldn't solve any problem moving out, and also those providers are not the ones to blame or punish. Only customer connecting from Spain are affected where is the infrastructure does not solve the problem.
IPs are blocked at Spanish internet provider level, the problem would be if you have customers in Spain, but it doesn't matter where you move your infra, if your ip is in one of the affected IP blocks, customers from Spain won't be able to reach no matter in what country is placed (what happened with docker pull )
I could make agents use delve (a go lang debugger) interactively, and it worked quite well specially when models weren't as good as they are now, they could choose where to put the breakpoint and inspect variables, I found that was the only way to unlock some situations when they insisted in that "it must be working", and it wasn't, I found that giving them the empirical tools to check for themselves was the only way to unstuck them.
Another use was for them to read the logs out of your development web server ( typical npm run dev, go run .)
I could do this with tmux send-keys and tmux capture-pane, you just need to organise the session, panes and windows and tell the agent where is what.
That was my first agent to tool communication experience, and it was cool.
After that I experimented with a agent to agent communication, and I would prompt to claude "after you finish ask @alex to review your code". In the CLAUDE.md file i'd explain that to talk to @alex you need to send the message using tmux send-keys to his tmux session, and to codex I'd say "when you received a review request from @claudia do .. such and such, and when you finish write her back the result of it"
I added one more agent to coordinate a todo list, and send next tasks.
After that I got a bit carried away and wrote some code to organise things in matrix chat rooms, (because the mobile app just works with your server) and I was fascinated that they seem to be collaborating quite well (to some extend), but it didn't scale.
I abandoned the "project" because after all I found agents were getting better and better and implementing internal todo tasks, subagents ...etc plus some other tmux orchestrations tools appeared every other day.
I got fatigued of some many new ai things coming up, that and the end, I went back to just use iTerm, split panes, and manually coordinate things. Tabs for projects, panes for agents, no more than 2 agents per project ( max 3 for a side non conflicting task ) I think that is also what cognitively does not tire me.
My project name was cool though, tamex, as in tame tmux agents :)
And to comment on the submission, I think the idea has potential, I might give it a try, the key is to have low friction and require low cognitive load from the end user.
I think that's why skills after all are the thing that is going to stick the most.
after looking more into it, I must say I agree with "Why not tmux" section but
I'm missing some comments on how this tool helps reducing the context needed for operating the TUI tool, for example when using capture-pane the agent can decide how much to read, I need to dig dipper maybe it's self evident but I'd like to see upfront how using this tool impacts token usage, specially if it saves tokens compared with giving the agent access to tmux.
reply