Cam Pak

@Chris_Segroves TRUE. I don't want a mass exodus into Oklahoma. So I'm okay with people thinking it's just tornadoes and cows

@CameronPak Of course it’s false, but I bet almost everyone in those states are fine with people who don’t live there believing the lie.

false

@michaelwhittle is oklahoma the 9th worst or the 9th best amongst the worst? I love Oklahoma haha

This is 100% accurate. Tennessee is awful. Don’t move here you will regret it.

@Shpigford Oh wow! The market decides!

knockoff.co is at around 75,000 daily active users! 🤯 a *browser extension*. absolutely bonkers.

@devinjameson You're doing a good work, Devin!

XL Foldkit release today! - foldkit/experimental/machine - Route.Transition for... you guessed it, route transitions! - Improved state management in Foldkit UI - Story/Scene test Command resolution in Submodels no longer requires Message mapping (the wrapping is recorded and replayed for you) Release notes have all the details you and your agents need to migrate. github.com/foldkit/foldki…

This is the golden age man. I built a desktop app that I use all day, every single day. And not just me! I built an app that developers live in to do their work. All with no prior desktop app experience. Never doom

A junior just asked me "what do I do if I'm being grilled about something I don't understand?" Try this: 1. In a grilling session 2. "I don't understand this" 3. "/handoff to a teaching agent to understand this" 4. Pick up the handoff doc with the /teach skill, in your teaching workspace 5. Learn it 6. Go back to the grilling session and pick up where you left off Keeps the grilling session clean, records progress in your /teach skill, and helps you learn

@devinjameson @localfirstconf Ooh, have fun!!

@heyderekj @taylorotwell Excited to try this!!

@taylorotwell DONE. ✅🏁 I made a visual feedback MCP (+MCP App) for gathering feedback. There's guest links and a kanban board. I call it ReviseMy. A version of this idea was back in 2024. The idea just stayed a domain. BUT NOW IT'S REAL. 💥 …isemy-production-b05pjt.laravel.cloud

I’ll send a new MacBook Air (good config nothing lame) to the best side project shipped on Laravel Cloud this weekend Not a drill please be somewhere I can actually ship it to Reply to this tweet with a laravel.cloud URL

I made my first Laravel app! 💥 Meet ReviseMy. A visual feedback MCP for gathering feedback complete with guest links, a Kanban board, and simple setup to use with your agent. revisemy.com

Hi All #PKMWeekly 12-Jul-26: @obsdmd AI Agent OS #verso apps, code release #DotFlowy (@CameronPak) release, walkthrough #Thymer Speed, Beta update @tana_inc Long form #Vellum Tasks @logseq Updated roadmap @CapacitiesHQ Update @tryOctarine inbox perf update @outlmd Update 👇

NEW: Study reveals LinkedIn is the most AI-saturated major social platform, with over 40% of long-form posts flagged as fully AI-generated “slop.”

@AlternativeTo Hey, I created Dotflowy, an OSS Workflowy alternative. I think it's fit for AlternativeTo and would like to be considered

Open-source and beautiful cross-platform Plex & Jellyfin client with HDR, Picture-in-Picture, Dolby Vision and offline downloads. Simple, private, and ad-free media streaming

this... this is the feature that makes Dotflowy actually do what it was created for. To help me slow down, focus on the right things, and get things done May the Lord bless this tool for people to do a good work

Try it for free (during alpha/beta, and there will be a generous free tier following) app.dotflowy.com invite code: jesus-saves

Powerful filtering added to Dotflowy

app.dotflowy.com :) invite code: jesus-saves

Use your Google account with Dotflowy now :)

@jamonholmgren @mattpocockuk Haha, I like creative chaos but with good boundaries. Matt's good at making those boundaries

@CameronPak @mattpocockuk heck ya. I think my messy trailblazing lands well alongside Matt's dialed and well articulated systems

I'm just going to dump my whole agentic setup out here, because I see too many people missing giant chunks of this and it's hurting them. Here's what I have and recommend: 0. an AGENTS.md that is a router -- it sends the agent to the right skills, docs, tools 1. a standard workflow doc/skill customized to my needs ... (grab Matt Pocock skills if you don't already have something) ... I tag this in most sessions with `@/AGENT_WORKFLOW.md` and it pulls it in. 2. self-healing docs for every system, and agents are instructed to keep them updated ... I tag the ones I know I need, or let the agent find them through AGENTS.md ... I also provide a more detailed summary in the first 7 lines of every doc, so they're easily greppable to find the right thing, and this is documented in AGENTS.md 3. agents always run the app ... the agent should always actually run the app itself, and test its work and fix issues as it goes, especially if running autonomously / asynchronously 4. end-to-end tests and instructions to write more and keep up to date, and docs on how to write tests, what to avoid, and a list of all the tests and what they test in yet another markdown doc ... write and run targeted tests during implementation, improve and commit with work 5. custom linters at precommit hooks looking for any problems you run across, with `--fix` fixing the problems automatically, OR if that's not feasible, it shells out to a cheaper LLM like Composer 2.5 or Sonnet to fix the problems -- NOT just flagging them, but actually resulting in cleaned code 6. cross-agent review at each major point: research, plan, implementation, and wrap-up. I mean codex, claude, cursor, whatever -- but it shouldn't be the same model reviewing the same code. And specific docs for agent review, what to look for, how to approach it. Also, personas -- looking at the code from different perspectives, such as maintainability, code quality, security, performance, AI smells, domains (e.g. "financial services expert" or whatever) ... and each persona also "owns" a set of system docs too and keeps them up to date 7. agent traces / worksheets that track what the agent is doing each session. if the agent fails partway through, you should be able to hand this worksheet to another agent and it could finish the job. commit this worksheet with the work so it's all connected and easy to reference later (you will reference these later!!), also have the agent apply git tags that correspond to specific worksheet names so they're easy to find 8. automatic agent feedback to you at the end of the session, added to a doc that is also committed with the work, that you periodically ingest into an interactive session and improve your workflows 9. a tools or bin folder that contains python or bash scripts that the agent has skills to make to make its job easier (for example, I have an `agent_review` bash script that lets the agent kick off agent reviews via CLI without knowing each agent's particular incantations) ... docs on how to make scripts effectively, and instructions to constantly build these out more 10. periodic agent sweeps through recent commits, looking for problems / gotchas from a higher level across commits 11. a coding conventions doc that is just for specific coding conventions you want to see in the code base, your review agents use these a lot (but a lot of this should be in linters) 12. an agent loop / night shift skill for autonomous work, that lays out how the agent is to approach this, from an orchestration standpoint 13. a task queue that is accessible to the agent (mine is just a TODOS.md, but yours might be in Linear etc, with a CLI to fetch via API) 14. a periodic false-confidence test audit skill that looks for tests that aren't actually testing what you think they're testing, and that fix those 15. visual regression tests -- take screenshots, compare via tool and with agent visual review, commit with work (git lfs useful here) or at least push into the PR 16. automatic performance benchmark tests that notice when performance degrades 17. performance profiling tools that can be used by agents for targeted benchmarking, trying new techniques, comparing outputs, and comparing profiles 18. end-of-shift full validations, including running all tests, performance, agent reviews, sweeps, everything -- when you return, it's all as pristine as it can be If you have all this, your agentic coding experience is going to be very different than dry prompting and manually guiding it toward the right thing every time.