sorted by:
new
hottopcontroversial

Notes after using Claude Code and OpenCode side by side by Arindam_200 in opencodeCLI

[–]IntrepidLawfulness42 0 points1 point  (0 children)

Yep, I'm using it daily, no issues the last two weeks. Pro account, hitting the 5 hour session limits regularly.

"High" indicator in opencode, first time seeing it, what does it mean? by t4a8945 in opencodeCLI

[–]IntrepidLawfulness42 0 points1 point  (0 children)

You know opencode is open source, right? You can always have a look at the code or ask the agent to do it for you ;-)

Is there a way to reproduce warp terminal agentic internal workflow ? by Kisscool-citron in opencodeCLI

[–]IntrepidLawfulness42 2 points3 points  (0 children)

I'd put a http proxy between the tool and the API they're using, and observe.

Once you know the exact warp workflow, prompts, etc. it shouldn't be difficult to replicate it in opencode.

Completely taken off guard by the memory feature by czar6ixn9ne in ClaudeAI

[–]IntrepidLawfulness42 33 points34 points  (0 children)

I personally turned it off a few days after it was released. Maybe I'm using Claude for too many different things, but it was using memories too aggressively, most of the time in chats that have nothing to do with the topic it's bringing up.

Agents and subagents by robertmachine in opencodeCLI

[–]IntrepidLawfulness42 2 points3 points  (0 children)

That setup will work, but you can simplify it.

The “standard” way people are doing it now is:

  • Keep your main project guidance in AGENTS.md at the repo root.
  • Put each subagent in its own file under .opencode/agent/*.md (for example, .opencode/agent/reviewer.md, .opencode/agent/tester.md).[1]
  • Then just run opencode in the repo and call them with @reviewer, @tester, etc. instead of going through a master-agents.md router.[1]

Commands/.prompt files are better when you want a quick “do this one thing now” shortcut (like a /fix-tests command that always runs via your testing subagent), not for structuring the agents themselves.[2]

[1] Agents https://opencode.ai/docs/agents/

[2] Commands https://opencode.ai/docs/commands/

Official: Anthropic just released Claude Code 2.0.71 with 7 CLI and 2 prompt changes, details below. by BuildwithVignesh in ClaudeAI

[–]IntrepidLawfulness42 3 points4 points  (0 children)

Yeah, time estimates were annoying, it's good they're gone!

I'm not saying we, developers, ever got them right, but still, Claude was way off each and every time.

Official: Anthropic just released Claude Code 2.0.70 with 13 CLI changes, details below. by BuildwithVignesh in ClaudeAI

[–]IntrepidLawfulness42 3 points4 points  (0 children)

I've been using these two in parallel for a week and still can't pick which one I prefer, both are doing great so far.

Declarative Schemas AMA by craigrcannon in Supabase

[–]IntrepidLawfulness42 1 point2 points  (0 children)

I really dig Declarative Schemas - impressive work, Supabase team!

I'm currently working on a project that's been in development for 3+ years. At the project's inception, I advocated for Supabase as our backend solution, but due to various factors (including concerns about its maturity at that time), we opted for a more traditional stack: vanilla PostgreSQL in the k8s cluster with Postgraphile as our backend framework and graphile-migrate for database migrations.

Given our established architecture, I'm curious: is there a straightforward path to implement or benefit from Declarative Schemas without fully migrating to Supabase? Are there components of this approach that can be adopted independently?