#ENVS
its really funny that cursor in enterprise envs lets you share transcripts and a lot of the ones i’m reading look like the person didn’t realize it would be shared with the whole team
October 30, 2026 at 7:28 PM
i've been calling the ever-expanding amalgamation of envs+repos+services+automation on the tailnet my construct. i've basically setup a mid-size dev shop for personal projects on all the compute i own
November 1, 2026 at 10:20 PM
How does intense prolonged heat effect plant life? Is total species diversity the best proxy for forest health? When did crows get so smart?

Interested? Check out my latest environmental science weekly news recap!
#ENVS #EnvironmentalScience
25M
The TESR week roundup for the week of October 26th
theenvscireview.substack.com
November 2, 2026 at 6:28 AM
So far, everyone saying I’m wrong about this has been a big user of local models 🙃
Theo - t3.gg (@theo) on X
@itssotsot Defined roles and “agent” archetypes are so 2024 lol We are definitely exploring “bot” like systems, specifically meta threads for commanding your threads/agents/envs, but it will not be a defined role system because those are artifacts of a time where models were much dumber.
x.com
November 2, 2026 at 2:57 AM
Oh yeah that, indeed. I think it will take time to move through corps. Indy/startups already there. Bech tech in large pockets this year, complete next year, and the lots of other corps go over the next year. Regulated and stodgy places hold out moving from undesirable to intolerable work envs.
October 28, 2026 at 8:17 PM
We predicted the optimal axes to scale our RL envs along quantitatively. We find that you can predict how your model will perform at 16x the FLOPS, so you can steer the axes while you generate more and more envs. Scaling laws, but for the data composition. 🧵7/9
October 28, 2026 at 2:40 PM
But in that table, you see another thing: It also matters how you scale your envs, i.e., whether you add more tasks prompts, new apps and APIs, deeper on-device databases. SynthAPI-SubOpt and SynthAPI-Opt have the same number of envs, but SynthAPI-Opt composes them smartly. 🧵6/9
October 28, 2026 at 2:40 PM
Defined roles and “agent” archetypes are so 2024 lol

We are definitely exploring “bot” like systems, specifically meta threads for commanding your threads/agents/envs, but it will not be a defined role system because those are artifacts of a time where models were much dumber.
November 1, 2026 at 10:30 PM
Your dev-environment point landed for me — secrets shouldn't even be reachable from the agent's sandbox in the first place. Is per-task ephemeral envs the practical answer, or too slow for daily work?
October 29, 2026 at 7:07 PM
9/
Common bioinformatics "just restart it" moments:
Missing package functions in R

Python envs not seeing installed packages

Shell doesn’t recognize newly installed tools

VSCode not seeing PATH changes

Environment variables not updating
October 29, 2026 at 2:15 PM
(can’t share the environments, but we do give all prompts we used so you can build your own envs in the appendix :) ) 🧵4/9
October 28, 2026 at 2:40 PM
Punya akun pubnix lagi di shellter(dot)me, daripada gak kepake. Di envs(dot)net juga dah lama gak gue beresin dan masih males.

