Hey there, We move fast. Not "we'll get to it in Q3" fast. We mean feedback lands on a Wednesday and a fix ships by Thursday. That's the kind of product we want to build, and this release is proof of it. v1.1.2 is out now — and it's got some real improvements that change how you interact with the extension day to day. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ THE SIDEBAR REDESIGN ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Archeo now lives in Chrome's side panel — the persistent drawer on the right side of your browser. This matters for a few reasons: No more popup that closes every time you click away. The nav rail stays visible. You can archive a page, jump to History, open a Design Brief, and switch back to Tokens without the extension resetting on you. It's a small change on paper. It feels like a big one in practice. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DESIGN BRIEFS — NOW WITH YOUR OWN AI KEY ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Design Briefs have always worked offline — no account, no API, just the extracted structure and design tokens from the live page. But the AI-enhanced version (the one that writes out a proper reconstruction spec with design intent, component breakdown, and UX notes) now has a dead-simple activation path inside the panel. Here's how it works: 1. Open the Brief panel 2. Hit "Use AI" 3. Pick Anthropic or OpenAI, paste your key, hit Test, then Save 4. Generate That's it. Your key lives in local extension storage. We never see it. Archeo only sends the extracted brief context to your chosen provider when you explicitly trigger generation. The offline version still works without any key at all. If you've been wanting to try the full brief output — this is the easiest it's ever been to set up. Try Archeo Free — 5 archives included → https://nasus1.gumroad.com/l/archeo ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WHAT ELSE LANDED IN v1.1.2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ → Capture Summary is now opt-in After an archive completes, a dot badge lights up on the Summary button in the rail. Open it when you want it — it no longer auto-pops and interrupts your workflow.

Point Archeo at any website. Hit capture. In 30 seconds you get: - every color token on the page - the full type scale - spacing values - all of it as JSON, Markdown, or Tailwind config No inspecting elements. No guessing hex codes. No copy-pasting. I built this because I was doing a brand audit for a client and spent two hours manually pulling colors and font sizes from a site I didn't have Figma access to. Now it takes 30 seconds. But the design export is just one side of it. The other thing Archeo does: it saves any web page as a fully working offline copy. Three formats: - ZIP with the full file structure - Single HTML with everything inlined - MHTML browser snapshot It scrolls the page before capturing so lazy-loaded content doesn't get missed. It pulls from Shadow DOM. It rewrites links so navigation still works offline. It strips trackers before saving. The result is a complete, portable, interrogatable copy of any page. Useful for: - saving competitor landing pages to reference later (they will change) - building reference libraries without bookmarks that die - feeding a full page to an AI tool without losing structure - auditing client sites before a redesign kickoff No cloud. No login. No analytics. Everything runs locally in your browser. v1.1 is live at archeo.dev $9 minimum, pay what you want. 14-day refund if it doesn't click for you. Community code AIDC20 takes 20% off. First 100 uses only! If you're doing any client work, competitive research, or design auditing, try it this week.

Been using this on client projects for months. Time to ship it. It's called Archeo. It downloads any web page as a working offline copy. Three formats: ZIP with full file structure, Single HTML with everything inlined, or MHTML as a browser snapshot. The scanner scrolls the page before capture to catch lazy-loaded content, pulls from Shadow DOM, rewrites links so offline navigation works, and blocks trackers before archiving. There's also a design system export. Point it at any site and it outputs color tokens, type scale, and spacing as JSON, Markdown, or Tailwind config. I use it for audits and reading codebases. No cloud, no login, no analytics. Fully local. v1.1 is live at archeo.dev. $9 minimum, pay what you want, 14-day refund if it doesn't work for you. For the community: use code AIDC20 for 20% off. First 100 uses only. If you try it, let me know what breaks. That feedback is more useful than anything right now. archeo.dev

Happy New year to you'll! I'm on the board of the Google Development Group at MDC as their research and development. Anyone have any tips on research and development topics I should be looking into?

Hi team: Just dropping an update on my Manus.AI useage which has been since 30 August 2025 until Today. This post is about using Manus to create a high-quality, well-featured briefing document and technical action plan. This was done with a Youtube transcript as the primary input (See Note #2 below). The task completed in 15 minutes on the first run which was much appreciated. <prompt> # Context I have a Text-based transcript from an AI Business Development Expert, and I want to convert that into a well-featured briefing document and technical action plan, so I can encode it into an AI & Automation workflow. # Query Using the full suite of Tools currently available with Manus AI, how would you suggest I do this? Please be explicit and very helpful. # Target Audience The end user for the well-featured briefing document would be other members of my business team and potential client business owners & operators. The end user for the technical action plan, will be myself, my lead Developer and our Agentic AI collective. # Task Please help me uses the lessons from the "How to Automate Any Business using AI tools" video to grow my business. </prompt> Task Credits Used: 429 Attached: Screenshots of Manus.AI usage since 30 August 2025. Note #1: This was a very simple prompt with little structure and zero security considerations, so I expect that a fully-featured prompt with security constraints plus initial design & UI enhancements would produce a better result. Note #2: The Youtube video that I extracted the transcript from, did not belong to me and was only used to test Manus.AI and assess it's output, and not to outright copy another creator's content. Always remember 'Fair Use' provisions and attribute creators as required. END.