Tag: roo-code
-
Cline and Roo Code: Auditing every tool call before it touches a file
A field-tested take on auditing every tool call before it touches a file with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Picking a model per task instead of per editor
A field-tested take on picking a model per task instead of per editor with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Treating the agent as a shell you can still read
A field-tested take on treating the agent as a shell you can still read with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Memory banks that outlive a single session
A field-tested take on memory banks that outlive a single session with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Logging every turn so you can learn from the agent, not just use it
Cline and Roo Code both keep a task history, but it's built for resuming a session, not for studying one. Logging every turn to a plain file turns a stream of one-off interactions into something you can actually search, compare, and learn a codebase's patterns from.
-
Cline and Roo Code: open-source agents teach you more than closed ones
Cline and Roo Code let you read the exact prompt, the tool definitions and the token bill behind every agent turn. Closed tools hide all three, which is why they're worse to learn from.
-
Cline and Roo Code: Roo modes that codify team-specific workflows
A field-tested take on Roo modes that codify team-specific workflows with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Building an internal guardrails library on top of Cline
A field-tested take on building an internal guardrails library on top of Cline with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Routing cheap models for boilerplate, frontier models for design
A field-tested take on routing cheap models for boilerplate, frontier models for design with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Plan mode as a cheap dry run before committing budget
A field-tested take on plan mode as a cheap dry run before committing budget with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Auditing every tool call before it touches a file
A field-tested take on auditing every tool call before it touches a file with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
-
Cline and Roo Code: Picking a model per task instead of per editor
A field-tested take on picking a model per task instead of per editor with Cline and Roo Code: what it rewards, where it breaks, and how to keep the workflow honest.
More posts tagged roo-code
- Cline and Roo Code: Treating the agent as a shell you can still read
- Cline and Roo Code: Memory banks that outlive a single session
- Cline and Roo Code: Logging every turn so you can learn from the agent, not just use it
- Cline and Roo Code: Why open-source agents are a better teacher than closed ones
- Cline and Roo Code: Roo modes that codify team-specific workflows
- Cline and Roo Code: Building an internal guardrails library on top of Cline
- Cline and Roo Code: Routing cheap models for boilerplate, frontier models for design
- Cline and Roo Code: Plan mode as a cheap dry run before committing budget
- Cline and Roo Code: Auditing every tool call before it touches a file
- Cline and Roo Code: Picking a model per task instead of per editor
- Cline and Roo Code: Teaching juniors by pairing on Cline sessions
- Cline and Roo Code: Plan mode budget that caught a runaway loop early
- Cline and Roo Code: What closed-source agents still did better, and where they did not
- Cline and Roo Code: Quiet pleasure of reading every tool call
- Cline and Roo Code: First month of honest logs from an open-source agent
- Cline and Roo Code: Running Cline against a local LLM for the first time
- Cline and Roo Code: Memory banks as a beginner experiment in agent continuity
- Cline and Roo Code: Picking models per task with almost no data, and learning fast
- Cline and Roo Code: First audit trail that made a security lead smile
- Cline and Roo Code: Cline tool manifests we shared with colleagues over lunch
- Cline and Roo Code: Roo modes that encoded our first team conventions
- Cline and Roo Code: Plan mode as a cheap insurance policy from day one
- Cline and Roo Code: Bring-your-own-key in the early days of model pricing
- Cline and Roo Code: First open-source agent we actually trusted
- Cline and Roo Code: Teaching juniors by pairing on Cline sessions
- Cline and Roo Code: Plan mode budget that caught a runaway loop early
- Cline and Roo Code: What closed-source agents still did better, and where they did not
- Cline and Roo Code: Quiet pleasure of reading every tool call
- Cline and Roo Code: First month of honest logs from an open-source agent
- Cline and Roo Code: Running Cline against a local LLM for the first time
- Cline and Roo Code: Memory banks as a beginner experiment in agent continuity
- Cline and Roo Code: Picking models per task with almost no data, and learning fast
- Cline and Roo Code: First audit trail that made a security lead smile
- Cline and Roo Code: Cline tool manifests we shared with colleagues over lunch
- Cline and Roo Code: Roo modes that encoded our first team conventions
- Cline and Roo Code: Plan mode as a cheap insurance policy from day one
- Cline and Roo Code: Bring-your-own-key in the early days of model pricing
- Cline and Roo Code: First open-source agent we actually trusted