Register and share your invite link to earn from video plays and referrals.

Search results for ExtraCoins
ExtraCoins community
One keyword maps to one global community path.
Create community
People
Not Found
Tweets including ExtraCoins
Melt away the last days of winter with a Monthly Booster! 🌞 Sizzle into the new month and claim a pack loaded with EXTRAS, including FS on Moonlight Guardian! Grab yours before Mar 1, 11:59 PM EST. 🔥 Turn up the heat 👉 #MonthlyBooster# #ExtraCoins#
Show more
Happy Constitution Day! The US Constitution is designed to realize and secure the ideals articulated in the Declaration of Independence through a system premised on the need to separate, check and balance power. The framers understood that “if men were angels no government would be necessary” and “if angels were to govern men neither internal nor external controls on government would be necessary.” The constitutional architecture has witnessed many perversions throughout recent history, including extraconstitutional assertions of authority by courts, the impotence of Congress, and the endurance of a permanent and too often unaccountable bureaucracy. But it still remains the best framework for self-government ever devised. As we celebrate 250 years of the American experiment (with 239 of those under the Constitution), we should work to usher in a constitutional renaissance that will restore that great document to its rightful place at the center of American civic life.
Show more
0
144
3.5K
544
Forward to community
extracting money from solana, robinhood chain, and arc chain and bridging it back home to hyperEVM
Extracting oil from the ground in Venezuela will be neither as cheap nor easy as the White House expects. Chevron's plan to invest $7 billion in two new fields there proves the point, says @liamdenning (via @opinion)
Show more
Extracting a probability from a doctor is one of life's unnecessary boss battles. Even if you beg them for an interval-valued subjective probability, and at that point you're basically asking for their hunch. I don't know if they get sued for giving out information or something.
Show more
0
170
1.8K
48
Forward to community
PODCAST: An AI pioneer on extracting value from technology
A common technique for distillation attacks involves extracting the model’s chain of thought. To make these attacks more difficult, we are introducing a change to the Messages API: it will no longer be possible to edit Claude's context prior to thinking blocks in a multi-turn conversation. We've done this in the least disruptive way we can: it applies only to new accounts using Fable 5.1 (distillation often makes use of large numbers of new, fake accounts), although we plan to roll out this change to all users for future model releases. We hope to find better solutions to distillation attacks in the long run.
Show more
I got this popup on my Pixel today while extracting text from an image.
# Practical and Useful Patterns for OpenAI Agent SDK 🌍 Are you extracting everything you need from agent execution results — for the next turn, UI rendering, and debugging? Understanding RunResult's surfaces lets you get maximum value from every agent run. 📌 Title: Results 🔗 URL: 🧩 Overview `RunResult` holds the complete outcome of an agent execution. It provides multiple surfaces: `final_output` for the user response, `to_input_list()` for building the next turn, `new_items` for UI rendering and audit trails with metadata, `last_agent` for continuing after handoffs, `interruptions`/`to_state()` for resumable snapshots, `raw_responses` for provider-level debugging, and `last_response_id` for Responses API chaining. 🛠 Usage Define `Agent(name="assistant", instructions="You are a helpful assistant.")` and run with `result = await input="Explain Python async/await")`. Access the final answer via ` Build the next turn's input with ` + [{"role": "user", "content": "Show me a concrete example"}]` and pass it to ` again. Iterate ` to inspect each `item.type` and ` Use `result.last_agent` to get the agent after a handoff for the next turn. If `result.interruptions` exist, save state with ` and resume later via ` state=state)`. Inspect `result.raw_responses` for model name and token usage, and use `result.last_response_id` for Responses API chaining. 🏗 Practical Patterns **final_output — User-Facing Response** `final_output` is the agent's final answer. When `output_type` is set, it returns a Pydantic model instance; otherwise, a string. Use it directly for API responses or chat UI rendering. **to_input_list() — Multi-Turn Conversation Building** `to_input_list()` converts execution results into the input format for the next turn. Append the user's new message and pass it back to ` for natural multi-turn conversations. This is the provider-agnostic approach. **new_items — UI Display and Audit Trails** `new_items` contains every item generated during execution (messages, tool calls, handoffs) with metadata. Use it for step-by-step chat UI rendering or audit logging. You can trace which agent called which tool and when. **last_agent — Continuation After Handoff** When a handoff occurs, `last_agent` returns the agent that handled the final step. Use it as the agent for the next ` call to continue the conversation with the correct specialist. **interruptions + to_state() — Pause and Resume** In human-in-the-loop workflows, save execution state as a snapshot with `to_state()` when an interruption occurs. After human approval, resume from the saved state — picking up exactly where the agent left off. **raw_responses — Provider-Level Debugging** `raw_responses` contains raw provider responses with model name, token usage, and latency data. Essential for cost analysis, performance tuning, and debugging unexpected model behavior. **last_response_id — Responses API Chaining** When using OpenAI's Responses API, pass `last_response_id` as `previous_response_id` in the next run for server-managed conversation continuation. The lightest-weight approach to multi-turn. 💡 Use Cases 💬 `final_output`: Display final answer in API responses or chat UI 🔄 `to_input_list()`: Manage multi-turn conversation history 📋 `new_items`: Step-by-step UI rendering, audit trail logging 🤖 `last_agent`: Continue conversation with the correct agent after handoff 📸 `to_state()`: Pause and resume human-in-the-loop workflows 🔍 `raw_responses`: Monitor token usage and analyze costs ⚠️ Caveats - `final_output` can be `None` (e.g., when execution ends with only a handoff). Always null-check before using it. - `to_input_list()` includes tool call history. Filter manually if the target agent doesn't need it. - `new_items` count grows proportionally with execution complexity. Watch memory usage with many tool calls. - States saved with `to_state()` are serializable, but be mindful of SDK version compatibility for long-term storage. - `last_response_id` is OpenAI-specific and not available with other providers. ✨ Master every surface of RunResult to extract maximum value from your agent executions! #OpenAIAgentSDK# #AIAgent#
Show more
Guy who launched 10 coins is mad at Trump for out extracting him