• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
  • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI

    Evan Conrad Lists Cloud Requirements for AI Agents

    Evan Conrad posted three recommendations for running AI agent projects in the cloud.

    EC
    1 Source, 24d ago, first seen 24d ago

    TLDR

    Evan Conrad, CEO and co-founder of SF Compute, which runs GPU clusters for AI workloads, tweeted a short list of features he called obvious for agent projects. He said the default should be to run in the cloud rather than on a laptop, that cloud environments should be easy to share across teams, and that cloud setups need clearer ways to avoid pasting secrets into chat. The post appears in a thread or reply discussing practical infrastructure needs for such projects.

    Combined views

    10.1K

    1 Source, first seen 24d ago

    Combined views

    10.1K

    1 Source, first seen 24d ago

    164 likes
    164 likes
    18 comments
    130 saves
    5 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    18 comments
    130 saves
    5 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    1 Source

    @evanjconradobvious things all the agent projects need: - the default should be to run in the cloud, not on your laptop, it's weird that everyone tries to push you towards running in the laptop - cloud envs should be sharable easily between your teams - cloud envs should have clearer and easier "don't paste the secret in chat" strategies. most services likely need to move to oauth-type refresh tokens with short lived ones handed to an agent - if you "search", it should search within the chats. Claude/Anthropic, why does cmd-f search chat names and not search IN the chat, how was this not fixed yesterday - Chats should live in folders or projects, and should likely be hidden in the GUI automatically if they're not used for a bit. you probably want three things: a "project", a "topic", and a "thread". Threads are single-player, topics are multi-player, and projects are multi-player. - most agents should consider baking in a repo by default, like loveable, via something like code storage or whatnot. a lot of agents are used by normies who don't have a github account or don't want to go and make a github repo in order for them to be able to collaborate with their team

    1 Source

    @evanjconradobvious things all the agent projects need: - the default should be to run in the cloud, not on your laptop, it's weird that everyone tries to push you towards running in the laptop - cloud envs should be sharable easily between your teams - cloud envs should have clearer and easier "don't paste the secret in chat" strategies. most services likely need to move to oauth-type refresh tokens with short lived ones handed to an agent - if you "search", it should search within the chats. Claude/Anthropic, why does cmd-f search chat names and not search IN the chat, how was this not fixed yesterday - Chats should live in folders or projects, and should likely be hidden in the GUI automatically if they're not used for a bit. you probably want three things: a "project", a "topic", and a "thread". Threads are single-player, topics are multi-player, and projects are multi-player. - most agents should consider baking in a repo by default, like loveable, via something like code storage or whatnot. a lot of agents are used by normies who don't have a github account or don't want to go and make a github repo in order for them to be able to collaborate with their team