https://ufal.shltr.eu/
October 28, 2026 at 1:37 PM
Overall, we create 458,752 RL envs, across 64 apps with 10,472 different APIs. 6266 of them are write-APIs, because virtually all our tasks are about making state-changing operations, like ordering something, playing something on the device, or sending messages etc. 🧵3/9
October 28, 2026 at 2:40 PM
We let Gemini build RL envs in three phases. 1) Come up with a new app, and implement APIs that agents can call. 2) Bootstrap some APIs and build task prompts that require them. 3) Fill in the on-device app databases, create a verifier, and check if it’s solvable. 🧵2/9
October 28, 2026 at 2:40 PM
🟢 PR #1033 — build(deps): bump docker/build-push-action from 6 to 7
**Pull request (OPEN)** · PR #1033 build(deps): bump docker/build-push-action from 6 to 7 · @dependabot * * * Bumps docker/build-push-action from 6 to 7. Release notes _Sourced from docker/build-push-action’s releases._ > ## v7.0.0 > > * Node 24 as default runtime (requires Actions Runner v2.327.1 or later) by @​crazy-max in docker/build-push-action#1470 > * Remove deprecated `DOCKER_BUILD_NO_SUMMARY` and `DOCKER_BUILD_EXPORT_RETENTION_DAYS` envs by @​crazy-max in docker/build-push-action#1473 > * Remove legacy export-build tool support for build summary by @​crazy-max in docker/build-push-action#1474 > * Switch to ESM and update config/test wiring by @​crazy-max in docker/build-push-action#1466 > * Bump `@​actions/core` from 1.11.1 to 3.0.0 in docker/build-push-action#1454 > * Bump `@​docker/actions-toolkit` from 0.62.1 to 0.79.0 in docker/build-push-action#1453 docker/build-push-action#1472 docker/build-push-action#1479 > * Bump minimatch from 3.1.2 to 3.1.5 in docker/build-push-action#1463 > > > **Full Changelog** : docker/build-push-action@v6.19.2…v7.0.0 > > ## v6.19.2 > > * Preserve port in `GIT_AUTH_TOKEN` host by @​crazy-max in docker/build-push-action#1458 > > > **Full Changelog** : docker/build-push-action@v6.19.1…v6.19.2 > > ## v6.19.1 > > * Derive `GIT_AUTH_TOKEN` host from GitHub server URL by @​crazy-max in docker/build-push-action#1456 > > > **Full Changelog** : docker/build-push-action@v6.19.0…v6.19.1 > > ## v6.19.0 > > * Scope default git auth token to `github.com` by @​crazy-max in docker/build-push-action#1451 > * Bump brace-expansion from 1.1.11 to 1.1.12 in docker/build-push-action#1396 > * Bump form-data from 2.5.1 to 2.5.5 in docker/build-push-action#1391 > * Bump js-yaml from 3.14.1 to 3.14.2 in docker/build-push-action#1429 > * Bump lodash from 4.17.21 to 4.17.23 in docker/build-push-action#1446 > * Bump tmp from 0.2.3 to 0.2.4 in docker/build-push-action#1398 > * Bump undici from 5.28.4 to 5.29.0 in docker/build-push-action#1397 > > > **Full Changelog** : docker/build-push-action@v6.18.0…v6.19.0 > > ## v6.18.0 > > * Bump `@​docker/actions-toolkit` from 0.61.0 to 0.62.1 in docker/build-push-action#1381 > > >> [!NOTE] Build summary is now supported with Docker Build Cloud. > > **Full Changelog** : docker/build-push-action@v6.17.0…v6.18.0 > > ## v6.17.0 > > * Bump `@​docker/actions-toolkit` from 0.59.0 to 0.61.0 by @​crazy-max in docker/build-push-action#1364 > > >> [!NOTE] Build record is now exported using the buildx history export command instead of the legacy export-build tool. > > **Full Changelog** : docker/build-push-action@v6.16.0…v6.17.0 > > ## v6.16.0 > > * Handle no default attestations env var by @​crazy-max in docker/build-push-action#1343 > … (truncated) Commits * c3c9e26 Merge pull request #1621 from docker/dependabot/npm_and_yarn/docker/actions-t… * 459b674 [dependabot skip] chore: update generated content * 4dedcb2 chore(deps): Bump `@​docker/actions-toolkit` from 0.99.0 to 0.100.0 * 379bf63 Merge pull request #1620 from crazy-max/buildx-error-message * 9877975 chore: update generated content * 7ed0556 use the shared Buildx error summary helper * 91670ba Merge pull request #1618 from docker/dependabot/npm_and_yarn/docker/actions-t… * 80dbc86 [dependabot skip] chore: update generated content * 50cac3a chore(deps): Bump `@​docker/actions-toolkit` from 0.98.0 to 0.99.0 * 03b4d6c Merge pull request #1617 from crazy-max/fix-metadata-workflow-commands * Additional commits viewable in compare view Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: * `@dependabot rebase` will rebase this PR * `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it * `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency * `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) * `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) * `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) * * * Ouvrir sur GitHub →
indiekit-demo.rmendes.net
November 1, 2026 at 8:15 PM
Corpo: We need all regression tests automated in CI/CD.

QA: Autotests are ready. Pipelines have been red for 7 days. Broken envs, broken features.

Corpo: Remove all tests so we can merge and ship to prod.

QA: So we automated regression testing just to remove it when it catches problems?
October 27, 2026 at 9:24 PM
Super cool! We're deep on an overhaul to the MCP and environments layer that will make this much easier to do. Curious how you're managing the connections to multiple envs now?

Will send a bot to look into this :) @bot remind me later
October 27, 2026 at 4:15 AM
amp's dev envs for agents feel like the missing piece between local dev and cloud chaos. shipping side projects just got easier.
October 23, 2026 at 12:12 PM
... oh right, "from the labs". I was about to start ranting about hardware prices x3

I suspect it's a combination of 'it never occurred to us' and 'Isn't that the dark pattern gacha games use?'

It's also the kind of thing you can't really quantify so impossible to get approval for in corpo envs
October 24, 2026 at 12:39 AM
Got a couple small changes into T3 Code as well, such as:
- Rewrite search to be 4x more accurate
two-click repo clones to other machines (including .envs)
- "Working" sidebar section to hide working threads
- live guest thread sharing so others can watch and queue prompts 🤫
- watch_pr tool so
October 25, 2026 at 3:27 AM
Yeah but i've been talking about something else, specifically about development environment, and how you are supposed to use separate nix envs for that, and you came here saying "nuh uh your os is global"??? Yeah?? I wasnt talking about firefox and telegram and emacs
October 26, 2026 at 1:53 AM
such as:
- Rewrite search to be 4x more accurate
two-click repo clones to other machines (including .envs)
- "Working" sidebar section to hide working threads
- live guest thread sharing so others can watch and queue prompts 🤫
-
October 25, 2026 at 3:29 AM
4/ The agent stack went neutral in one day: at AGNTCon, Anthropic donated Agent Skills (claims 1M skills, 280M installs) to the Agentic AI Foundation, OpenAI donated the Open Responses API spec, HF donated OpenEnv for RL envs, Alibaba donated OpenSandbox.
October 23, 2026 at 4:07 PM
Well thought yesterday was bad guess who has to change out all their envs...
If you're a railway customer, you need to jump on this immediately.

"We strongly recommend that you immediately roll all environment variables, including any API keys, stored in Railway"

blog.railway.com/p/security-d...
Security Disclosure: Wednesday October 21st | Railway Blog
Railway detected anomalous activity involving systems that store customer environment variables and recommends your immediate attention
blog.railway.com
October 22, 2026 at 7:18 AM
Yesterday, we had our invertebrate and zooplankton ID lab for the ENVS 3450 Aquatic Environments course. It is always neat to see those important little critters up close!

This one is a Daphnia, a cladoceran zooplankton species, carrying around some eggs.
October 21, 2026 at 3:25 PM