Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Vorflux has opened its new cloud platform, allowing users to run tasks from a plan to a merged PR on a dedicated machine. It can plan, build, test, and review on its own. > Diff reviews are done by a different model family than the one that wrote it...

12,162 Aufrufe • vor 1 Monat •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 Aufrufe • vor 8 Monaten

How Did Pi Network Build a Huge User Base Before it Had a Fully Open Blockchain? Launched in 2019 by Stanford graduates, Pi (Pi Network) made crypto participation possible through a smartphone app instead of expensive mining hardware. But what exactly made its model different? (1) It made mining accessible through smartphones. Pi allowed users to earn Pi by checking into the app and starting a mining session. The process was designed to consume very little battery and computing power compared with traditional proof of work mining. This removed one of the biggest barriers to crypto mining, expensive hardware and high electricity costs. (2) It turned users into part of the network's growth engine. Pi introduced referral bonuses that encouraged existing users to invite friends and family. Users could also build security circles by adding people they trusted to the network. This created a built in growth mechanism that helped Pi expand its community rapidly. (3) Early Pi mining was not traditional blockchain mining. Before Open Network, users were not securing a public blockchain through conventional proof of work mining. Instead, the mobile app helped establish user participation and prepare the ecosystem before the network became publicly accessible. (4) Pi built the community before opening the network. Pi spent years operating through different development stages before launching its Open Network in February 2025. A firewalled Enclosed Mainnet had already gone live in December 2021, giving the project a working but closed blockchain years before it opened externally. During that period, the project focused heavily on growing its user base and developing its ecosystem. This flipped the usual crypto growth model, where networks often launch first and try to attract users afterward. (5) The Open Network changed what users could actually do. With Open Network, Pi became externally connected to the broader blockchain ecosystem. Users were now able to engage with Pi beyond the closed system it had been previously in, while developers were free to create applications on the network. This made the token and its massive community more realistic.

BSCN

43,622 Aufrufe • vor 19 Tagen

this is f*cking beyond comprehension. Google engineers just shipped the entire agent lifecycle in one release: build, scale, govern. and every piece answers a specific way agents die in production > context layers (Static, Turn, User, Cache): you decide what the model carries between turns, so token spend stops being a mystery > a self heal plugin: the agent notices a tool call failed and retries it a different way instead of dying mid run > adk deploy: one command from your laptop to the managed runtime, no packaging, no infra ticket > Go joins Python and Java, with its own A2A SDK then the part nobody builds for themselves: > a dashboard on token consumption, latency, error rates and tool calls: the four things that actually kill an agent > a traces tab that opens the real sequence of actions the agent took, step by step > a playground wired to the deployed agent, past sessions included, so debugging is not a redeploy loop > an Evaluation Layer with a User Simulator, because you cannot unit test a non deterministic system and the part that decides whether it ever ships: > agents get native identities as first class IAM principals: least privilege applies to them like it does to people > Model Armor screens prompt injection, tool calls and responses, inline for Gemini or over REST > Security Command Center inventories every agentic asset and flags data exfiltration by an agent ADK is already at 7 million downloads. the runtime has a free tier, and express mode runs off a Gmail address. the prototype was never the hard part.

NO1ennn

24,666 Aufrufe • vor 16 Tagen