Arthur

@cognition Devins Model picker is pretty nice for a model agnostic harness. Also Fusion make so much sense with a Lead and Sidekick but @dabit3 GPT 6.1 Sol as a sidekick would be nice but I guess this will come soon and maybe let me change the effort of the Sidekick would be great.

agree, jev or jev like models will have a huge impact it's not the " shiny" new thing but rather really useful and fast high-volume decision making tool go to x and just search jev for the diffent things people build already - harness decisions like

will share more about enterprise and B2B AI here creating a lot of enablement materials for SAP Business Technology Platform (soon Business AI Platform) and maybe some of you might find it useful you get a real feeling where enterprise AI is at right now

GPT 5.6 Sol med - xhigh is currently my go-to coding model been testing fable 5 and GPT 5.6 Sol the last few days Opus 4.8 with dynamic workflows was already pretty good but fable tops this. GPT 5.6 Sol Ultra also spins up a lot of subagents but the results weren't that good in my tests

GPT 5.6 medium-high are really good for daily coding tasks but overall, fable / opus still better at design, though gpt 5.6 caught up a bit. + Codex app is really good with all the features like computer use / browser use and plugins

I’ve been building a small agentic GitOps infrastructure on k3s, and the main lesson is this: the agent should not be the platform. GitOps is the platform. The agent is an operator that works inside boundaries. Current shape of the stack: 1. k3s on Hetzner

It gets constrained inputs, read/write boundaries, policy gates, branch protection, and Git as the actuator. Higher-risk changes stay human-reviewed. That feels like the right shape for small infrastructure: - cheap enough to run on one node - Git-native enough to audit

I’ve been building a small agentic GitOps infrastructure on k3s, and the main lesson is this: the agent should not be the platform. GitOps is the platform. The agent is an operator that works inside boundaries. Current shape of the stack: 1. k3s on Hetzner

Prometheus, Grafana, Loki, Tempo, Alloy, Alertmanager, blackbox probes, and runbooks make the system explainable before an agent touches it. 10. MCP + alert-to-agent loop

I’ve been building a small agentic GitOps infrastructure on k3s, and the main lesson is this: the agent should not be the platform. GitOps is the platform. The agent is an operator that works inside boundaries. Current shape of the stack: 1. k3s on Hetzner

One generic Helm chart, explicit app registration, per-project service-account impersonation, scoped RBAC, quotas, limit ranges, PSA labels, and default-deny egress. 8. SOPS + age

I’ve been building a small agentic GitOps infrastructure on k3s, and the main lesson is this: the agent should not be the platform. GitOps is the platform. The agent is an operator that works inside boundaries. Current shape of the stack: 1. k3s on Hetzner

CI pushes sortable image tags. Flux writes the promoted tag back into each app’s deploy/values.yaml, so deployments remain Git commits. 5. Gateway API + Traefik + cert-manager + external-dns Apps get HTTPRoutes. The shared gateway carries wildcard TLS. DNS lands in Cloudflare automatically.

I’ve been building a small agentic GitOps infrastructure on k3s, and the main lesson is this: the agent should not be the platform. GitOps is the platform. The agent is an operator that works inside boundaries. Current shape of the stack: 1. k3s on Hetzner

A lean Kubernetes base. Single-node today, with the app and DB model designed so it can move toward HA without changing how apps are deployed. 2. Flux Operator One FluxInstance syncs the cluster root from Git. No app-of-apps sprawl, no imperative drift as the default operating model.

I do a lot of work around agent-assisted coding/vibe coding, and two questions come up every single time: How do I get my app live? How do I make it secure? my first instinct was an agentic cloud that just auto-checks and ships it

I genuinely don't know yet if this solves real pain or if it's just another idea. that's why I'm looking for testers. bring your own Codex / Claude subscription or API key, I cover sandbox and hosting. all I want back is honest feedback. comment or DM men

I do a lot of work around agent-assisted coding/vibe coding, and two questions come up every single time: How do I get my app live? How do I make it secure? my first instinct was an agentic cloud that just auto-checks and ships it

but the reality is still, a human has to review it in an business / enterprise context. an auto-scan won't tell you your architecture is wrong or your tech-stack decision will hurt in six months. the expert in the loop is the value. so I built pullplane to test one idea:

@cursor_ai cloud agents are wild you literally spin up a VM, tell it what to build, and watch it: - open browsers - click around - run tests - record everything - debug itself first agent walks you through setup and gets everything running without you lifting a finger

I introduced some bugs with the latests changes and focusing on fixing them today-md v1.7.6.

This release tightens the planning loop on macOS: a reliable Cmd-_ quick add flow, Monday-based week views, cleaner rescheduling, better calendar onboarding, preserved subtasks on reload, and clearer list color picking.