Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

1/3 🤖 Meet AgentOS: A Token-efficient, Microkernel AI agent with on-device model routing across CLI, Web UI, and chat. A local router reads every message on your device and sends it to the cheapest model that can still do the job well. You stop overpaying for AI. ⚡ What...

149,843 Aufrufe • vor 1 Tag •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Introducing Glidepath. A new way for builders on Bankr to take profit -- without nuking their own chart, or their reputation. The problem: Builders earn fees in their own token. The second they sell into the pool, the chart craters, holders get wrecked, and trust evaporates. And they torch their own long-term upside doing it. First -- what Glidepath is not: It doesn't pull liquidity. It never touches your pool's LP. Pulling liquidity makes trading your token inefficient and unappealing. It's your own tokens, fed back into the pool in slices so small the market barely registers them, each one sized by the Bankr AI agent to live conditions. Why that's healthy for the chart, not harmful: Every slice is a tiny fraction of pool depth, spread over time. Organic buy volume absorbs it, price can keep trending instead of taking a wick. A small, steady, absorbable flow is nothing like a full clip. It actually gets better. Once "the dev might dump" is off the table, buyers price in less risk. The overhang that caps every launch disappears. Less rug risk → stronger bid. Committing to a Glidepath can be bullish. And it's not opt‑in. Selling your fee token straight into the pool through Bankr is now turned off -- Glidepath is the only way to sell it on Bankr. So "the dev might dump" stops being a promise holders have to trust, and becomes a rule they can see. Credible commitment -- enforced, not just offered. And here's the part builders sleep on: Before you commit, Glidepath shows what that same stack is worth at higher market caps. You don't have to dump to fund your project. Grind the coin up, and the same tokens fund you many times over. Your treasury grows with your chart, not against it. Once you commit: → tokens are locked to a vesting wallet → after a short heads-up window (48hr), they exit in small slices using the AI generated sell plan → each slice capped to a fraction of real liquidity -- the AI can size under the cap, never over And it's all in the open. Your token page shows a live exit plan for everyone to see -- committed, sold, remaining -- with the exact timing fuzzed so it can't be front-run. Holders see a capped, transparent glide. No hidden float. No 3am chart nuke. Bottom line: Creators -- take profit on your terms, chart and reputation intact. Holders -- "the dev might dump" becomes a known, capped, visible number known up front. For once, you and your holders want the exact same thing: number go up. This is what launching on Bankr should mean: credible commitment, built in. Glidepath now live in your Bankr terminal

Bankr

97,476 Aufrufe • vor 29 Tagen

