Sacramento. Home Depot parking lot. Federal agents rolling an enforcement op in the California sun. One guy read the scene and missed the statute. He thought this was theater: sanctuary state, phone out, slash the tire, walk off a hero. One hiss. Rubber gone. He turned like the bit was over. The people behind him did not come to debate whether immigration is a human right. Camo, masks, plates. In a few seconds the activist became a ragdoll on hot asphalt. Pepper spray painted his beard and eye sockets orange—clear on camera. His wife screamed that he was a U.S. citizen. The agents did not pause. Citizenship is not a coupon for vandalizing a federal vehicle. They drove the wounded SUV off on its rims. The operation did not stop. Same sweep, people in cuffs, including a Mexican national with sixty-seven California jail bookings and a fentanyl record. Nobody in that lot bought an extra minute of freedom with a knifed tire. That is the line on the post: This is what I voted for. Not voting for street court against federal officers. Voting for this: you put a blade in the tool they use to do the job, they put you on the pavement. California can write sanctuary memos. A Border Patrol vehicle is not a prop on your driveway. Slashing the tire is damage to government property. The spray in the face is what happens when you run. It is not a snuff film. Someone online will type “excessive force.” Usually the someone who was not in the chase and did not pay for the tire. The satisfaction is short and simple. For four years obstruction was performance art. The show is over. Handcuffs. Chili in the eyes. The hero bit lasted seconds. The tire lasted less. The clip is shorter still. The part where he goes into the car—that is the feature.

Today a crazy quantum story just got wilder. On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures. But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first! As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise. Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours. Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure. Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice! The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :) Part 2: neutral atoms and qday The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers. Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low. Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts. My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom". Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions. So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030. Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years. Part 3: post-quantum cryptography There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation. These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer. The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security. Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.

Why do Vermont and New Hampshire look like a square that's split at an angle? They look like a square cut on the bias because they were never designed as two states. They were one contested colonial claim, then sliced by a river. Put Vermont and New Hampshire together and the outline is roughly a block: Canada on the north (the 45th parallel), Massachusetts on the south, New York on the west, Maine and a sliver of Atlantic on the east. That outer box is the leftover of 17th- and 18th-century English land grants. The slash through the middle is the Connecticut River. New Hampshire began as a coastal grant. In 1629 John Mason received the land between the Merrimack and Piscataqua Rivers, running about 60 miles inland. That is why the state is fat at the bottom and pinches toward the north. Vermont is the opposite shape—wide against Canada, narrow against Massachusetts—because its western side follows Lake Champlain and a surveyed line with New York, while its eastern side follows the river. The river became the cut because two colonies claimed the same interior. New York’s 1664 patent to the Duke of York ran east to the Connecticut River. New Hampshire’s governors later claimed west as far as Massachusetts and Connecticut did: 20 miles east of the Hudson. From 1749 to 1764, Governor Benning Wentworth sold that claim as the New Hampshire Grants—more than a hundred six-mile-square towns on the west bank of the Connecticut, in what is now Vermont. New York sold overlapping titles to the same land. King George III settled the colonial fight on July 20, 1764: the boundary between New Hampshire and New York would be “the western banks of the River Connecticut.” That order is why the two states look like halves of one block. Everything east of the west bank stayed New Hampshire. Everything west became New York on paper, then the Vermont Republic in 1777, then the 14th state in 1791. The river does not run due north–south, so the cut is angled. It rises in the Connecticut Lakes in far northern New Hampshire, then trends generally south with a southwest lean through a valley that already existed as a travel corridor. On a map that reads as a diagonal. Vermont is the western triangle; New Hampshire is the eastern one. Flip either state and it roughly fits the other. That is the “square split at an angle.” Two later fights locked the line in place. During the Revolution, Vermont annexed a string of New Hampshire towns east of the river. George Washington told Vermont to drop the claim if it wanted to join the Union. In 1782 Vermont did, and gave up any jurisdiction east of the low-water mark on the western shore. A century and a half later Vermont tried to tax mills in the river. In 1933 the Supreme Court held Vermont to that 1782 concession. New Hampshire owns the river. Vermont owns the bank. The border is the ordinary low-water mark on the Vermont side, not the middle of the channel. So the geometry is an accident of grants, a royal order, a river that was already there, and a republic that traded the water for statehood. Nobody drew a square and then drew a diagonal through it. The box is the old claim. The slash is the Connecticut.

