π€ Building the future of browser automation with AI agents
CoFounder @100x.bot - turning Chrome into your personal AI assistant
β¨ What we're solving:
β’ Manual browser tasks β Automated workflows
β’ Complex web scraping β Simple AI commands
β’ Repetitive clicks β Smart automation
Try it free: https://t.co/BhdOGQH2WO π
#AI #Automation #Chrome
I made puppt, a cli to inspect and edit pptx files reliably. the biggest part of the code base is actually the renderer.
I started with an approximation based renderer against a set of ~65 slides for testing. but that method quickly hit the limits since presentationml/drawingml are quite long and on top of that the actual renders are affected by the implementation level quirks (msppt vs apple notes vs libre vs google docs).
so I start implementing the spec. i divided the spec into 12 broad milestones. this is promising and less stressful since with every change you are not fearing if the "mismatch pixel count is going to go down or up".
the first mvp of puppt was taking about 7 second to render because my render pipeline was mvp. so no caching/optimizations. spent another day working on it.
now it can render a slide <200 ms on average.
check it out here https://t.co/i5oe1fjUea
@theo i used the same claude -p approach for using it in one of my side project ( https://t.co/PgrVeWbm7S a2ui renderer ). canopy would start instance of claude-code or codex and expose itself as a mcp. now i am not sure if its acceptable usage. obviously codex has no issues
Daptinβs app-connection design sits closer to Nango than Merge, but the ownership boundary is different.
https://t.co/u0LXA8qu9H
Nango gives you managed integration runtime: provider auth, connections, token refresh, proxy calls, syncs, actions, webhooks, observability.
Merge gives you normalized category APIs: HRIS, ATS, CRM, accounting, ticketing, file storage. The product stores a Merge account token and talks to Mergeβs common models.
Daptin keeps the integration state inside the database.
`oauth_connect` is the provider OAuth app config.
`oauth_token` is the userβs connected account for that provider.
`integration` is the provider API surface, usually an OpenAPI spec.
When an operation runs, the request supplies `oauth_token_id`. Daptin checks that the token belongs to the authenticated user and that it matches the `oauth_connect_id` expected by the integration. Then it attaches the outbound auth.
For API-key/basic/bearer providers, the same execution path uses `credential_id`, checks access, decrypts the credential, and maps it into the outbound request.
The provider API stays native:
`GET /integration/{provider}/operations`
`GET /integration/{provider}/operations/{operation}`
`GET /integration/{provider}/openapi.yaml`
`POST /integration/{provider}/{operation}`
So Daptin does not need a Merge-style common model to make app connections work. It can expose provider-native operations from the imported spec, while keeping auth, permissions, token ownership, and runtime execution in the same backend.
Merge optimizes for breadth through normalized models.
Nango optimizes for managed integration runtime and sync/action infrastructure.
Daptinβs feature uses its own rows, permissions, OAuth flow, credentials, OpenAPI importer, and action runtime. The connected app is visible as Daptin data, not as an external platform account hidden behind another API.
what if you could run #playwright#javascript or #typescript projects directly from your chrome browser. no npm install needed. see the results right there (or send it a table or another api) (skip video to 1:10 timestamp)
Building JSLike: a #JavaScript interpreter that runs real ES6+ code, JSX, and TS/TSX-style modules without eval() or new Function(). CSP-safe, react friendly, zero runtime dependencies after build.
> npm install jslike
https://t.co/1BwYGUcLHj
i recently did a similar analysis on the r/mkindia (the mechanical keyboard sub) and found the top 10 across three budgets when i was buying myself a keyboard, here is the analysis if someone wanna see i made it public https://t.co/128HJ4YT2D
Reddit tells you exactly what your market thinks. The problem is there's too much of it to actually read.
We built an agent that hits Reddit's 1,000 post ceiling, scores every single one, classifies it by topic, and plots the whole thing into a sentiment scatter, so you can see patterns across an entire community in one glance instead of one post at a time.
No manual scrolling. No vague impressions. Just data your team can actually act on.
What you'll walk away with:
β A live Smart Table with 1,000 scraped and classified Reddit posts
β A sentiment scatter plot that maps emotion, topic and time simultaneously
β A trend graph showing which conversations are growing and which ones are dying
https://t.co/C7hqnmJLpJ
We are adding soon oauth connection so https://t.co/BhdOGQHAMm can directly interact with the likes of google calender/drive etc via API. So your work gets done reliably. Also coming soon is way to talk to your browser from anywhere. Yes, just leave your laptop on at home and talk to it from your mobile. Stay tuned
@jarredsumner waiting for loops, functions, modules, linters, and compilers for hooks. i love its inside json because humans can read json. sadly there is no precedent around this to leverage. /s