Introducing Pods Hyperspace Pods lets a small group of people - a family, a startup, a few friends, to pool their laptops and desktops into one AI cluster. Everyone installs the CLI, someone creates a pod, shares an invite link, and the machines form a mesh. Models like Qwen 3.5 32B or GLM-5 Turbo that need more memory than any single laptop has get automatically sharded across the group's devices - layers split proportionally, inference pipelined through the ring. From the outside it looks like one OpenAI-compatible API endpoint with a pk_* key that drops straight into your AI tools and products. No configuration beyond pasting the key and changing the base URL. A team of five paying for cloud AI burns $500–2,000 a month on API calls. The same team's existing machines can serve Qwen 3.5 (competitive on SWE-bench) and GLM-5 Turbo (#1 on BrowseComp for tool-calling and web research) for free - the hardware is already on their desks. When a query genuinely needs a frontier model nobody has locally, the pod falls back to cloud at wholesale rates from a shared treasury. But for the daily work - code reviews, refactors, research, drafting - local models handle it and nobody gets billed. And when it is idle, you can rent out your pod on the compute marketplace, with fine-grained permissions for access management. There's no central server involved in inference. Prompts go from your machine to your pod members' machines and back: all of this enabled by the fully peer-to-peer Hyperspace network. Pod state - who's a member, which API keys are valid, how much treasury is left - is replicated across members with consensus, so the whole thing works on a local network. Members behind home routers don't need port forwarding either. The practical setup for most pods is three models covering different jobs: Qwen 3.5 32B for code and reasoning, GLM-5 Turbo for browsing and research, Gemma 4 for fast lightweight tasks. All running on hardware you already own. Pods ship today in Hyperspace v5.19. Model sharding, API keys, treasury, and Raft coordinator are all live. What Makes This Different - No middleman. Your prompts travel from your IDE to your pod members' hardware and back. There is no server in between reading your data. - No vendor lock-in. Pod membership, API keys, and treasury are replicated across your own machines using Raft consensus. If the internet goes down, your local network keeps working. There is no database in someone else's cloud that your pod depends on. - Automatic sharding. You don't configure layer ranges or calculate VRAM budgets. Tell the pod which model you want. It figures out how to split it across whatever hardware is online. - Real NAT traversal. Your friend behind a home router with a dynamic IP? Works. No VPN, no Tailscale, no port forwarding. The nodes handle it. - Free when local. This is the part that matters most. Cloud AI bills scale with usage. Pod inference on local hardware scales with nothing. The marginal cost of your 10,000th prompt is the electricity your laptop was already using. Coming soon: - Pod federation: pods form alliances with other pods. - Marketplace: pods with spare capacity can sell inference to other pods.

Varun

308,089 Aufrufe • vor 3 Monaten

Fable 5 comes back!It can now build playable game prototypes. I think it is actually a signal for where AI coding is going. Making a game is not just “write some code.” Even a small browser game needs: game loop;character movement;collision logic;scoring system;UI states;physics tuning;visual feedback;bug fixing;playtesting This is why game prototyping is a great test for AI models. A model cannot fake it with a pretty answer. Either the game runs, or it does not. What impressed me about Fable 5 is that it is useful for the messy middle: turning an idea into mechanics, turning mechanics into code, debugging broken interactions, and iterating until the prototype feels playable. But here is the practical part: I would not use the strongest model for every step. For game building, I would split the workflow: 1. Fable 5 for game design + architecture 2. a fast coding model for routine implementation 3. a vision-capable model for screenshot/UI feedback 4. a cheaper model for docs, test cases, and small fixes 5. fallback when latency, cost, or output quality becomes a problem That is the real AI coding stack. Not “one magic model does everything.” More like: the right model, for the right task, at the right cost, with fallback when things break. This is why I’ve been looking at ZenMux ZenMux. ZenMux gives developers one gateway to access multiple leading AI models, with OpenAI / Anthropic / Google Vertex compatible APIs, cost tracking, quality benchmarks, auto-routing, and compensation when output quality, latency, or throughput falls short. If AI can now make games, the next question is not just “which model is strongest?” It is:how do we manage the whole model workflow Fable 5 shows the creative ceiling. ZenMux is closer to the infrastructure layer you need when AI coding becomes a real production habit.

Rachel🥥

57,766 Aufrufe • vor 13 Tagen

OpenAI's AgentKit will be so insane, build every step of agents on one platform. These visual agent builders make the whole process of iterating and launching agents far more efficient. It sits on top of the Responses API and unifies the tools that were previously scattered across SDKs and custom orchestration. It lets developers create agent workflows visually, connect data sources securely, and measure performance automatically without coding every layer by hand. The core of AgentKit is the Agent Builder, a drag-and-drop canvas where each node represents an action, guardrail, or decision branch. Developers can link these nodes into multi-agent workflows, preview results instantly, and version each setup. It supports inline evaluation so that developers can see how changes affect output before deploying. The Connector Registry is a single admin panel that manages how data and tools connect across the OpenAI ecosystem. It centralizes integrations like Google Drive, SharePoint, Dropbox, and Microsoft Teams. Large organizations can govern access and flow of data between agents securely under one global console. ChatKit provides a ready-to-use chat interface for embedding agents inside apps or websites. It manages streaming, message threads, and model reasoning displays automatically. Developers can skin the interface to match their product without writing custom front-end code. Under the hood, all these blocks use the same execution core that runs agent reasoning through OpenAI’s APIs. Workflows in Agent Builder compile down to structured instructions for the Responses API, which handles model calls, tool use, and context passing. Connector Registry handles authentication and routing for external tools, while Evals and RFT provide feedback loops that improve agents over time. This integration means developers no longer need to handle orchestration logic, model evaluation pipelines, or safety layers separately. Everything runs natively within OpenAI’s control plane with managed security, automatic versioning, and built-in testing. In short, AgentKit standardizes the entire life cycle of an AI agent—from visual design to deployment and performance tuning—inside a single unified system.

Rohan Paul

178,460 Aufrufe • vor 9 Monaten

I built a content engine that runs on telegram. Two commands... /discover: sends out to 9 sources across HackerNews, Reddit communities covering AI automation, prompt engineering, vibe coding, and specialist newsletters. Pulls everything published in the last 24 hours, runs each item through an AI extraction layer that scores it against 100+ niche keywords, deduplicates, and drops the relevant ideas into a Notion database. Takes about 90 seconds. Costs fractions of a cent. /ideas: this command pulls the top scored ideas from that database, randomizes the selection so you're not seeing the same ones every time, and sends them to you in a clean numbered list. You reply with /write 3 or whatever you choose, and the system researches the topic using Perplexity's live web search, generates three distinct outline options with different angles and hooks, saves them to a Google Doc, and sends you a message telling you they're ready. You read the outlines, and you pick one. You then reply with the command /outline 2. The system writes the full piece in your voice, following your brand guidelines, with specific examples and concrete claims. It can be done in under two minutes of your time. The whole thing runs on n8n, with no subscriptions beyond what you already use. If content takes too long or you don't have ideas, this solves that. I built this for myself; I can do it for you. If you're tired of knowing you should be posting and still not doing it, let's talk.

Savvy | Ai & Automation

14,879 Aufrufe • vor 3 Monaten