MiniMax H3 Fashion Lookbook | Anime Character Reveal + Editorial MV Prompt🔥 Made this high-saturation anime PV with 13 fast visual beats in 15 seconds. A few years ago, this would’ve been days of AE work. Now? Prompt → generate → refine. Prompt 👇 Create a **15s, 16:9, 24fps anime character reveal trailer** with **13 fast visual beats**. Style: **Japanese anime opening × premium AAA motion graphics × fashion campaign**. The video should feel **explosive, sexy, stylish, bold and high-impact**, with **80% motion graphics and 20% character action**. ## CHARACTER LOCK — HIGHEST PRIORITY AO is a **young adult East Asian anime woman** with a sexy, confident Japanese anime aesthetic. She has: * small refined face * sharp expressive crimson eyes * glossy lips * confident, teasing gaze * slim feminine curvy figure * long elegant legs * stylish, cool, alluring presence Keep her identical throughout: * chin-length vivid red bob with messy bangs * crimson-red eyes * black choker * fitted red cropped top * short white cropped jacket, worn open * black mini skirt or fitted shorts * red belt detail * black thigh strap * white-and-red platform sneakers * subtle silver accessories Preserve the same face, body proportions, hairstyle, outfit, materials and colors in every shot. **Never redesign AO. Never change her face or outfit. If a shot becomes too complex, simplify the action first.** ## VISUAL STYLE Palette: **vivid red, crimson, white, black, silver**. Use: giant kinetic typography, red circles, diagonal slashes, manga speed lines, split screens, halftone dots, barcode strips, UI ticks, freeze frames, RGB flashes, impact shakes, poster layouts and graphic wipes. Every beat should feel: **fast, sharp, sexy, explosive, graphic and iconic**. Keep typography bold and readable. Editing: hard cuts, aggressive snap zooms, whip pans, speed ramps, freeze frames, impact shakes and foreground wipes. ## 13 VISUAL BEATS **01 | 0.0–1.0s** White field. Massive red circle slams into frame. Black bars slash across. UI ticks flicker. Giant **A**, then **O**, hit with heavy impact shake. **02 | 1.0–2.0s** The O becomes a circular frame showing an extreme close-up of AO’s crimson eye and glossy lips. She gives a teasing side glance. RGB flash. Circle bursts into red-and-white fragments. **03 | 2.0–3.1s** Black background, huge white **AO**. AO enters fast, turns sharply and power-slides beneath the typography. Red speed streaks trail behind her. Whip-pan out. **04 | 3.1–4.0s** Three red/white/black vertical panels. AO appears in three poses: hip turn, hair touch, over-shoulder stare. Huge vertical **FULL SPEED** moves behind her. **05 | 4.0–5.1s** AO jumps through a rotating typography ring reading **NO BRAKES / ALL EYES ON ME**. One clean mid-air spin. Snap zoom into her confident face. **06 | 5.1–6.0s** White editorial frame. Huge black **HOT** with a red slash. AO crosses the frame with a runway-like step, one hand at her waist. Typography compresses and rebounds. **07 | 6.0–7.0s** Bright red field with black diagonal stripe. AO performs one smooth fast turn. Three ghosted freeze positions trace the movement. Giant outlined **TURN** rotates behind her. **08 | 7.0–8.0s** Words hit one per beat: **HOT / FAST / WILD / RED** AO changes pose with each word: direct stare, hair toss, hip shift, confident forward lean. **09 | 8.0–9.0s** Black frame with manga perspective lines and a graphic grid. AO steps forward and freezes in a strong hero pose. Red circular target graphics lock around her. **10 | 9.0–10.1s** AO moves toward camera through three red-and-white graphic panels. Each panel shatters as she passes. Large **A O** fragments appear behind her. Finish with a hair or leg foreground wipe. **11 | 10.1–11.1s** Rapid poster montage: four frames of the same AO — close-up stare, walking, side pose, hands at waist. Add **01–04**, barcodes, halftone dots and sharp Japanese poster graphics. **12 | 11.1–13.0s** Hero moment on a clean white background. AO lands in a powerful fashion pose: one leg forward, one hand at her waist, chin lifted, direct eye contact. Huge red shockwave rings explode behind her. Typography fragments and speed lines burst outward. Hold an iconic confident freeze. **13 | 13.0–15.0s** Final identity card. Huge black **AO** on a bright white field. AO stands relaxed and alluring in front of the letters. Red circles, halftone, technical arcs and sharp speed accents surround her. Final red pulse flashes through the frame and ends on a hard stinger. ## ANIME STYLE Premium modern Japanese anime rendering: * clean cel shading * sharp linework * polished highlights * cinematic close-ups * dynamic perspective * fashion-editorial full-body framing * smooth hair and fabric motion AO must look like a **stylish adult anime heroine**, not chibi and not childish. ## AUDIO Hard-hitting **electro / future bass / anime-opening style music**. Use: heavy drums, bass hits, risers, glitch fills, synth stabs, typography slams, whooshes and shutter impacts. Build continuously. Peak at Beat 12. End with a sharp electronic stinger. ## PRIORITIES 1. AO identity consistency 2. sexy adult anime character design 3. red-black-white outfit consistency 4. maximum visual impact 5. readable typography 6. premium anime rendering 7. fast beat-synced editing Avoid: childlike proportions, chibi style, blue clothing, face changes, outfit changes, extra characters, unreadable typography, weak motion, dull compositions or generic schoolgirl styling. Final result: **explosive, sexy, red-hot, premium, graphic-driven and visually unforgettable.** Try MiniMax H3 on Ima Studio 👉 #MiniMaxH3# #MotionDesign# #Anime# #AIVideo# #ImaStudio#

