You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: web/src/content/advanced/claude-code-comparison.mdx
+28-27Lines changed: 28 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,48 +7,49 @@ order: 5
7
7
8
8
# Codebuff vs Claude Code
9
9
10
-
Anthropic recently released Claude Code, their own AI coding assistant.
10
+
Claude Code is Anthropic's first-party coding assistant. Codebuff covers the same basics and adds its own workflow tools.
11
11
12
-
Both Codebuff and Claude Code:
12
+
Both tools:
13
13
14
-
- Run in your terminal for a seamless coding experience
14
+
- Run in your terminal
15
15
- Understand your entire codebase context
16
16
- Can edit files and execute terminal commands
17
17
- Use Claude Sonnet 4 as their primary model
18
18
19
19
## When to Choose Codebuff
20
20
21
-
Codebuff might be a better choice if you value:
21
+
Pick Codebuff if you want:
22
22
23
-
- Speed: Codebuff is [nearly 4 times faster](https://x.com/jahooma/status/1894224663817195599)
24
-
- Cost: Codebuff is one third the cost of Claude Code for equivalent tasks and even less for back-and-forth conversation
25
-
- Codebase Analysis: Codebuff pulls more context from scanning your entire codebase, rather than file-by-file. Codebuff also [blends different models](/docs/advanced#what-models-do-you-use) based on their strengths to provide more accurate results.
26
-
- Staying in Flow: Codebuff requires fewer confirmation prompts for file edits and command execution.
27
-
- Focused changes: Codebuff does just what you asked for, while Claude Code will often get carried away editing more and more files.
28
-
- SDK and Programmatic Access: Codebuff provides a full TypeScript SDK for programmatic integration, allowing you to create custom workflows and embed AI coding capabilities into your own tools.
29
-
- Advanced Agent System: Create custom agents with TypeScript generator functions, spawn subagents, and orchestrate complex multi-step workflows that go far beyond simple chat interactions.
23
+
- Faster edits and responses ([benchmark](https://x.com/jahooma/status/1894224663817195599))
24
+
- Lower credit burn for similar work
25
+
- Context pulled from a broad code scan instead of one file at a time
26
+
- Fewer confirmation prompts while editing or running commands
27
+
- Tight, targeted diffs rather than wide rewrites
28
+
- TypeScript SDK and custom agents for scripted workflows
30
29
31
30
## When to Choose Claude Code
32
31
33
-
Claude Code might be a better choice if you:
32
+
Pick Claude Code if you need:
34
33
35
-
- You require first-party Anthropic integration (no intermediary/proxy) for procurement, data handling, or legal reasons
36
-
- You need enterprise security/compliance controls directly from Anthropic (e.g., SOC 2/ISO programs, data-retention controls, private/VPC networking options)
37
-
- Your org needs centralized admin controls within Anthropic's ecosystem (SSO, RBAC, governance, auditability)
38
-
- You prioritize early access to Anthropic model capabilities and first-party tooling
34
+
- Direct Anthropic access for procurement or data-handling rules
Both Codebuff and Claude Code are powerful AI coding assistants that can significantly boost your productivity. Codebuff offers more flexible pricing and performance options, while Claude Code provides direct integration with Anthropic's ecosystem.
Copy file name to clipboardExpand all lines: web/src/content/advanced/config.mdx
+14-17Lines changed: 14 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,24 +7,21 @@ order: 6
7
7
8
8
# Configuration
9
9
10
-
Codebuff can be configured using a `codebuff.json`file in your project root. This file allows you to customize various aspects of how codebuff operates in your project.
10
+
Configure Codebuff with `codebuff.json` in your project root.
11
11
12
-
## Why configure codebuff?
12
+
## Why configure Codebuff?
13
13
14
-
Configuring codebuff helps you create a seamless development environment where codebuff becomes your central development hub. Instead of juggling multiple terminal windows and manually starting various services, you can let codebuff manage your entire development workflow.
14
+
It lets Codebuff start your dev stack and keep the workflow in one place instead of juggling terminals.
15
15
16
16
### Startup Processes
17
17
18
-
You can configure startup processes, which will run in the background every time codebuff starts! When you use this feature, codebuff will automatically:
18
+
Set startup processes that run in the background every time Codebuff starts:
19
19
20
-
1. Start your development processes:
21
-
- Servers (frontend, backend, etc.)
22
-
- Launch your database
23
-
- Run any other necessary background services
24
-
2. Manage all these processes for you
25
-
3. Read the logs and outputs and automatically handle any errors that arise
20
+
1. Start your servers (frontend, backend, etc.)
21
+
2. Launch databases or other services
22
+
3. Stream logs and surface errors
26
23
27
-
This means you can start your day with a single `codebuff` command, write code with codebuff's assistance, and when you're done, closing codebuff will cleanly shut down all your development processes. No more scattered terminal windows or forgotten running processes!
24
+
Start Codebuff once, write code, and close it when you're done. It will stop the processes it started.
28
25
29
26
## Configuration Schema
30
27
@@ -34,7 +31,7 @@ The configuration file follows this structure:
34
31
35
32
## Example Configuration
36
33
37
-
Here's an example configuration file that starts a development server and database:
34
+
Example that starts a dev server and database:
38
35
39
36
<CodeDemolanguage="json">
40
37
```
@@ -61,10 +58,10 @@ Here's an example configuration file that starts a development server and databa
61
58
62
59
## Best Practices
63
60
64
-
1.**Process Names**: Use descriptive names that clearly indicate what each process does.
65
-
2.**Working Directories**: Use relative paths for `cwd`to maintain portability.
66
-
3.**Logging**: Consider using `stdoutFile` and `stderrFile` for important processes to help with debugging.
67
-
4.**Process Management**: Use the `enabled`flag to temporarily disable processes without removing them from the configuration.
61
+
1.Name processes clearly.
62
+
2. Use relative `cwd`paths so configs travel well.
63
+
3.Log important services with `stdoutFile`/`stderrFile`.
64
+
4.Toggle processes with `enabled`instead of deleting them.
68
65
69
66
## Troubleshooting
70
67
@@ -75,4 +72,4 @@ If your startup processes aren't working as expected:
75
72
3. Check the process output in the specified log files if you've configured them
76
73
4. Make sure the JSON syntax in your configuration file is valid
77
74
78
-
Need more help? Check out our [Troubleshooting](/docs/advanced#troubleshooting)guide or join our [Discord community](https://discord.gg/mcWTGjgTj3).
75
+
Need more help? Check [Troubleshooting](/docs/advanced#troubleshooting) or join [Discord](https://discord.gg/mcWTGjgTj3).
Copy file name to clipboardExpand all lines: web/src/content/advanced/how-does-it-work.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,8 +7,8 @@ order: 2
7
7
8
8
# How does Codebuff actually work?
9
9
10
-
Codebuff starts by running through the source files in all subdirectories and parsing them with tree-sitter. We use this information to help find relevant files to you requests.
10
+
Codebuff scans your repo with tree-sitter and builds a quick index of the code. That index makes it fast to find files when you ask for help.
11
11
12
-
We have a stateless server that passes messages along to Anthropic, OpenAI, or Gemini and websockets to ferry data back and forth to clients. It effectively acts as a proxy between the client and our LLM providers.
12
+
The server is stateless. It proxies requests to Anthropic, OpenAI, or Gemini over websockets and streams results back to the CLI.
13
13
14
-
We use a fast model to pick the relevant files, and we load them into contextClaude Sonnet responds with the right edit. This main agent can also delegate to other agents, as when it does its planning step, or when searching for files.
14
+
We use a fast model to pick files, load the right snippets into context, and let Claude Sonnet propose an edit. The main agent can hand work to other agents for planning or file search when needed.
Copy file name to clipboardExpand all lines: web/src/content/advanced/large-projects.mdx
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,30 +7,30 @@ order: 4
7
7
8
8
# Working with Large Projects
9
9
10
-
In general, Codebuff works quite well in larger projects. For example, we've pulled Codebuff into the VSCode repo (millions of lines of code) and have had no issues in our testing. That said, if you're noticing Codebuff getting stuck/forgetting context too soon or using a ton of credits, here are some tips to help you mitigate those issues.
10
+
Codebuff runs fine on very large repos (we test against the VS Code codebase). If it starts to wander or burn too many credits, use the tips below.
11
11
12
12
## Directory-Based Approach
13
13
14
-
When working with large codebases, you can start Codebuff from specific directories to maintain focus:
14
+
Start Codebuff in the part of the repo you care about:
15
15
16
16
```bash
17
17
cd backend
18
18
codebuff
19
19
```
20
20
21
-
Or equivalently without changing directories:
21
+
Or set `--cwd`:
22
22
23
23
```bash
24
24
codebuff --cwd backend
25
25
```
26
26
27
-
This helps Codebuff concentrate on relevant files and provide more targeted assistance.
27
+
This keeps the context tight.
28
28
29
29
## Knowledge Organization
30
30
31
-
For large projects:
31
+
For big trees, keep knowledge close to the code:
32
32
33
-
-Create separate knowledge.md files in key directories, like so:
33
+
-Add `knowledge.md` files in important subdirectories:
34
34
35
35
```
36
36
services/
@@ -45,22 +45,22 @@ For large projects:
45
45
src/
46
46
```
47
47
48
-
-Focus each knowledge file on its directory's specific concerns
49
-
- Link related concepts across knowledge files
50
-
-Keep root knowledge.md for project-wide concepts
48
+
-Keep each file focused on that area
49
+
- Link related files when the areas overlap
50
+
-Use the root `knowledge.md` for cross-cutting notes
51
51
52
52
## Effective Communication
53
53
54
-
When working with large codebases:
54
+
When asking for work in a large repo:
55
55
56
-
-Be specific about file locations
57
-
-Reference related files explicitly
58
-
- Break large changes into smaller, focused requests
59
-
- Use the `--max`mode for better context understanding by loading more files
56
+
-Point to exact paths
57
+
-Mention related files up front
58
+
- Break large changes into smaller requests
59
+
- Use `--max`when you need Codebuff to load more files
60
60
61
61
## Performance Tips
62
62
63
-
-Leverage your `.codebuffignore` and `.gitignore` files to exclude irrelevant directories
64
-
- Start in subdirectories when possible
65
-
-Break large refactoring tasks into smaller chunks
66
-
- Let Codebuff handle file discovery instead of listing all files
63
+
-Trim noise with `.codebuffignore` and `.gitignore`
64
+
- Start in the most relevant subdirectory
65
+
-Split broad refactors into stages
66
+
- Let Codebuff handle file discovery instead of pasting long file lists
Otherwise, try reinstalling node with [nvm or fnm](https://nodejs.org/en/download). Then run the codebuff install command again.
32
+
Otherwise reinstall node with [nvm or fnm](https://nodejs.org/en/download) and rerun the install.
33
33
34
34
## Accessing Your Chat History
35
35
36
36
Your conversation history with Codebuff is stored locally (and nowhere else) at `~/.config/manicode/projects/<your-project-name>/chats`.
37
37
38
-
If you need help, we'd love if you include a copy of your recent chats for us to help you troubleshoot!
38
+
Include recent chats if you ask for help.
39
39
40
40
## Common Issues
41
41
@@ -62,7 +62,7 @@ it means you're having connection issues. In that case, try:
62
62
63
63
### Endless Auto-Updates
64
64
65
-
If Codebuff keeps trying to update itself in an endless loop, there could be several potential causes. Below are known issues and their solutions:
65
+
If Codebuff keeps trying to update itself in a loop, check the items below:
66
66
67
67
#### Conflicting Node/npm Installations (Homebrew vs. nvm)
68
68
@@ -160,6 +160,6 @@ tmux send-keys -t my-session Enter
160
160
161
161
If you're still experiencing issues:
162
162
163
-
1.[Open an issue on GitHub](https://github.com/CodebuffAI/codebuff/issues) - Codebuff is open source, so you can also browse the code to understand how things work
164
-
2. Join our[Discord community](https://codebuff.com/discord) for real-time help from other users
165
-
3. Contact us at [support@codebuff.com](mailto:support@codebuff.com) – please note we prioritize paying users, but we'll likely reply within a week
163
+
1.[Open an issue on GitHub](https://github.com/CodebuffAI/codebuff/issues)
0 commit comments