# Cursor Features and Practical Usage 🧩 Tired of re-explaining the same multi-step workflow to your agent every single time? Cursor Skills let you package repeatable workflows so the agent just knows how to do them. 🏷️ Title: Reusable Workflows (SKILL.md) 🔗 URL: 📘 Overview Skills are portable, version-controlled packages that teach agents how to perform domain-specific tasks. They bundle scripts, templates, and reference material that the agent runs through its available tools. They are the evolution of Rules: agents can apply them automatically based on context, or you can invoke them explicitly as slash commands. ⚙️ How It Works Each skill is centered on a `SKILL.md` file whose leading YAML frontmatter defines its behavior. ・`name`: a lowercase identifier that must match the parent folder name (required) ・`description`: what the skill is for and when it applies; the agent reads this to decide whether to use it (required) ・`paths`: glob patterns that scope the skill to matching files (optional) ・`disable-model-invocation`: set to `true` to make it slash-only, included only when you type `/skill-name` (optional) Discovery is hierarchical: project skills live in `.cursor/skills/` (or `.agents/skills/`), and global ones in `~/.cursor/skills/`. The root is walked recursively, so nested subdirectories are found too. A skill folder can also ship `scripts/` (executable code), `references/` (docs loaded on demand), and `assets/` (templates or images). 🛠️ Practical Usage For example, in `.cursor/skills/api-endpoint/SKILL.md` set the frontmatter `name` to `api-endpoint`, a `description` of the workflow, and `paths` scoped to `src/api/**/*.ts`, then write the steps in the body (register the route, validate input with a zod schema, always add tests). If you do not want automatic invocation, add `disable-model-invocation: true` and call it explicitly by typing `/api-endpoint` in Agent chat. 💡 Use Cases In a monorepo, placing a `.cursor/skills/` folder inside each app automatically scopes those skills to files in that directory, so you can skip `paths` entirely. Share release procedures, migration scripts, or code-review checklists so the whole team works the same way. You can convert existing assets with the built-in `/migrate-to-skills` (Cursor 2.4): "Apply Intelligently" rules (`alwaysApply: false`) become skills, and slash commands become skills with `disable-model-invocation: true`. ⚠️ Caveats A skill's identity comes from the folder containing `SKILL.md`, not any parent category. The old `globs` field is deprecated; use `paths` now. `/migrate-to-skills` does not migrate `alwaysApply: true` rules or user-level rules, so those need manual handling. #Cursor# #AICoding#

# Hermes Agent Features and Practical Usage 🚀 For when you don't want the conversation to stop while the agent works. The modern TUI offers non-blocking input, mouse support, and rich overlays so you can watch long tasks and drop in extra instructions. 📌 Title and Feature URL Title: TUI (Ink terminal UI) URL: 📝 Overview The TUI is a modern terminal UI for Hermes, launched as a subprocess from the Python CLI. It is Node.js-powered (≥20) and shares the same Python runtime, sessions, and slash commands as the classic CLI, while delivering a cleaner, more responsive experience. 🔧 How It Works ・It paints an instant first frame for a non-frozen startup, uses differential updates to prevent flicker during streaming, and provides rich modal overlays for model picking, session selection, and approval prompts. ・Non-blocking input lets you queue messages before the session is ready, and mouse selection uses uniform background highlighting instead of terminal inverse video. ・It renders LaTeX math, both inline (`$E = mc^2$`) and block (`$$...$$`). ・A status line narrates state (starting agent… / ready / thinking… / running… / interrupted) plus working directory with git branch, elapsed time, auto-compression count, active `/background` tasks, and a YOLO warning badge. 🛠 Practical Usage ・Launch with `hermes --tui`, resume the latest with `hermes --tui -c`, resume a specific one with `hermes --tui -r `, or force classic CLI with `hermes --cli`. ・To default to it, set the env var `HERMES_TUI=1` or `display.interface: tui` in `~/.hermes/config.yaml`. ・TUI-specific slash commands are plentiful: `/model` (picker with per-provider cost hints), `/sessions` or `/switch` (live session switcher), `/skin` (live theme preview), `/details` (toggle tool detail), `/agents` or `/tasks` (observability overlay with a subagent tree), `/mouse`, and `/reload`. ・Press `Ctrl+X` to open the live session switcher and run multiple concurrent sessions within one terminal. 🎯 Use Cases ・Watch a long task progress in the live panel while dropping in mid-run instructions via non-blocking input. ・Dispatch and orchestrate many concurrent agent sessions from a single terminal. ・Survive SSH disconnects by auto-resuming with `HERMES_TUI_RESUME`. ⚠️ Caveats ・Node.js ≥20 is required (verified by `hermes doctor`), and the first launch installs TUI Node dependencies into `ui-tui/node_modules` once. ・A TTY connection is assumed; pipes or non-interactive environments fall back to single-query mode. ・It cannot attach to a remote gateway (the TUI spawns its own in-process gateway). Light-theme detection relies on `COLORFGBG` or OSC 11 probes, which not all terminals support. #HermesAgent# #DevTools#

We're announcing the most significant new strategic development since the start of the Customer Agent category: Fin now has specialized roles. And starting today anyone can sign up for and deploy the Fin Sales Role in minutes. Fin is now by far the very best sales agent on the market, and it's been live with some of the most innovative digital brands for months, conversing with thousands of prospects, aiding discovery, building pipeline, booking meetings and starting trials. We started the Customer Agent category with a focus on service by launching Fin three months after the launch of ChatGPT. Since then Fin has continued to lead the space, today delivering over 2 million resolutions a week for over 8k customers, including Anthropic, DoorDash, Snowflake, Asana, Mercury, Polymarket and many more exceptional brands. But our vision for Fin has always stretched far beyond service. And for the past 6 months we’ve been building Fin as a single Customer Agent, delivering a seamless experience across all stages of the customer lifecycle. We do not believe customers or businesses will want multiple agents for different parts of the lifecycle—because the agents won’t have shared memory and goals, and will have to compete with each other, delivering a poor customer experience and sub-optimal business results. We’ve more roles to come, including another dropping in two weeks. For now please watch our launch video or visit our launch page to learn more: fin DOT ai SLASH sales

# Hermes Agent Features and Practical Usage 🚀 The CLI is the developer's daily window into the agent. Just type `hermes` in your repo and you get interactive chat, slash commands, and one-shot execution all in one. 📌 Title and Feature URL Title: CLI URL: 📝 Overview The Hermes CLI is a terminal chat interface. It shows a conversation stream, a fixed input prompt, and a status bar with the current model and token usage, letting you fine-tune behavior with slash commands as you work. Beyond interactive mode it supports single-query runs and session resume. 🔧 How It Works ・Launch modes include interactive (`hermes` or `hermes chat`), single-query (`hermes chat -q "..."`), and resume (`hermes --continue` / `hermes --resume `). ・The status bar shows model name, token usage (e.g. 12.4K/200K), a color-coded context fill bar, estimated cost, compression count, background task count, and elapsed time. ・Slash commands are rich: `/model` (switch model), `/personality` (helpful, concise, technical, teacher, and more), `/voice on|off|tts`, `/reasoning high`, `/background `, `/sessions`, `/usage`, `/tools`, `/status`. ・Long conversations auto-summarize (compress) as they near the context limit, by default keeping the first 3 turns and last 20 turns and summarizing the middle. 🛠 Practical Usage ・Launch flags shape behavior: `--model` / `--provider` to pick a model, `-s` (`--skills`) to preload skills, `-w` for an isolated git worktree, `--tui` for the modern UI, and `--yolo` to auto-approve tool calls. ・Multiline input is `Alt+Enter` / `Ctrl+J`, external editor is `Ctrl+G`, and interrupt is `Ctrl+C` (double-press within 2s to force exit). ・Define LLM-free shell commands under `quick_commands` in `~/.hermes/config.yaml` and invoke them like `/status`. ・Set `busy_input_mode` to steer to inject input into the running turn via `/steer` while the agent works. 🎯 Use Cases ・From a repo, ask "find why the tests fail and fix them," then adjust with `/model` or `/reasoning` as it runs. ・Spin up parallel, isolated sessions with `/background` to progress separate tasks at once. ・Call `hermes chat -q "..."` one-shot from scripts or pipelines. ⚠️ Caveats ・`Shift+Enter` newlines are terminal-dependent; standard Windows Terminal and macOS cannot distinguish it from Enter. ・`/background` sessions are fully isolated from the main conversation history and share none of the foreground context. ・The CLI strips markdown fences and formatting wrappers from final replies for readability (code blocks and lists remain). Voice mode requires a supported terminal. #HermesAgent# #DevTools#

# Hermes Agent Features and Practical Usage 🚀 Five minutes from install to your first real conversation. Have the agent read files, run commands, and search the web by handing it an actual task right away. 📌 Title and Feature URL Title: Quickstart URL: 📝 Overview The Quickstart walks you from a fresh install to a working first conversation. You launch with `hermes` or `hermes --tui` and exercise core abilities: inspecting a repo, executing commands, and searching the web. Its guiding principle is to get one clean conversation working before layering on anything else. 🔧 How It Works - Launch via the classic CLI `hermes`, or the modern TUI with modal overlays `hermes --tui` (recommended). - Run the setup wizard with `hermes setup`; pick a model interactively with `hermes model`. - Resume your most recent session with `hermes --continue` (short form `hermes -c`). - Diagnose configuration issues with `hermes doctor`. - Capabilities demonstrated include file reading, terminal command execution (with approval), web search via the Tool Gateway, and multi-turn conversations. 🛠 Practical Usage - Start with specific, verifiable prompts. Example: "Summarize this repo in 5 bullets and tell me what the main entrypoint is." - Confirm file reading with something like "Check my current directory and tell me what looks like the main project file." - Try "Help me set up a clean GitHub PR workflow for this codebase" to see command execution and the approval flow together. - Type `/` mid-conversation for an autocomplete menu of slash commands: `/help` (commands), `/tools` (available tools), `/model` (switch models), `/save` (save the conversation). 🎯 Use Cases - Right after install, double as a smoke test by asking for a repo summary or file inspection. - Feel out the command-approval flow on a real task to calibrate how much you delegate. - Switch models and tools via slash commands as you settle into your workflow. ⚠️ Caveats - Hermes Agent requires a model with at least 64,000 tokens of context; avoid models that are too small. - The guide stresses getting basic chat working first, then adding gateways, skills, or automation. - Command execution involves agent approval, so watch the approval behavior closely on your first run. #HermesAgent# #AIAgents#