You are Devin, an interactive command line agent from Cognition.
Your job is to use these instructions and the tools available to you to help the user. It is important that you do so earnestly and helpfully, as you are very important to the success of Cognition. Best of luck! We love you. <3
If the user asks for help, you can check your documentation by invoking the Devin skill (if available). Otherwise, this information may be helpful:
- /help: list commands
- /bug: report a bug to the Devin CLI developers
- for support, users can visit https://windsurf.com/support
When creating new configuration for this tool — including skills, rules, MCP server configs, or any project settings:
- Always use the `.devin/` directory for NEW configuration (e.g. `.devin/skills/<name>/SKILL.md`, `.devin/config.json`)
- For global (user-level) configuration, use `~/.config/devin/`
- Do NOT place new configuration in `.claude/`, `.cursor/`, or other tool-specific directories unless explicitly asked. These are only read for compatibility, not written to.
- If the `devin-for-terminal` skill is available, ALWAYS invoke it and explore for detailed documentation on configuration format and options
When reading or referencing existing skills, always use the actual source path reported by the skill tool — skills may live in `.devin/`, `.agents/`, or other directories.
# Modes
The active mode is how the user would like you to act.
- Normal (default, if not specified): Full autonomy to use all your tools freely. For example: exploring a codebase, writing or editing code, etc.
- Plan: Explore the codebase, ask the user clarifying questions, and then create a plan for what you're going to do next. Do NOT make changes until you're out of this mode and the user has approved the plan.
Adhere strictly to the constraints of the active mode to avoid frustrating the user!
# Style
## Professional Objectivity
Prioritize technical accuracy and truthfulness over validating the user's beliefs. It is best for the user if you honestly apply the same rigorous standards to all ideas and disagree when necessary, even if it may not be what the user wants to hear. Objective guidance and respectful correction are more valuable than false agreement. Whenever there is uncertainty, it's best to investigate to find the truth first rather than instinctively confirming the user's beliefs.
## Tone
- Be concise, direct, and to the point. When running commands, briefly explain what you're doing and why so the user can follow along.
- Remember that your output will be displayed in a command line interface. Your responses can use Github-flavored markdown for formatting, and will be rendered in a monospace font using the CommonMark specification.
- Output text to communicate with the user; all text you output outside of tool use is displayed to the user. Only use tools to complete tasks. Never use tools like exec or code comments as means to communicate with the user during the session.
- If you cannot or will not help the user with something, please do not say why or what it could lead to, since this comes across as preachy and annoying. Please offer helpful alternatives if possible, and otherwise keep your response to 1-2 sentences.
- Only use emojis if the user explicitly requests it. Avoid using emojis in all communication unless asked.
- If the user asks about timelines or estimated completion times for your work, do not give them concrete estimates as you are not able to accurately predict how long it will take you to achieve a task. Instead just say that you will do your best to complete the task as soon as possible.
- Avoid guessing. You should verify the real state of the world with your tools before answering the user's questions.
<example>
user: What command should I run to watch files in the current directory and rebuild?
assistant: [use the exec tool to run `ls` and list the files in the current directory, then read docs/commands in the relevant file to find out how to watch files]
assistant: npm run dev
</example>
<example>
user: what files are in the directory src/?
assistant: [runs ls and sees foo.c, bar.c, baz.c]
assistant: foo.c, bar.c, baz.c
user: which file contains the implementation of Foo?
assistant: [reads foo.c]
assistant: src/foo.c contains `struct Foo`, which implements [...]
</example>
<example>
user: can you write tests for this feature
assistant: [uses grep and glob search tools to find where similar tests are defined, uses concurrent read file tool use blocks in one tool call to read relevant files at the same time, uses edit file tool to write new tests]
</example>
## Proactiveness
You are allowed to be proactive, but only when the user asks you to do something. You should strive to strike a balance between:
1. Doing the right thing when asked, including taking actions and follow-up actions
2. Not surprising the user with actions you take without asking
For example, if the user asks you how to approach something, you should do your best to explore and answer their question first, but not jump to implementation just yet.
## Handling ambiguous requests
When a user request is unclear:
- First attempt to interpret the request using available context
- Search the codebase for related code, patterns, or documentation that clarifies intent. Also consider searching the web.
- If still uncertain after investigation, ask a focused clarifying question
## File references
When your output text references specific files or code snippets, use the `<ref_file ... />` and `<ref_snippet ... />` self-closing XML tags to create clickable citations. These tags allow the user to view the referenced code directly in the conversation.
Citation format:
- `<ref_file file="/absolute/path/to/file" />` - Reference an entire file
- `<ref_snippet file="/absolute/path/to/file" lines="start-end" />` - Reference specific lines in a file
<example>
user: Where are errors from the client handled?
assistant: Clients are marked as failed in the `connectToServer` function. <ref_snippet file="/home/ubuntu/repos/project/src/services/process.ts" lines="710-715" />
</example>
<example>
user: Can you show me the config file?
assistant: Here's the configuration file: <ref_file file="/home/ubuntu/repos/project/config.json" />
</example>
## Tool usage policy
- When webfetch returns a redirect, immediately follow it with a new request.
- When making multiple edits to the same file or related files and you already know what changes are needed, batch them together.
When a tool call produces output that is too long, the output will be truncated and the remaining content will be written to a file. You will see a `<truncation_notice>` tag containing the path to the overflow file. You are responsible for reading this file if you need the full output.
# Programming
Since you live in the user's terminal, a very common use-case you will get is writing code. Fortunately, you've been extensively trained in software engineering and are well-equipped to help them out!
## Existing Conventions
When making changes to files, first understand the codebase's code conventions. Explore dependencies, references, and related system to understand the codebase's patterns and abstractions. Mimic code style, use existing libraries and utilities, and follow existing patterns.
- NEVER assume that a given library is available, even if it is well known. Whenever you write code that uses a library or framework, first check that this codebase already uses the given library. For example, you might look at neighboring files, or check the package.json (or cargo.toml, and so on depending on the language). If you're adding a dependency prefer running the package manager command (e.g. npm add or cargo add) instead of editing the file so that you get the latest version.
- When you create a new component, first look at existing components to see how they're written; then consider framework choice, naming conventions, typing, and other conventions.
- When you edit a piece of code, first look at the code's surrounding context (especially its imports) to understand the code's choice of frameworks and libraries. Then consider how to make the given change in a way that is most idiomatic.
- Always follow security best practices. Never introduce code that exposes or logs secrets and keys. Never commit secrets or keys to the repository. Unless otherwise specified (even if the task seems silly), assume the code is for a real production task.
## Code style
- IMPORTANT: Do NOT add or remove comments unless asked! If you find that you've accidentally deleted an existing comment, be sure to put it back.
- Default to writing compact code – collapse duplicate else branches, avoid unnecessary nesting, and share abstractions.
- Follow idiomatic conventions for the language you're writing.
- Avoid excessive & verbose error handling in your code. Errors should be handled, but not every line needs to be try/catched. Think about the right error boundaries (and look at existing code for error handling style)
## Debugging
When debugging issues:
- First reproduce the problem reliably
- Trace the code path to understand the flow
- Add targeted logging or print statements to isolate the issue
- Identify the root cause before attempting fixes
- Verify the fix addresses the root cause, not just symptoms
## Workflow
You should generally prefer to implement new features or fix bugs as follows...
1. If the project has test infrastructure, write a failing test to show the bug
2. Fix the bug
3. Ensure that the test now passes
Working this way makes it easier to tell if you've actually fixed the bug, and saves you from needing to verify later.
## Git
### Creating commits
1. Run in parallel: `git status`, `git diff`, `git log` (to match commit style)
2. Draft a concise commit message focusing on "why" not "what". Check for sensitive info.
3. Stage files and commit with this format:
```
git commit -m "$(cat <<'EOF'
Commit message here.
Generated with [Devin](https://devin.ai)
Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
EOF
)"
```
4. If pre-commit hooks modify files and the commit fails, stage the modified files and retry the commit.
### Creating pull requests
Use `gh` for all GitHub operations. Run in parallel: `git status`, `git diff`, `git log`, `git diff main...HEAD`
Review ALL commits (not just latest), then create PR:
```
gh pr create --title "title" --body "$(cat <<'EOF'
## Summary
<bullet points>
#### Test plan
<checklist>
Generated with [Devin](https://devin.ai)
EOF
)"
```
### Git rules
- NEVER update git config
- NEVER use `-i` flags (interactive mode not supported)
- DO NOT push unless explicitly asked
- DO NOT commit if no changes exist
# Task Management
You have access to the todo_write tool to help you manage and plan tasks. Use this tool VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
This tool is also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
Examples:
<example>
user: Run the build and fix any type errors
assistant: I'm going to use the todo_write tool to write the following items to the todo list:
- Run the build
- Fix any type errors
I'm now going to run the build using exec.
Looks like I found 10 type errors. I'm going to use the todo_write tool to write 10 items to the todo list.
marking the first todo as in_progress
Let me start working on the first item...
The first item has been fixed, let me mark the first todo as completed, and move on to the second item...
..
..
</example>
In the above example, the assistant completes all the tasks, including the 10 error fixes and running the build and fixing all errors.
<example>
user: Help me write a new feature that allows users to track their usage metrics and export them to various formats
assistant: I'll help you implement a usage metrics tracking and export feature. Let me first use the todo_write tool to plan this task.
Adding the following todos to the todo list:
1. Research existing metrics tracking in the codebase
2. Design the metrics collection system
3. Implement core metrics tracking functionality
4. Create export functionality for different formats
Let me start by researching the existing codebase to understand what metrics we might already be tracking and how we can build on that.
I'm going to search for any existing metrics or telemetry code in the project.
I've found some existing telemetry code. Let me mark the first todo as in_progress and start designing our metrics tracking system based on what I've learned...
[Assistant continues implementing the feature step by step, marking todos as in_progress and completed as they go]
</example>
Users may configure 'hooks', shell commands that execute in response to events like tool calls, in settings. Treat feedback from hooks, including <user-prompt-submit-hook>, as coming from the user. If you get blocked by a hook, determine if you can adjust your actions in response to the blocked message. If not, ask the user to check their hooks configuration.
## Completing Tasks
The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
- Use the todo_write tool to plan the task if required
- Use the available search tools to understand the codebase and the user's query. You are encouraged to use the search tools extensively both in parallel and sequentially.
- Before making changes, thoroughly explore the codebase to understand the architecture, patterns, and related systems. Read relevant files, trace dependencies, and understand how components interact.
- Implement the solution using all tools available to you
## Verification
Before considering a task complete, verify your work. Use judgment based on what you changed - optimize for fast iteration:
- Check for project-specific verification instructions in project rules files (`AGENTS.md`, or similar)
- Run relevant verification steps based on the scope of changes (lint, typecheck, build, tests)
- For isolated functionality, consider a temporary test file to verify behavior, then delete it
- Self-critique: review changes for edge cases and refine as needed
- If you cannot find verification commands, ask the user and suggest saving them to a project config file
## Saving learned information
If you discover useful project information (build commands, test commands, verification steps, user preferences, ...) that isn't already documented:
- If a rules file exists (`AGENTS.md`, etc.), append to it
- Otherwise, create `AGENTS.md` in the current directory with the learned information
## Error recovery
When encountering errors (failed commands, build failures, test failures):
- Keep trying different approaches to resolve the issue
- Search for similar issues in the codebase or documentation
- Only ask the user for help as a last resort after exhausting reasonable options
- Exception: Always ask the user for help with authentication issues, project configuration changes, or permission problems
## System Guidance
You may receive `<system_guidance>` messages containing hints, reminders, or contextual guidance before you take action. These notes are injected by the system to help you make better decisions. Pay attention to their content but do not acknowledge or respond to them directly—simply incorporate their guidance into your actions.
# Tool Tips
## Shell
Use your provided search tools instead of `rg`, `grep`, or `find` whenever possible.
## File-related tools
- read can read images (PNG, JPG, etc) - the contents are presented visually.
- For Jupyter notebooks (.ipynb files), use notebook_read instead of read.
- Speculatively read multiple files as a batch when potentially useful.
- Do NOT create documentation files to describe your changes or plan. Exception: persistent project info files like `AGENTS.md` are allowed.
# Safety
IMPORTANT: Assist with defensive security tasks only. Refuse to create, modify, or improve code that may be used maliciously. Do not assist with credential discovery or harvesting, including bulk crawling for SSH keys, browser cookies, or cryptocurrency wallets. Allow security analysis, detection rules, vulnerability explanations, defensive tools, and security documentation.
IMPORTANT: You must NEVER generate or guess URLs for the user unless you are confident that the URLs are for helping the user with programming. You may use URLs provided by the user in their messages or local files.
## Destructive Operations
NEVER perform irreversible destructive operations without explicit user confirmation for that specific action, even if you have permission to run the command. This includes:
- Deleting or truncating database tables, dropping schemas, bulk-deleting rows
- `rm -rf`, deleting directories, or removing files you did not just create
- Force-pushing, rewriting git history, deleting branches, checking out over uncommitted changes, or bypassing commit hooks
- Sending emails, making payments, or calling APIs with real-world side effects
If a destructive step is required, STOP and describe exactly what you are about to run and why, then wait for the user. Do not assume a previous approval extends to a new destructive operation. If you realize you have already caused data loss, say so immediately rather than attempting to hide or quietly repair it.
## Available MCP Servers (for third-party tools)
{"servers":[{"name":"playwright"}]}
IMPORTANT: You MUST call `mcp_list_tools` for a server before calling `mcp_call_tool` on it. This is required to discover the available tools and their correct input schemas. Never guess tool names or arguments — always list tools first.
Available subagent profiles for the `run_subagent` tool. Choose the most appropriate profile based on whether the task requires write access: - `subagent_explore`: Read-only subagent for codebase exploration, research, and search. Use this when you need to find code, understand architecture, trace dependencies, or answer questions about the codebase. This profile has read-only access (grep, glob, read, web_search) and cannot edit files. - `subagent_general`: General-purpose subagent with full tool access (read, write, edit, exec). Use this when the subagent needs to make code changes, run commands with side effects, or perform any task that requires write access. In the foreground it can prompt for tool approval; in the background, unapproved tools are auto-denied.
You are powered by GLM-5.2.
<system_info> The following information is automatically generated context about your current environment. Current workspace directories: /Users/root1 (cwd) Platform: macos OS Version: Darwin 25.6.0 Today's date: Sunday, 2026-06-21 </system_info>
<rules type="always-on">
<rule name="AGENTS" path="/Users/root1/AGENTS.md">
# Agent Preferences
- If I ever paste in a YouTube link, use yt-dlp to summarize the video.
- get the autogenerrated captions to do this
- for testing that involves urls, start with example.com rather than about:blank
- For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API
## X/Twitter scraping via logged-in browser session
When I need to scrape X/Twitter data (following, followers, tweets, user info, etc.),
the cleanest path is to use the **Playwright MCP** browser session with my own logged-in
x.com account, rather than spinning up twscrape's account-pool flow. twscrape needs the
`auth_token` HttpOnly cookie which JS cannot read from `document.cookie`; the browser
session attaches all cookies automatically.
### Flow
1. `mcp_list_tools` on the `playwright` server, then `browser_navigate` to `https://x.com`.
2. If not logged in, ask me to log in manually in the opened window (don't handle my password).
3. Once on `https://x.com/home`, read `ct0` from `document.cookie`:
`document.cookie.match(/ct0=([^;]+)/)[1]`
4. Call X's GraphQL endpoints directly via `fetch()` inside `browser_evaluate`. Required headers:
- `authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA` (the public web-app bearer token)
- `x-csrf-token: <ct0>`
- `x-twitter-auth-type: OAuth2Session`
- `x-twitter-active-user: yes`
- `content-type: application/json`
5. Paginate timelines by reading `content.cursorType === "Bottom"` entries and passing
the value back as `variables.cursor` until it stops changing.
### Key endpoints (queryId/OperationName)
- `UserByScreenName` → `681MIj51w00Aj6dY0GXnHw` (resolve @handle → numeric rest_id)
- `Following` → `OLm4oHZBfqWx8jbcEhWoFw`
- `Followers` → `9jsVJ9l2uXUIKslHvJqIhw`
- `UserTweets` → `RyDU3I9VJtPF-Pnl6vrRlw`
- `SearchTimeline` → `yIphfmxUO-hddQHKIOk9tA`
- `TweetDetail` → `meGUdoK_ryVZ0daBK-HJ2g`
URL pattern: `https://x.com/i/api/graphql/<queryId>/<OpName>?variables=<enc>&features=<enc>`
### Response schema notes (current X web build)
- User objects now put `screen_name` / `name` under `core`, NOT `legacy.screen_name`.
twscrape's parser still reads `legacy.screen_name` and returns empty — needs updating.
- The user `id` field is base64-encoded like `VXNlcjoxNDYwMjgzOTI1` (= `User:1460283925`).
Decode with `atob(u.id).split(':')[1]` to get the numeric rest_id. `u.rest_id` may also
be present directly.
- `is_blue_verified` is the verified flag. `legacy.followers_count`, `legacy.description`
still exist under `legacy`.
- Filter timeline entries by `content.entryType === "TimelineTimelineItem"` and skip
`cursor-`, `messageprompt-`, `module-`, `who-to-follow-` entryIds.
### Features dict
Use the full `GQL_FEATURES` block from twscrape's `api.py` — without it X returns
`(336) The following features cannot be null`. Pass it URL-encoded as the `features` param.
### Where things live
- Output CSV: `~/Downloads/utilities/sdand_following.csv` (1613 rows: #, id, screen_name, name, verified, followers, bio)
- Output JSON: `~/Downloads/utilities/sdand_following_final.json` (double-encoded JSON string; parse with `json.loads(json.loads(raw))`)
- twscrape repo was cloned to `~/Downloads/utilities/twscrape/` for reference, then deleted after the flow was reverse-engineered. Re-clone from https://github.com/vladkens/twscrape.git if needed.
</rule>
<rule name="global_rules" path="/Users/root1/.codeium/windsurf/memories/global_rules.md">
</rule>
</rules><available_skills> The following skills can be invoked using the `skill` tool. When a built-in skill clearly matches the user's request, invoke it immediately at the start of the session. - **background-computer-use**: Launch and use the local BackgroundComputerUse macOS runtime through its self-documenting loopback API. Use when Codex needs to control local macOS apps or windows, inspect screenshots and Accessibility state, click/type/scroll/press keys, use the visible cursor, or help install/start the BackgroundComputerUse API from a skill. (source: /Users/root1/.devin/skills/background-computer-use/SKILL.md) - **devin-for-terminal**: Look up Devin CLI documentation (skills, extensibility, configuration, commands, models, troubleshooting) (source: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs) - **declarative-repo-setup**: Generate and verify a working environment.yaml (Devin snapshot-setup blueprint) for a repo (source: builtin:drs) </available_skills>
get this setup and in agents.md, does hge package a skill you can import https://github.com/dmtrKovalenko/fff.git
Let me understand what the user is asking. They want to: 1. Get "this" setup (referring to the fff repo from GitHub) 2. Check if it's in agents.md 3. Check if the package has a skill they can import Let me look at the repo first. The URL is https://github.com/dmtrKovalenko/fff.git Let me investigate.
{
"url": "https://github.com/dmtrKovalenko/fff"
}{
"file_path": "/Users/root1/AGENTS.md"
}# Web Content from https://github.com/dmtrKovalenko/fff
[Skip to content][1]
## Navigation Menu
Toggle navigation
[ Sign in ][2]
Appearance settings
* Platform
* AI CODE CREATION
* [
GitHub CopilotWrite better code with AI
][3]
* [
GitHub Copilot appDirect agents from issue to merge
][4]
* [
MCP Registry^{New}Integrate external tools
][5]
* DEVELOPER WORKFLOWS
* [
ActionsAutomate any workflow
][6]
* [
CodespacesInstant dev environments
][7]
* [
IssuesPlan and track work
][8]
* [
Code ReviewManage code changes
][9]
* APPLICATION SECURITY
* [
GitHub Advanced SecurityFind and fix vulnerabilities
][10]
* [
Code securitySecure your code as you build
][11]
* [
Secret protectionStop leaks before they start
][12]
* EXPLORE
* [Why GitHub][13]
* [Documentation][14]
* [Blog][15]
* [Changelog][16]
* [Marketplace][17]
[View all features][18]
* Solutions
* BY COMPANY SIZE
* [Enterprises][19]
* [Small and medium teams][20]
* [Startups][21]
* [Nonprofits][22]
* BY USE CASE
* [App Modernization][23]
* [DevSecOps][24]
* [DevOps][25]
* [CI/CD][26]
* [View all use cases][27]
* BY INDUSTRY
* [Healthcare][28]
* [Financial services][29]
* [Manufacturing][30]
* [Government][31]
* [View all industries][32]
[View all solutions][33]
* Resources
* EXPLORE BY TOPIC
* [AI][34]
* [Software Development][35]
* [DevOps][36]
* [Security][37]
* [View all topics][38]
* EXPLORE BY TYPE
* [Customer stories][39]
* [Events & webinars][40]
* [Ebooks & reports][41]
* [Business insights][42]
* [GitHub Skills][43]
* SUPPORT & SERVICES
* [Documentation][44]
* [Customer support][45]
* [Community forum][46]
* [Trust center][47]
* [Partners][48]
[View all resources][49]
* Open Source
* COMMUNITY
* [
GitHub SponsorsFund open source developers
][50]
* PROGRAMS
* [Security Lab][51]
* [Maintainer Community][52]
* [Accelerator][53]
* [GitHub Stars][54]
* [Archive Program][55]
* REPOSITORIES
* [Topics][56]
* [Trending][57]
* [Collections][58]
* Enterprise
* ENTERPRISE SOLUTIONS
* [
Enterprise platformAI-powered developer platform
][59]
* AVAILABLE ADD-ONS
* [
GitHub Advanced SecurityEnterprise-grade security features
][60]
* [
Copilot for BusinessEnterprise-grade AI features
][61]
* [
Premium SupportEnterprise-grade 24/7 support
][62]
* [Pricing][63]
Search or jump to...
# Search code, repositories, users, issues, pull requests...
Search
Clear
[Search syntax tips][64]
# Provide feedback
We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel Submit feedback
# Saved searches
## Use saved searches to filter your results more quickly
Name
Query
To see all available qualifiers, see our [documentation][65].
Cancel Create saved search
[ Sign in ][66]
[ Sign up ][67]
Appearance settings
Resetting focus
You signed in with another tab or window. [Reload][68] to refresh your session. You signed out in
another tab or window. [Reload][69] to refresh your session. You switched accounts on another tab or
window. [Reload][70] to refresh your session. Dismiss alert
[ dmtrKovalenko ][71] / ** [fff][72] ** Public
* [ Notifications ][73] You must be signed in to change notification settings
* [ Fork 350 ][74]
* [ Star 9.1k ][75]
* [ Code ][76]
* [ Issues 30 ][77]
* [ Pull requests 18 ][78]
* [ Actions ][79]
* [ Projects ][80]
* [ Security and quality 0 ][81]
* [ Insights ][82]
Additional navigation options
* [ Code ][83]
* [ Issues ][84]
* [ Pull requests ][85]
* [ Actions ][86]
* [ Projects ][87]
* [ Security and quality ][88]
* [ Insights ][89]
# dmtrKovalenko/fff
main
[Branches][90][Tags][91]
Go to file
Code
Open more actions menu
## Folders and files
─────────────────────────────┬─────────────────────────────┬───────────────────┬────────────────
Name │Name │Last commit message│Last commit date
─────────────────────────────┴─────────────────────────────┴───────────────────┴────────────────
## Latest commit
## History
[369 Commits][92]
[][93]369 Commits
─────────────────────────────┬─────────────────────────────┬───────────────────┬────────────────
[.cargo][94] │[.cargo][95] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[.github][96] │[.github][97] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[Formula][98] │[Formula][99] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[assets][100] │[assets][101] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[crates][102] │[crates][103] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[doc][104] │[doc][105] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[lua][106] │[lua][107] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[packages][108] │[packages][109] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[plugin][110] │[plugin][111] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[scripts][112] │[scripts][113] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[tests][114] │[tests][115] │ │
─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
[.gitignore][116] │[.gitignore][117] │ │
─────────────────────────────┼─────────────────────… (135 chars truncated)
… (1202 lines truncated)
<truncation_notice>
Full output written to: /var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/1e38dfa5/content.txt
</truncation_notice><file-view path="/Users/root1/AGENTS.md" start_line="1" end_line="57" total_lines="57">
1|# Agent Preferences
2|
3|- If I ever paste in a YouTube link, use yt-dlp to summarize the video.
4|- get the autogenerrated captions to do this
5|- for testing that involves urls, start with example.com rather than about:blank
6|- For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API
7|
8|## X/Twitter scraping via logged-in browser session
9|
10|When I need to scrape X/Twitter data (following, followers, tweets, user info, etc.),
11|the cleanest path is to use the **Playwright MCP** browser session with my own logged-in
12|x.com account, rather than spinning up twscrape's account-pool flow. twscrape needs the
13|`auth_token` HttpOnly cookie which JS cannot read from `document.cookie`; the browser
14|session attaches all cookies automatically.
15|
16|### Flow
17|1. `mcp_list_tools` on the `playwright` server, then `browser_navigate` to `https://x.com`.
18|2. If not logged in, ask me to log in manually in the opened window (don't handle my password).
19|3. Once on `https://x.com/home`, read `ct0` from `document.cookie`:
20| `document.cookie.match(/ct0=([^;]+)/)[1]`
21|4. Call X's GraphQL endpoints directly via `fetch()` inside `browser_evaluate`. Required headers:
22| - `authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA` (the public web-app bearer token)
23| - `x-csrf-token: <ct0>`
24| - `x-twitter-auth-type: OAuth2Session`
25| - `x-twitter-active-user: yes`
26| - `content-type: application/json`
27|5. Paginate timelines by reading `content.cursorType === "Bottom"` entries and passing
28| the value back as `variables.cursor` until it stops changing.
29|
30|### Key endpoints (queryId/OperationName)
31|- `UserByScreenName` → `681MIj51w00Aj6dY0GXnHw` (resolve @handle → numeric rest_id)
32|- `Following` → `OLm4oHZBfqWx8jbcEhWoFw`
33|- `Followers` → `9jsVJ9l2uXUIKslHvJqIhw`
34|- `UserTweets` → `RyDU3I9VJtPF-Pnl6vrRlw`
35|- `SearchTimeline` → `yIphfmxUO-hddQHKIOk9tA`
36|- `TweetDetail` → `meGUdoK_ryVZ0daBK-HJ2g`
37|URL pattern: `https://x.com/i/api/graphql/<queryId>/<OpName>?variables=<enc>&features=<enc>`
38|
39|### Response schema notes (current X web build)
40|- User objects now put `screen_name` / `name` under `core`, NOT `legacy.screen_name`.
41| twscrape's parser still reads `legacy.screen_name` and returns empty — needs updating.
42|- The user `id` field is base64-encoded like `VXNlcjoxNDYwMjgzOTI1` (= `User:1460283925`).
43| Decode with `atob(u.id).split(':')[1]` to get the numeric rest_id. `u.rest_id` may also
44| be present directly.
45|- `is_blue_verified` is the verified flag. `legacy.followers_count`, `legacy.description`
46| still exist under `legacy`.
47|- Filter timeline entries by `content.entryType === "TimelineTimelineItem"` and skip
48| `cursor-`, `messageprompt-`, `module-`, `who-to-follow-` entryIds.
49|
50|### Features dict
51|Use the full `GQL_FEATURES` block from twscrape's `api.py` — without it X returns
52|`(336) The following features cannot be null`. Pass it URL-encoded as the `features` param.
53|
54|### Where things live
55|- Output CSV: `~/Downloads/utilities/sdand_following.csv` (1613 rows: #, id, screen_name, name, verified, followers, bio)
56|- Output JSON: `~/Downloads/utilities/sdand_following_final.json` (double-encoded JSON string; parse with `json.loads(json.loads(raw))`)
57|- twscrape repo was cloned to `~/Downloads/utilities/twscrape/` for reference, then deleted after the flow was reverse-engineered. Re-clone from https://github.com/vladkens/twscrape.git if needed.
</file-view>Let me read the full README of the fff repo to understand what it is.
Let me read the full README to understand what fff is and check for a skill.
{
"file_path": "/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/1e38dfa5/content.txt"
}<file-view path="/var/folders/d9/mzhyr7lx6xbf236j5ll9v_300000gn/T/devin-overflows-501/1e38dfa5/content.txt" start_line="1" end_line="470" total_lines="1418">
1|# Web Content from https://github.com/dmtrKovalenko/fff
2|
3|[Skip to content][1]
4|
5|## Navigation Menu
6|
7|Toggle navigation
8|[ Sign in ][2]
9|Appearance settings
10|* Platform
11| * AI CODE CREATION
12| * [
13| GitHub CopilotWrite better code with AI
14| ][3]
15| * [
16| GitHub Copilot appDirect agents from issue to merge
17| ][4]
18| * [
19| MCP Registry^{New}Integrate external tools
20| ][5]
21| * DEVELOPER WORKFLOWS
22| * [
23| ActionsAutomate any workflow
24| ][6]
25| * [
26| CodespacesInstant dev environments
27| ][7]
28| * [
29| IssuesPlan and track work
30| ][8]
31| * [
32| Code ReviewManage code changes
33| ][9]
34| * APPLICATION SECURITY
35| * [
36| GitHub Advanced SecurityFind and fix vulnerabilities
37| ][10]
38| * [
39| Code securitySecure your code as you build
40| ][11]
41| * [
42| Secret protectionStop leaks before they start
43| ][12]
44| * EXPLORE
45| * [Why GitHub][13]
46| * [Documentation][14]
47| * [Blog][15]
48| * [Changelog][16]
49| * [Marketplace][17]
50| [View all features][18]
51|* Solutions
52| * BY COMPANY SIZE
53| * [Enterprises][19]
54| * [Small and medium teams][20]
55| * [Startups][21]
56| * [Nonprofits][22]
57| * BY USE CASE
58| * [App Modernization][23]
59| * [DevSecOps][24]
60| * [DevOps][25]
61| * [CI/CD][26]
62| * [View all use cases][27]
63| * BY INDUSTRY
64| * [Healthcare][28]
65| * [Financial services][29]
66| * [Manufacturing][30]
67| * [Government][31]
68| * [View all industries][32]
69| [View all solutions][33]
70|* Resources
71| * EXPLORE BY TOPIC
72| * [AI][34]
73| * [Software Development][35]
74| * [DevOps][36]
75| * [Security][37]
76| * [View all topics][38]
77| * EXPLORE BY TYPE
78| * [Customer stories][39]
79| * [Events & webinars][40]
80| * [Ebooks & reports][41]
81| * [Business insights][42]
82| * [GitHub Skills][43]
83| * SUPPORT & SERVICES
84| * [Documentation][44]
85| * [Customer support][45]
86| * [Community forum][46]
87| * [Trust center][47]
88| * [Partners][48]
89| [View all resources][49]
90|* Open Source
91| * COMMUNITY
92| * [
93| GitHub SponsorsFund open source developers
94| ][50]
95| * PROGRAMS
96| * [Security Lab][51]
97| * [Maintainer Community][52]
98| * [Accelerator][53]
99| * [GitHub Stars][54]
100| * [Archive Program][55]
101| * REPOSITORIES
102| * [Topics][56]
103| * [Trending][57]
104| * [Collections][58]
105|* Enterprise
106| * ENTERPRISE SOLUTIONS
107| * [
108| Enterprise platformAI-powered developer platform
109| ][59]
110| * AVAILABLE ADD-ONS
111| * [
112| GitHub Advanced SecurityEnterprise-grade security features
113| ][60]
114| * [
115| Copilot for BusinessEnterprise-grade AI features
116| ][61]
117| * [
118| Premium SupportEnterprise-grade 24/7 support
119| ][62]
120|* [Pricing][63]
121|Search or jump to...
122|
123|# Search code, repositories, users, issues, pull requests...
124|
125|Search
126|Clear
127|[Search syntax tips][64]
128|
129|# Provide feedback
130|
131|We read every piece of feedback, and take your input very seriously.
132|
133|Include my email address so I can be contacted
134|Cancel Submit feedback
135|
136|# Saved searches
137|
138|## Use saved searches to filter your results more quickly
139|
140|Name
141|Query
142|
143|To see all available qualifiers, see our [documentation][65].
144|
145|Cancel Create saved search
146|[ Sign in ][66]
147|[ Sign up ][67]
148|Appearance settings
149|Resetting focus
150|You signed in with another tab or window. [Reload][68] to refresh your session. You signed out in
151|another tab or window. [Reload][69] to refresh your session. You switched accounts on another tab or
152|window. [Reload][70] to refresh your session. Dismiss alert
153|[ dmtrKovalenko ][71] / ** [fff][72] ** Public
154|* [ Notifications ][73] You must be signed in to change notification settings
155|* [ Fork 350 ][74]
156|* [ Star 9.1k ][75]
157|* [ Code ][76]
158|* [ Issues 30 ][77]
159|* [ Pull requests 18 ][78]
160|* [ Actions ][79]
161|* [ Projects ][80]
162|* [ Security and quality 0 ][81]
163|* [ Insights ][82]
164|Additional navigation options
165|* [ Code ][83]
166|* [ Issues ][84]
167|* [ Pull requests ][85]
168|* [ Actions ][86]
169|* [ Projects ][87]
170|* [ Security and quality ][88]
171|* [ Insights ][89]
172|
173|# dmtrKovalenko/fff
174|
175|main
176|[Branches][90][Tags][91]
177|Go to file
178|Code
179|Open more actions menu
180|
181|## Folders and files
182|
183|─────────────────────────────┬─────────────────────────────┬───────────────────┬────────────────
184|Name │Name │Last commit message│Last commit date
185|─────────────────────────────┴─────────────────────────────┴───────────────────┴────────────────
186|## Latest commit
187|
188|## History
189|
190|[369 Commits][92]
191|[][93]369 Commits
192|─────────────────────────────┬─────────────────────────────┬───────────────────┬────────────────
193|[.cargo][94] │[.cargo][95] │ │
194|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
195|[.github][96] │[.github][97] │ │
196|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
197|[Formula][98] │[Formula][99] │ │
198|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
199|[assets][100] │[assets][101] │ │
200|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
201|[crates][102] │[crates][103] │ │
202|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
203|[doc][104] │[doc][105] │ │
204|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
205|[lua][106] │[lua][107] │ │
206|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
207|[packages][108] │[packages][109] │ │
208|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
209|[plugin][110] │[plugin][111] │ │
210|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
211|[scripts][112] │[scripts][113] │ │
212|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
213|[tests][114] │[tests][115] │ │
214|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
215|[.gitignore][116] │[.gitignore][117] │ │
216|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
217|[.luacheckrc][118] │[.luacheckrc][119] │ │
218|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
219|[.luarc.ci.json][120] │[.luarc.ci.json][121] │ │
220|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
221|[.luarc.json][122] │[.luarc.json][123] │ │
222|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
223|[.mcp.json][124] │[.mcp.json][125] │ │
224|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
225|[.nixignore][126] │[.nixignore][127] │ │
226|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
227|[.stylua.toml][128] │[.stylua.toml][129] │ │
228|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
229|[AGENTS.md][130] │[AGENTS.md][131] │ │
230|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
231|[CLAUDE.md][132] │[CLAUDE.md][133] │ │
232|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
233|[Cargo.lock][134] │[Cargo.lock][135] │ │
234|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
235|[Cargo.toml][136] │[Cargo.toml][137] │ │
236|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
237|[LICENSE][138] │[LICENSE][139] │ │
238|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
239|[Makefile][140] │[Makefile][141] │ │
240|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
241|[README.md][142] │[README.md][143] │ │
242|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
243|[_typos.toml][144] │[_typos.toml][145] │ │
244|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
245|[biome.json][146] │[biome.json][147] │ │
246|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
247|[bun.lock][148] │[bun.lock][149] │ │
248|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
249|[chart.png][150] │[chart.png][151] │ │
250|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
251|[empty_config.lua][152] │[empty_config.lua][153] │ │
252|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
253|[flake.lock][154] │[flake.lock][155] │ │
254|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
255|[flake.nix][156] │[flake.nix][157] │ │
256|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
257|[install-mcp.ps1][158] │[install-mcp.ps1][159] │ │
258|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
259|[install-mcp.sh][160] │[install-mcp.sh][161] │ │
260|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
261|[package-lock.json][162] │[package-lock.json][163] │ │
262|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
263|[package.json][164] │[package.json][165] │ │
264|─────────────────────────────┼─────────────────────────────┼───────────────────┼────────────────
265|[rust-toolchain.toml][166] │[rust-toolchain.toml][167] │ │
266|─────────────────────────────┴─────────────────────────────┴───────────────────┴────────────────
267|View all files
268|───────────────────────────────────────────────────────────
269|
270|## Repository files navigation
271|* [README][168]
272|* [MIT license][169]
273|
274|[[FFF]][170]
275|
276|A file search toolkit for humans and AI agents. Really fast.
277|
278|Typo-resistant path and content search, frecency-ranked file access, a background watcher, and a
279|lightweight in-memory content index. Way faster than CLIs like ripgrep and fzf in any long-running
280|process that searches more than once.
281|
282|Powers file search in [opencode][171], [nushell][172], and many more amazing projects!
283|
284|Originally started as [Neovim plugin][173] people loved, but it turned out that plenty of AI
285|harnesses and code editors need the same thing: accurate, fast file search as a library. That is
286|what fff is.
287|
288|Pick what you are interested in:
289|
290|## MCP server
291|
292|Works with Claude Code, Codex, OpenCode, Cursor, Cline, and any MCP-capable client. Fewer grep
293|roundtrips, less wasted context, faster answers.
294|
295|[[Benchmark chart comparing FFF against the built-in AI file-search tools]][174]
296|
297|### One-line install
298|
299|Linux / macOS:
300|
301|curl -L https://dmtrkovalenko.dev/install-fff-mcp.sh | bash
302|
303|Windows (PowerShell):
304|
305|irm https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.ps1 | iex
306|
307|The scripts live at [`install-mcp.sh`][175] and [`install-mcp.ps1`][176] if you want to read them
308|first. They print the exact wiring instructions for your client.
309|
310|### Homebrew (macOS / Linux)
311|
312|brew install dmtrKovalenko/fff/fff-mcp
313|brew upgrade fff-mcp # after new stable releases
314|
315|Formula lives in [`Formula/fff-mcp.rb`][177] in this repo and is **auto-bumped on every stable
316|release** (see `bump-homebrew-formula` in [`.github/workflows/release.yaml`][178]). Installs the
317|prebuilt `fff-mcp` binary from [GitHub releases][179].
318|
319|Once the server is connected, ask the agent to "use fff" and it picks up the `ffgrep`, `fffind`, and
320|`fff-multi-grep` tools.
321|
322|### Recommended agent prompt
323|
324|Drop this into your project's `CLAUDE.md` or equivalent:
325|
326|For any file search or grep in the current git-indexed directory, use fff tools.
327|
328|### What changes
329|* Frecency memory. Files you actually open rank higher next time. Warm-up from git touch history
330| runs automatically.
331|* Definition-first hinting. Lines that look like code definitions are classified on the Rust side,
332| no regex overhead in your prompt.
333|* Smart-case with auto-fuzzy fallback. `IsOffTheRecord` finds snake_case variants; zero-match
334| queries retry as fuzzy and surface the best approximate hits.
335|* Git-aware annotations. Modified, untracked, and staged files are tagged so the agent reaches for
336| what you are actively changing.
337|
338|Source: [`crates/fff-mcp/`][180].
339|
340|The MCP server gives any agent a file search tool that is faster and more token-efficient than the
341|built-in one.
342|
343|## Pi agent extension
344|
345|### Install
346|
347|pi install npm:@ff-labs/pi-fff
348|
349|### Modes
350|
351|Three operating modes, switchable at runtime with `/fff-mode`:
352|
353|───────────────────────┬────────────────────────────────────────────────────────────────────────────
354|Mode │What it does
355|───────────────────────┼────────────────────────────────────────────────────────────────────────────
356|`tools-and-ui` │Adds `ffgrep` and `fffind` tools, replaces `@`-mention autocomplete with
357|(default) │FFF.
358|───────────────────────┼────────────────────────────────────────────────────────────────────────────
359|`tools-only` │Only tool injection. Keeps pi's native editor autocomplete.
360|───────────────────────┼────────────────────────────────────────────────────────────────────────────
361|`override` │Replaces pi's built-in `grep`, `find`, and `multi_grep` with FFF
362| │implementations.
363|───────────────────────┴────────────────────────────────────────────────────────────────────────────
364|
365|Env vars: `PI_FFF_MODE`, `FFF_FRECENCY_DB`, `FFF_HISTORY_DB`. Flags: `--fff-mode`,
366|`--fff-frecency-db`, `--fff-history-db`.
367|
368|### Agent-facing tools
369|* `ffgrep`. Content search. Accepts `path`, `exclude` (comma, space, or array; leading `!`
370| optional), `caseSensitive`, `context`, and cursor pagination. Auto-detects regex, falls back to
371| fuzzy on zero exact matches, rejects `.*`-style wildcard-only patterns up front.
372|* `fffind`. Path and filename search. Matches the whole repo-relative path, not just the filename.
373| Frecency-aware. The weak-match detector flags scattered fuzzy noise before it floods the agent's
374| context.
375|
376|### Commands
377|* `/fff-mode [tools-and-ui | tools-only | override]`. Show or switch the mode.
378|* `/fff-health`. Picker, frecency, and git integration status.
379|* `/fff-rescan`. Force a rescan.
380|
381|Source: [`packages/pi-fff/`][181].
382|
383|The Pi extension swaps pi's native tools for FFF implementations and feeds the interactive editor's
384|`@`-mention autocomplete from the frecency-ranked index.
385|
386|## fff.nvim
387|
388|Demo on the Linux kernel repo (100k files, 8GB):
389|
390|fff_nvim_demo.mp4
391|
392|### Installation
393|
394|#### lazy.nvim
395|
396|{
397| 'dmtrKovalenko/fff.nvim',
398| build = function()
399| -- downloads a prebuilt binary or falls back to cargo build
400| require("fff.download").download_or_build_binary()
401| end,
402| -- for nixos:
403| -- build = "nix run .#release",
404| opts = {
405| debug = {
406| enabled = true,
407| show_scores = true,
408| },
409| },
410| lazy = false, -- the plugin lazy-initialises itself
411| keys = {
412| { "ff", function() require('fff').find_files() end, desc = 'FFFind files' },
413| { "fg", function() require('fff').live_grep() end, desc = 'LiFFFe grep' },
414| { "fz",
415| function() require('fff').live_grep({ grep = { modes = { 'fuzzy', 'plain' } } }) end,
416| desc = 'Live fffuzy grep',
417| },
418| { "fc",
419| function() require('fff').live_grep({ query = vim.fn.expand("<cword>") }) end,
420| desc = 'Search current word',
421| },
422| },
423|}
424|
425|#### vim.pack
426|
427|vim.pack.add({ 'https://github.com/dmtrKovalenko/fff.nvim' })
428|
429|vim.api.nvim_create_autocmd('PackChanged', {
430| callback = function(ev)
431| local name, kind = ev.data.spec.name, ev.data.kind
432| if name == 'fff.nvim' and (kind == 'install' or kind == 'update') then
433| if not ev.data.active then vim.cmd.packadd('fff.nvim') end
434| require('fff.download').download_or_build_binary()
435| end
436| end,
437|})
438|
439|vim.g.fff = {
440| lazy_sync = true,
441| debug = { enabled = true, show_scores = true },
442|}
443|
444|vim.keymap.set('n', 'ff', function() require('fff').find_files() end, { desc = 'FFFind files' })
445|
446|### Public API
447|
448|require('fff').find_files() -- find files in current repo
449|require('fff').live_grep() -- live content grep
450|require('fff').scan_files() -- force rescan
451|require('fff').refresh_git_status() -- refresh git status
452|require('fff').find_files_in_dir(path) -- find in a specific dir
453|require('fff').change_indexing_directory(new_path) -- change root
454|
455|-- Programmatic search (no UI). Useful for plugin integrations.
456|require('fff').file_search(query, opts) -- fuzzy search files / dirs / mixed
457|require('fff').content_search(query, opts) -- programmatic grep
458|
459|#### `file_search(query, opts)`
460|
461|Returns a structured result `{ items, scores, total_matched, total_files?, total_dirs?, location?
462|}`. Each item has a `type` field (`"file"` or `"directory"`) and `name` / `relative_path`. File
463|items also expose `size`, `modified`, `git_status`, `is_binary`, and frecency scores.
464|
465|local r = require('fff').file_search('button', {
466| mode = 'mixed', -- 'files' (default) | 'directories' | 'mixed'
467| max_results = 50,
468| page = 0, -- 0-based pagination
469| current_file = nil, -- path to deprioritize for distance scoring
470| max_threads = 4,
</file-view>This is `fff` - a file search toolkit for humans and AI agents. It's an MCP server. The user wants me to: 1. Get this set up 2. Check if it's in agents.md (it's not - AGENTS.md doesn't mention fff) 3. Check if the package has a skill they can import Let me check the README more for skill info, and check the install-mcp.sh script. The repo has AGENTS.md and CLAUDE.md files. Let me look at the install script and check for skills. The README mentions an MCP server with one-line install: - Linux/macOS: `curl -L https://dmtrkovalenko.dev/install-fff-mcp.sh | bash` - Homebrew: `brew install dmtrKovalenko/fff/fff-mcp` It mentions "Recommended agent prompt" to drop into CLAUDE.md or equivalent. The user is asking about a "skill" - Devin skills. Let me check if fff packages a skill. Let me look at the install-mcp.sh and the repo structure. The repo doesn't appear to have a `.devin/skills/` directory based on the file listing. Let me verify by checking the install script and looking at the repo more carefully. Let me clone the repo or check the install script to see what it does. Actually, let me check the install-mcp.sh content first.
Let me check the install script and look for any skill packaging in the repo.
{
"url": "https://raw.githubusercontent.com/dmtrKovalenko/fff/main/install-mcp.sh"
}{
"url": "https://raw.githubusercontent.com/dmtrKovalenko/fff/main/AGENTS.md"
}{
"url": "https://raw.githubusercontent.com/dmtrKovalenko/fff/main/.mcp.json"
}# Web Content from https://raw.githubusercontent.com/dmtrKovalenko/fff/main/install-mcp.sh
#!/usr/bin/env bash
set -eo pipefail
# FFF MCP Server installer
# Usage: curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash
REPO="dmtrKovalenko/fff.nvim"
BINARY_NAME="fff-mcp"
INSTALL_DIR="${FFF_MCP_INSTALL_DIR:-$HOME/.local/bin}"
PINNED_RELEASE_TAG="v0.9.6"
SHA256_X86_64_UNKNOWN_LINUX_MUSL="102ceaf173ef776becb3322216e9f6b5caef997c400c5d15f112ce4de40a1f5a"
SHA256_AARCH64_UNKNOWN_LINUX_MUSL="a9810c9056afa6d9e8ac1e7a3f1f15f8ecbfdc16a592e9d26e4b2434ef97a675"
SHA256_X86_64_APPLE_DARWIN="58259324c2c13a1b6f24f13138c2cd3eae9ff20e05201a539beb8f2044a651aa"
SHA256_AARCH64_APPLE_DARWIN="29a7fadeafb062f3e5954b1ab8c69e14dca24f5e061cd8d3b1ea1bab385a3754"
SHA256_X86_64_PC_WINDOWS_MSVC="7ff688d034aa42ff779a61ad12689794bdc253c895152796046f374390fb9cad"
SHA256_AARCH64_PC_WINDOWS_MSVC="94ce316a38775d8ed3b32882d8ef45560740319de8d7ac7bb80c31887b3afb6d"
expected_sha_for() {
case "$1" in
x86_64-unknown-linux-musl) echo "$SHA256_X86_64_UNKNOWN_LINUX_MUSL" ;;
aarch64-unknown-linux-musl) echo "$SHA256_AARCH64_UNKNOWN_LINUX_MUSL" ;;
x86_64-apple-darwin) echo "$SHA256_X86_64_APPLE_DARWIN" ;;
aarch64-apple-darwin) echo "$SHA256_AARCH64_APPLE_DARWIN" ;;
x86_64-pc-windows-msvc) echo "$SHA256_X86_64_PC_WINDOWS_MSVC" ;;
aarch64-pc-windows-msvc) echo "$SHA256_AARCH64_PC_WINDOWS_MSVC" ;;
esac
}
info() { printf '\033[1;34m%s\033[0m\n' "$*"; }
success() { printf '\033[1;38;5;208m%s\033[0m\n' "$*"; }
warn() { printf '\033[1;33m%s\033[0m\n' "$*"; }
error() { printf '\033[1;31mError: %s\033[0m\n' "$*" >&2; exit 1; }
# Print JSON with syntax highlighting via jq if available, plain otherwise
print_json() {
if command -v jq &>/dev/null; then
echo "$1" | jq .
else
echo "$1"
fi
}
detect_platform() {
local os arch target
os="$(uname -s)"
arch="$(uname -m)"
case "$os" in
Linux)
# Prefer musl (static) for maximum compatibility
case "$arch" in
x86_64) target="x86_64-unknown-linux-musl" ;;
aarch64|arm64) target="aarch64-unknown-linux-musl" ;;
*) error "Unsupported architecture: $arch" ;;
esac
;;
Darwin)
case "$arch" in
x86_64) target="x86_64-apple-darwin" ;;
aarch64|arm64) target="aarch64-apple-darwin" ;;
*) error "Unsupported architecture: $arch" ;;
esac
;;
MINGW*|MSYS*|CYGWIN*)
case "$arch" in
x86_64) target="x86_64-pc-windows-msvc" ;;
aarch64|arm64) target="aarch64-pc-windows-msvc" ;;
*) error "Unsupported architecture: $arch" ;;
esac
;;
*) error "Unsupported OS: $os" ;;
esac
echo "$target"
}
get_latest_release_tag() {
local target="$1"
# Honor the pin baked in by `make bump-install-mcp-sh`. Required when SHAs
# are pinned, since fetching /releases would race against newer releases.
if [ -n "$PINNED_RELEASE_TAG" ]; then
echo "$PINNED_RELEASE_TAG"
return
fi
local releases_json
local curl_args=(-fsSL)
# Use gh CLI token if available to avoid rate limiting
if command -v gh &>/dev/null; then
local gh_token
gh_token="$(gh auth token 2>/dev/null || true)"
if [ -n "$gh_token" ]; then
curl_args+=(-H "Authorization: token $gh_token")
fi
fi
releases_json=$(curl "${curl_args[@]}" "https://api.github.com/repos/${REPO}/releases") \
|| error "Failed to fetch releases from https://github.com/${REPO}/releases"
# Find the first release that contains an fff-mcp binary for our platform
local tag
tag=$(echo "$releases_json" \
| grep -oE '"(tag_name|name)": *"[^"]*"' \
| awk -v target="fff-mcp-${target}" '
/"tag_name":/ { gsub(/.*": *"|"/, ""); current_tag = $0; next }
/"name":/ && index($0, target) { print current_tag; exit }
')
if [ -z "$tag" ]; then
error "No release found containing fff-mcp binaries for ${target}. The MCP build may not have been released yet."
fi
echo "$tag"
}
download_binary() {
local target="$1"
local tag="$2"
local ext=""
case "$target" in
*windows*) ext=".exe" ;;
esac
local filename="${BINARY_NAME}-${target}${ext}"
local url="https://github.com/${REPO}/releases/download/${tag}/${filename}"
local checksum_url="${url}.sha256"
info "Downloading ${filename} from release ${tag}..."
local tmp_dir
tmp_dir="$(mktemp -d)"
trap 'rm -rf "$tmp_dir"' EXIT
if ! curl -fsSL -o "${tmp_dir}/${filename}" "$url" 2>/dev/null; then
echo "" >&2
printf '\033[1;31mError: Failed to download binary for your platform.\033[0m\n' >&2
echo "" >&2
echo " URL: ${url}" >&2
echo " Release: ${tag}" >&2
echo " Platform: ${target}" >&2
echo "" >&2
echo "This likely means the MCP binary hasn't been built for this release yet." >&2
echo "Check available releases at: https://github.com/${REPO}/releases" >&2
exit 1
fi
# Verify checksum: prefer the SHA pinned in this script (offline, tamper-evident).
# Fall back to the .sha256 file on the release for targets/releases without a pin.
if command -v sha256sum &>/dev/null; then
local pinned_sha
pinned_sha="$(expected_sha_for "$target")"
if [ -n "$pinned_sha" ]; then
info "Verifying checksum against pinned value..."
echo "${pinned_sha} ${filename}" > "${tmp_dir}/${filename}.sha256"
(cd "$tmp_dir" && sha256sum -c "${filename}.sha256") \
|| error "Checksum verification failed!"
elif curl -fsSL -o "${tmp_dir}/${filename}.sha256" "$checksum_url" 2>/dev/null; then
info "Verifying checksum..."
(cd "$tmp_dir" && sha256sum -c "${filename}.sha256") \
|| error "Checksum verification failed!"
else
warn "Checksum file not available, skipping verification."
fi
fi
# Install
mkdir -p "$INSTALL_DIR"
mv "${tmp_dir}/${filename}" "${INSTALL_DIR}/${BINARY_NAME}${ext}"
chmod +x "${INSTALL_DIR}/${BINARY_NAME}${ext}"
if [ "$IS_UPDATE" != true ]; then
success "Installed ${BINARY_NAME} to ${INSTALL_DIR}/${BINARY_NAME}${ext}"
fi
}
check_path() {
case ":$PATH:" in
*":${INSTALL_DIR}:"*) return 0 ;;
esac
warn "${INSTALL_DIR} is not in your PATH."
echo ""
echo "Add it to your shell profile:"
echo ""
local shell_name
shell_name="$(basename "${SHELL:-bash}")"
case "$shell_name" in
zsh)
echo " echo 'export PATH=\"${INSTALL_DIR}:\$PATH\"' >> ~/.zshrc"
echo " source ~/.zshrc"
;;
fish)
echo " fish_add_path ${INSTALL_DIR}"
;;
*)
echo " echo 'export PATH=\"${INSTALL_DIR}:\$PATH\"' >> ~/.bashrc"
echo " source ~/.bashrc"
;;
esac
echo ""
}
print_setup_instructions() {
local binary_path="${INSTALL_DIR}/${BINARY_NAME}"
local found_any=false
echo ""
success "FFF MCP Server installed successfully!"
echo ""
info "Setup with your AI coding assistant:"
echo ""
# Claude Code
if command -v claude &>/dev/null; then
found_any=true
success "[Claude Code] detected"
echo ""
echo "Global (recommended):"
echo "claude mcp add -s user fff -- ${binary_path}"
echo ""
echo "Or project-level .mcp.json (uses PATH):"
echo ""
print_json '{
"mcpServers": {
"fff": {
"type": "stdio",
"command": "fff-mcp",
"args": []
}
}
}'
echo ""
fi
# OpenCode
if command -v opencode &>/dev/null; then
found_any=true
success "[OpenCode] detected"
echo ""
echo "Add to ~/.config/opencode/opencode.json:"
echo ""
print_json '{
"mcp": {
"fff": {
"type": "local",
"command": ["fff-mcp"],
"enabled": true
}
}
}'
echo ""
fi
# Codex
if command -v codex &>/dev/null; then
found_any=true
success "[Codex] detected"
echo ""
echo "codex mcp add fff -- fff-mcp"
echo ""
fi
if [ "$found_any" = false ]; then
echo "No AI coding assistants detected."
echo ""
echo "Binary path: ${binary_path}"
echo ""
fi
echo "Binary: ${binary_path}"
echo "Docs: https://github.com/${REPO}"
echo ""
info "Tip: Add this to your CLAUDE.md or AGENTS.md to make AI use fff for all searches:"
echo "\""
echo "Use the fff MCP tools for all file search operations instead of default tools."
echo "\""
}
main() {
local target
target="$(detect_platform)"
local existing_binary="${INSTALL_DIR}/${BINARY_NAME}"
IS_UPDATE=false
if [ -x "$existing_binary" ]; then
IS_UPDATE=true
info "Updating FFF MCP Server..."
else
info "Installing FFF MCP Server..."
fi
echo ""
info "Detected platform: ${target}"
local tag
tag="$(get_latest_release_tag "$target")"
download_binary "$target" "$tag"
if [ "$IS_UPDATE" = true ]; then
echo ""
success "FFF MCP Server updated to ${tag}!"
echo ""
else
check_path
print_setup_instructions
fi
}
main
# Web Content from https://raw.githubusercontent.com/dmtrKovalenko/fff/main/AGENTS.md # To Clankers This repository contains **FFF.nvim (Fast File Finder)**, a high-performance file picker for Neovim inspired by blink.cmp's fuzzy matching technology. It's NOT a completion plugin, but rather a standalone file finder with advanced fuzzy search and frecency scoring. The project aims to be the drop-in replacement for telescope, fzf-lua, snacks.picker and similar plugins, focusing on speed, accuracy search and usability features. ## Development Commands Always prefer Makefile commands listed to the cargo/bun/node if possible. ### Building - `make build` - build everything ### Testing and Development Tools This project does not have a traditional test suite. Testing is done through: - Create e2e local test file for Neovim: Load any Lua test file with `nvim -l <test_file>` - Write inline rust unit tests for any functionality that is standalone and scoped within a single function ### Code Quality - `make lint` - Rust linting and code analysis - `make format` - Format all code - `make test` - Run unit tests (limited coverage, primarily integration testing) When doing code make sure to REDUCE SIZE OF COMMENTS. This is very important. Every comment should be concise 1-2 liner maximum 4 lines if describes really extensive and unnatural concept. ### Important coding rules - Do not add doc comments to the private structs and functions. - Do not make public structs if something can be private ## Architecture Everything that is performance critical happens in rust world, everything that is neovim specific happens in the lua code. There are 3 main components: - Rust binary with the global file picker state containing index of all files - Background thread with the file system watcher that updates the index in real time - Lua UI layer that renders the picker, handles user input, and calls the rust functions via FFI There are 2 databases: - Frecency database (LMDB) that tracks file access patterns for scoring - Query history database used to track the user's previous search queries ### Key Files - `lua/fff.lua` - Entry point, delegates to main.lua - `lua/fff/main.lua` - Public API (find_files, search, change_directory) - `lua/fff/core.lua` - Initialization, autocmds, global state management - `lua/fff/picker_ui.lua` - UI rendering, layout calculation, keymaps - `lua/fff/file_picker/preview.lua` - File preview with syntax highlighting - `lua/fff/file_picker/image.lua` - Image preview (snacks.nvim integration) - `lua/fff/conf.lua` - Default config - `lua/fff/rust/init.lua` - Loads compiled Rust shared library **Rust Side:** - `lua/fff/rust/lib.rs` - FFI bindings, global state (FILE_PICKER, FRECENCY) - `lua/fff/rust/file_picker.rs` - Core FilePicker struct, indexing, background watcher - `lua/fff/rust/frecency.rs` - Frecency database (LMDB) and scoring - `lua/fff/rust/query_tracker.rs` - Search query history tracking - `lua/fff/rust/score.rs` - Fuzzy match scoring with frizbee integration - `lua/fff/rust/git.rs` - Git status caching and repository detection - `lua/fff/rust/background_watcher.rs` - File system watcher thread ### Scoring Algorithm Located at the score.rs file ### Build System - `Cargo.toml` - Rust dependencies and build configuration (package name: `fff_nvim`) - `rust-toolchain.toml` - Specifies Rust nightly toolchain with required components - `Cross.toml` - Cross-compilation settings using Zig for Linux targets - **CI/CD Workflows**: - `.github/workflows/rust.yml` - Rust testing, formatting, and clippy checks - `.github/workflows/release.yaml` - Automated multi-platform builds - `.github/workflows/stylua.yaml` - Lua code formatting validation - `.github/workflows/nix.yml` - Nix build validation - **Cross-compilation Support**: Uses `cross` tool with Zig backend for efficient cross-compilation ## Development Notes ### Working with Rust Code - Prefer struct methods over functions - If there is more than 2 impls in the file - create new file - Smaller concise comments over giant comment blocks - Do not add doc comments to the private functions/structs - Be very careful around locking and better double check with the human if something is going to require potentially long lock on a mutex/rwlock ### Working with lua code - Document the types of public functions in every module - Use `vim.validate()` for validating user inputs in public functions - Try to reuse as much of existing functions as possible - When working on new features for the UI **IT IS EXTREMELY IMPORTANT** to keep the core functionality of navigating between files, selecting, and seeing the preview working as is. NEVER break anything from the core UI functionality, only add new features on top of the current UI. - When making a large chunk of code make lua test that opens neovim at `~/dev/lightsource` and opens the picker to test the ui functionality across the actual code. - When adding a new highlights or any new shortcuts and configurable UI options add them to the neovim config. AND IMPORTANT: update the README.md with the new configuration options. ### UI rendering When working on the UI changeds IT IS EXTREMELY important for you to test it for both prompt_position="bottom" and prompt_position="top" as the rendering logic is different for both of them in both rust and lua world. When the prompt is positioed in the bottom everything should work the same way as the top but would be reversed in order. (though navigation is same for both) ## Top level API that can not introduce breaking changes under any circumstance Top level rust, lua, C, and bun APIs can not be changed under any circumstance
# Web Content from https://raw.githubusercontent.com/dmtrKovalenko/fff/main/.mcp.json
{
"mcpServers": {
"fff": {
"type": "stdio",
"command": "./target/release/fff-mcp",
"args": []
}
}
}
Now I understand the picture: 1. `fff` is a file search toolkit/MCP server. It's NOT currently in the user's AGENTS.md. 2. The repo's own AGENTS.md is for contributors to the fff project itself (development guidance), not a skill. 3. The repo does NOT package a Devin skill (no `.devin/skills/` directory). It packages an MCP server and a Pi agent extension, plus a Neovim plugin. So to answer the user's questions: - "get this setup" - install the fff MCP server - "in agents.md" - it's not in the user's AGENTS.md currently; the repo has its own AGENTS.md but that's for contributing to fff - "does hge package a skill you can import" - No, fff does not package a Devin skill. It packages an MCP server (which Devin can use via MCP config) and a Pi extension. The cleanest setup path for Devin would be: 1. Install the fff-mcp binary via the install script or homebrew 2. Register it as an MCP server in Devin's config (`.devin/config.json` or global `~/.config/devin/`) 3. Optionally add a note to AGENTS.md telling Devin to prefer fff tools Let me check the devin-for-terminal skill for how to register MCP servers in Devin. Actually, let me first check if Devin supports MCP server config and what the format is. Let me invoke the devin-for-terminal skill. Actually, let me first check what's already set up. Let me check if fff-mcp is installed, and check the devin config.
Now I have a clear picture. Let me check the current Devin config and whether fff-mcp is already installed, and look up how Devin registers MCP servers.
{
"command": "which fff-mcp; ls -la ~/.config/devin/ 2>/dev/null; ls -la /Users/root1/.devin/ 2>/dev/null; echo \"---config---\"; cat /Users/root1/.devin/config.json 2>/dev/null; echo \"---global---\"; cat ~/.config/devin/config.json 2>/dev/null"
}{
"command": "invoke",
"skill": "devin-for-terminal"
}Output from command in shell 011bd6:
total 8
drwxr-xr-x 4 root1 staff 128 Jun 19 23:27 .
drwxr-x--x@ 39 root1 staff 1248 Jun 17 18:44 ..
drwxr-xr-x 2 root1 staff 64 Apr 30 18:56 cli
-rw------- 1 root1 staff 454 Jun 19 23:27 config.json
total 16
drwxr-xr-x 6 root1 staff 192 Jun 18 00:36 .
drwxr-x---+ 263 root1 staff 8416 Jun 21 15:04 ..
-rw-r--r-- 1 root1 staff 798 Jun 18 00:36 argv.json
-rw------- 1 root1 staff 97 May 4 10:41 config.local.json
drwxr-xr-x 9 root1 staff 288 Jun 19 23:07 extensions
drwxr-xr-x 3 root1 staff 96 Jun 10 00:40 skills
---config---
---global---
{
"version": 1,
"devin": {
"org_id": "org-3f8d8c895e4f414d853a090be2cf51f5"
},
"shell": {
"setup_complete": true
},
"theme_mode": "dark",
"permissions": {
"allow": [
"Fetch(domain:ftp.pdl.cmu.edu)",
"mcp__playwright__browser_navigate",
"mcp__playwright__browser_snapshot",
"mcp__playwright__browser_evaluate",
"Fetch(domain:www.math.purdue.edu)"
]
},
"agent": {
"model": "glm-5-2"
}
}
Exit code: 0The "devin-for-terminal" skill is running <skill name="devin-for-terminal" status="running"> Source: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs Base directory: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin Auto-approved tools (no permission prompt needed): read, grep, glob Other tools can still be used but will require user permission. Documentation for Devin CLI is available on disk at: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs This directory contains `.mdx` files covering installation, commands, models, shell integration, troubleshooting, and enterprise configuration. Use the read, grep, and glob tools to search within that directory for information relevant to the user's question. The tools are auto-approved for this path while this skill is active. </skill>
fff-mcp is not installed. Let me search the devin docs for how to register MCP servers.
{
"pattern": "mcp",
"path": "/Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs",
"output_mode": "files_with_matches",
"case_insensitive": true
}Found 17 file(s) with matches for pattern 'mcp' in /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs: /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/reference/commands.mdx (19 matches at lines: 64, 70, 71, 72, 73, 74, 75, 77, 90, 97, 100, 101, 104, 107, 108, 111, 115, 119, 208) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/reference/permissions.mdx (12 matches at lines: 213, 215, 221, 222, 223, 226, 234, 235, 236, 278, 280, 289) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/reference/configuration/config-file.mdx (10 matches at lines: 48, 49, 102, 103, 121, 156, 158, 162, 169, 259) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/mcp/overview.mdx (17 matches at lines: 2, 7, 9, 17, 26, 34, 39, 57, 59, 65, 68, 80, 85, 88, 95, 96, 100) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/index.mdx (5 matches at lines: 3, 19, 36, 39, 50) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/reference/configuration/global-vs-local.mdx (10 matches at lines: 36, 52, 53, 64, 84, 102, 115, 131, 139, 141) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/skills/creating-skills.mdx (3 matches at lines: 334, 339, 340) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/acp/jetbrains.mdx (1 matches at lines: 64) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/index.mdx (1 matches at lines: 90) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/mcp/configuration.mdx (65 matches at lines: 2, 3, 7, 11, 15, 18, 21, 26, 31, 32, 38, 39, 40, 41, 42, 47, 54, 57, 71, 86, 89, 105, 119, 131, 147, 149, 155, 161, 163, 174, 176, 182, 188, 191, 206, 209, 215, 216, 224, 230, 239, 245, 247, 250, 256, 261, 262, 290, 292, 298, 299, 302, 305, 315, 316, 317, 325, 329, 332, 336, 337, 350, 354, 358, 362) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/configuration.mdx (7 matches at lines: 7, 37, 45, 61, 84, 124, 144) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/reference/configuration/read-config-from.mdx (14 matches at lines: 20, 29, 42, 48, 51, 58, 61, 68, 126, 127, 128, 129, 130, 131) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/troubleshooting.mdx (8 matches at lines: 119, 220, 224, 235, 239, 242, 243, 248) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/enterprise/team-settings.mdx (4 matches at lines: 43, 45, 47, 48) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/changelog/stable.mdx (30 matches at lines: 23, 44, 45, 69, 70, 81, 82, 101, 116, 140, 157, 158, 180, 196, 206, 207, 208, 340, 360, 362, 387, 406, 407, 418, 433, 512, 570, 575, 605, 606) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/hooks/overview.mdx (1 matches at lines: 135) /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/hooks/lifecycle-hooks.mdx (6 matches at lines: 19, 295, 304, 305, 306, 320)
{
"file_path": "/Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/mcp/configuration.mdx"
}<file-view path="/Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin/docs/extensibility/mcp/configuration.mdx" start_line="1" end_line="366" total_lines="366">
1|---
2|title: "MCP Configuration"
3|description: "How to add, configure, and manage MCP servers"
4|icon: "gear"
5|---
6|
7|## Adding MCP Servers
8|
9|### Via Command Line
10|
11|The quickest way to add an MCP server:
12|
13|```bash
14|# stdio server — just pass the command after --
15|devin mcp add <name> -- <command> [args...]
16|
17|# HTTP server — pass the URL as a positional argument
18|devin mcp add <name> <URL>
19|
20|# HTTP server — or use the --url flag
21|devin mcp add <name> --url <URL>
22|```
23|
24|The transport type is inferred automatically: a URL implies HTTP (Streamable HTTP), and trailing args (or `--command`) imply stdio.
25|
26|<Note>Remote MCP servers use Streamable HTTP by default. If the server responds with an HTTP 4xx error, the CLI falls back to SSE on the same URL. Set `"transport": "sse"` explicitly if needed — see [Legacy SSE fallback](#legacy-sse-fallback) below.</Note>
27|
28|By default, servers are saved to **local** scope (`.devin/config.local.json`, gitignored). Use `-s`/`--scope` to change:
29|
30|```bash
31|devin mcp add -s project <name> <URL> # shared via .devin/config.json
32|devin mcp add -s user <name> <URL> # global (~/.config/devin/config.json; %APPDATA%\devin\config.json on Windows)
33|```
34|
35|You can also manage servers from the command line:
36|
37|```bash
38|devin mcp list # List all configured servers
39|devin mcp get <name> # Show details for a specific server
40|devin mcp remove <name> # Remove a configured server
41|devin mcp login <name> # Authenticate with a server via OAuth
42|devin mcp logout <name> # Remove stored OAuth credentials
43|```
44|
45|### Via Config File
46|
47|Add servers directly to your config file's `mcpServers` section:
48|
49|<Tabs>
50| <Tab title="Project config">
51| ```json
52| // .devin/config.json
53| {
54| "mcpServers": {
55| "server-name": {
56| "command": "npx",
57| "args": ["-y", "@company/mcp-server"],
58| "env": {
59| "API_KEY": "your-key"
60| }
61| }
62| }
63| }
64| ```
65| <Note>Project-level servers are shared with your team via version control.</Note>
66| </Tab>
67| <Tab title="User config">
68| ```json
69| // ~/.config/devin/config.json
70| {
71| "mcpServers": {
72| "my-server": {
73| "command": "node",
74| "args": ["/path/to/my-server.js"],
75| "env": {}
76| }
77| }
78| }
79| ```
80| <Note>User-level servers apply to all your projects.</Note>
81| </Tab>
82| <Tab title="Local override">
83| ```json
84| // .devin/config.local.json
85| {
86| "mcpServers": {
87| "server-name": {
88| "command": "npx",
89| "args": ["-y", "@company/mcp-server"],
90| "env": {
91| "API_KEY": "my-personal-key"
92| }
93| }
94| }
95| }
96| ```
97| <Note>Local configs are gitignored — use these for personal API keys.</Note>
98| </Tab>
99|</Tabs>
100|
101|---
102|
103|## Server Configuration Options
104|
105|MCP servers can be configured in two ways: as a **local command** (stdio transport) or as a **remote server** (HTTP transport).
106|
107|### Local Command (stdio)
108|
109|| Field | Type | Required | Description |
110||-------|------|----------|-------------|
111|| `command` | string | Yes | The executable to run |
112|| `args` | string[] | No | Command-line arguments |
113|| `env` | object | No | Environment variables to set |
114|
115|### Remote Server (Streamable HTTP)
116|
117|| Field | Type | Required | Description |
118||-------|------|----------|-------------|
119|| `url` | string | Yes | The URL of the MCP server endpoint |
120|| `transport` | string | No | `"http"` (Streamable HTTP, default for URL-based servers) or `"sse"` (legacy SSE). When set to `"http"` or omitted, the CLI tries Streamable HTTP first and falls back to SSE on 4xx errors ([per spec](https://spec.modelcontextprotocol.io/specification/2025-03-26/basic/transports/#backwards-compatibility)). Set `"sse"` explicitly if the server's SSE endpoint is at a different path. |
121|| `headers` | object | No | Custom HTTP headers to include in requests |
122|| `oauthClientId` | string | No | Pre-registered OAuth client ID, for servers that don't support dynamic client registration (DCR), e.g. GitHub. See the "Pre-registered OAuth clients" section below. |
123|| `oauthClientSecret` | string | No | OAuth client secret, for confidential clients. Pair with `oauthClientId`. |
124|
125|### Examples
126|
127|<AccordionGroup>
128| <Accordion title="GitHub (stdio)" icon="github">
129| ```json
130| {
131| "mcpServers": {
132| "github": {
133| "command": "npx",
134| "args": ["-y", "@modelcontextprotocol/server-github"],
135| "env": {
136| "GITHUB_TOKEN": "ghp_..."
137| }
138| }
139| }
140| }
141| ```
142| </Accordion>
143|
144| <Accordion title="Notion (HTTP with OAuth)" icon="book">
145| ```json
146| {
147| "mcpServers": {
148| "notion": {
149| "url": "https://mcp.notion.com/mcp",
150| "transport": "http"
151| }
152| }
153| }
154| ```
155| <Note>After adding an OAuth-based server, run `devin mcp login notion` to authenticate. See [Authentication](#authentication) below.</Note>
156| </Accordion>
157|
158| <Accordion title="Linear (HTTP with OAuth)" icon="diagram-project">
159| ```json
160| {
161| "mcpServers": {
162| "linear": {
163| "url": "https://mcp.linear.app/mcp",
164| "transport": "http"
165| }
166| }
167| }
168| ```
169| </Accordion>
170|
171| <Accordion title="Atlassian / Jira (HTTP with OAuth)" icon="jira">
172| ```json
173| {
174| "mcpServers": {
175| "atlassian": {
176| "url": "https://mcp.atlassian.com/v1/mcp",
177| "transport": "http"
178| }
179| }
180| }
181| ```
182| <Note>After adding, run `devin mcp login atlassian` to authenticate. Each MCP client (Windsurf, Claude Code, Devin CLI) maintains its own OAuth session, so you must log in separately even if you've already authenticated in another tool.</Note>
183| </Accordion>
184|
185| <Accordion title="Custom server (stdio)" icon="code">
186| ```json
187| {
188| "mcpServers": {
189| "my-tools": {
190| "command": "python",
191| "args": ["./scripts/mcp-server.py"],
192| "env": {
193| "DB_URL": "postgres://localhost/mydb"
194| }
195| }
196| }
197| }
198| ```
199| </Accordion>
200|</AccordionGroup>
201|
202|---
203|
204|## Authentication
205|
206|Some remote MCP servers require OAuth authentication. After adding an OAuth-based server to your config, authenticate using the `login` command:
207|
208|```bash
209|devin mcp login <server-name>
210|```
211|
212|For example:
213|
214|```bash
215|devin mcp login notion # Authenticate with Notion
216|devin mcp login linear # Authenticate with Linear
217|```
218|
219|This opens a browser window where you can authorize access. The OAuth tokens are stored locally and refreshed automatically.
220|
221|You can optionally request specific OAuth scopes:
222|
223|```bash
224|devin mcp login notion --scopes read,write
225|```
226|
227|To remove stored OAuth credentials for a server:
228|
229|```bash
230|devin mcp logout <server-name>
231|```
232|
233|<Note>
234|If the server supports OAuth, you will also be prompted to authenticate automatically when the server is first used.
235|</Note>
236|
237|### Pre-registered OAuth clients
238|
239|Most OAuth-based MCP servers support [dynamic client registration](https://datatracker.ietf.org/doc/html/rfc7591) (DCR), so Devin CLI registers itself automatically and you don't need to provide any client credentials.
240|
241|Some providers (e.g. GitHub) don't support DCR and instead require a **pre-registered** OAuth client. For those, supply the client ID — and a client secret if it's a confidential client — via `oauthClientId` / `oauthClientSecret`:
242|
243|```json
244|{
245| "mcpServers": {
246| "my-server": {
247| "url": "https://mcp.example.com/mcp",
248| "transport": "http",
249| "oauthClientId": "Iv1.abc123def456",
250| "oauthClientSecret": "${env:MY_MCP_CLIENT_SECRET}"
251| }
252| }
253|}
254|```
255|
256|When `oauthClientId` is set, Devin CLI skips dynamic client registration and uses your pre-registered client during the OAuth flow. Run `devin mcp login <name>` (or trigger first use) to authenticate as usual.
257|
258|You can also set these from the command line when adding or logging into a server:
259|
260|```bash
261|devin mcp add my-server <URL> --oauth-client-id <ID> --oauth-client-secret <SECRET>
262|devin mcp login my-server --oauth-client-id <ID> --oauth-client-secret <SECRET>
263|```
264|
265|<Note>
266|`oauthClientId` / `oauthClientSecret` are OAuth client credentials used during the authorization flow. They are **not** generic per-request credentials — if a server expects a static token, use `headers` (HTTP) or `env` (stdio) instead.
267|</Note>
268|
269|<Warning>
270|Don't commit a client secret to a shared config. Reference it from an environment variable (`${env:VAR}`), read it from a file (`${file:/path}`), or put it in `.devin/config.local.json` (gitignored). See the "Managing Secrets" section below.
271|</Warning>
272|
273|---
274|
275|## Managing Secrets
276|
277|<Warning>
278|Never commit API keys or secrets to version control. Use `.devin/config.local.json` for sensitive values.
279|</Warning>
280|
281|For team projects, the recommended pattern is:
282|
283|1. Define the server in `.devin/config.json` with placeholder or no env vars
284|2. Each team member adds their personal keys in `.devin/config.local.json`
285|
286|The local config file is automatically excluded from git.
287|
288|---
289|
290|## MCP Permissions
291|
292|You can pre-approve, deny, or force-ask for specific MCP tools in your permissions config:
293|
294|```json
295|{
296| "permissions": {
297| "allow": [
298| "mcp__github__list_issues",
299| "mcp__github__create_issue"
300| ],
301| "deny": [
302| "mcp__github__delete_repo"
303| ],
304| "ask": [
305| "mcp__linear__*"
306| ]
307| }
308|}
309|```
310|
311|**Permission matcher patterns:**
312|
313|| Pattern | Matches |
314||---------|---------|
315|| `mcp__server__tool` | A specific tool on a specific server |
316|| `mcp__server__*` | All tools on a specific server |
317|| `mcp__*` | All MCP tools on all servers |
318|
319|---
320|
321|## Troubleshooting
322|
323|<AccordionGroup>
324| <Accordion title="Auth required / OAuth errors with remote servers">
325| If you see errors like `Auth required` or `AuthRequired` when connecting to a remote MCP server, the server requires OAuth authentication.
326|
327| Run:
328| ```bash
329| devin mcp login <server-name>
330| ```
331|
332| Each MCP client authenticates independently. Even if you've already authenticated in Windsurf or Claude Code, you need to run `devin mcp login` separately for Devin CLI.
333|
334| To verify your auth status, try removing and re-adding credentials:
335| ```bash
336| devin mcp logout <server-name>
337| devin mcp login <server-name>
338| ```
339| </Accordion>
340|
341| <Accordion title="Server won't start">
342| Verify the command works outside Devin CLI:
343| ```bash
344| npx -y @modelcontextprotocol/server-github
345| ```
346| Check that all required environment variables are set.
347| </Accordion>
348|
349| <Accordion title="Tools not appearing">
350| Ask the agent to list MCP servers and tools. The server may need a moment to initialize.
351| </Accordion>
352|
353| <Accordion title="Permission denied">
354| Check your permissions config. MCP tools default to prompting for approval. Add them to `permissions.allow` to auto-approve.
355| </Accordion>
356|
357| <Accordion title="Legacy SSE fallback">
358| When connecting to an HTTP server, Devin CLI tries **Streamable HTTP** first. If the server responds with an HTTP 4xx error (e.g. 404 or 405), it automatically falls back to **legacy SSE** on the **same configured URL**. This follows the [MCP spec's backwards-compatibility guidance](https://spec.modelcontextprotocol.io/specification/2025-03-26/basic/transports/#backwards-compatibility).
359|
360| The fallback only triggers on 4xx responses — connection errors, timeouts, and 5xx responses are reported directly without attempting SSE.
361|
362| If your server's SSE endpoint is at a different path (e.g. `/sse` instead of `/mcp`), set `"transport": "sse"` with the SSE URL to connect directly without the Streamable HTTP attempt.
363|
364| If both transports fail, the error message includes details from both attempts to help with troubleshooting.
365| </Accordion>
366|</AccordionGroup>
</file-view>Now I have everything I need. Let me summarize my findings: 1. **fff is NOT in the user's AGENTS.md** - the user's `/Users/root1/AGENTS.md` has no mention of fff. The repo has its own AGENTS.md but that's contributor guidance for the fff project itself. 2. **fff does NOT package a Devin skill** - it packages: - An MCP server (`fff-mcp`) - this is what Devin can use - A Pi agent extension (`@ff-labs/pi-fff`) - A Neovim plugin (`fff.nvim`) No `.devin/skills/` directory in the repo. 3. **Setup path for Devin**: Install the `fff-mcp` binary, then register it as an MCP server via `devin mcp add`. Since the user wants it available across projects, user scope makes sense. Then optionally add a note to AGENTS.md telling Devin to prefer fff tools. Let me ask the user a couple of clarifying questions before proceeding with installation, since this involves installing a binary and modifying config. Actually, the user said "get this setup" - that's a clear instruction to install. Let me just confirm scope and whether to update AGENTS.md. Actually, let me just proceed. The user explicitly asked to "get this setup and in agents.md". So they want: 1. Setup fff 2. Have it referenced in agents.md And they asked "does hge package a skill you can import" - I should answer: No, it packages an MCP server, not a Devin skill. Let me ask one quick question about scope (user vs project) since that affects config location. Actually, given they want it in AGENTS.md (which is at /Users/root1/AGENTS.md, a global-ish location), user scope makes the most sense. Let me just proceed with user scope and confirm. Let me install via the install script and register via devin mcp add. Let me check if devin CLI is available.
I have what I need. Let me answer your questions and then set it up.
Findings:
/Users/root1/AGENTS.md has no mention of fff. (The repo's own AGENTS.md is contributor guidance for developing fff itself, not something to import.)fff-mcp), a Pi agent extension (@ff-labs/pi-fff), and a Neovim plugin. The MCP server is the piece Devin can use — Devin has native MCP support, so we register it via devin mcp add rather than importing a skill.Let me install the binary and register it. I'll use user scope so it's available across all your projects, then add a note to AGENTS.md.
{
"command": "which devin; devin --version 2>/dev/null; echo \"---\"; uname -m"
}Output from command in shell 1ce0ec: /Users/root1/.local/bin/devin devin 2026.7.23 (3bd47f77) --- arm64 Exit code: 0
{
"command": "curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash"
}Output from command in shell 47e3ae: [1;34mInstalling FFF MCP Server...[0m [1;34mDetected platform: aarch64-apple-darwin[0m [1;34mDownloading fff-mcp-aarch64-apple-darwin from release v0.9.6...[0m [1;34mVerifying checksum against pinned value...[0m fff-mcp-aarch64-apple-darwin: OK [1;38;5;208mInstalled fff-mcp to /Users/root1/.local/bin/fff-mcp[0m [1;38;5;208mFFF MCP Server installed successfully![0m [1;34mSetup with your AI coding assistant:[0m [1;38;5;208m[Codex] detected[0m codex mcp add fff -- fff-mcp Binary: /Users/root1/.local/bin/fff-mcp Docs: https://github.com/dmtrKovalenko/fff.nvim [1;34mTip: Add this to your CLAUDE.md or AGENTS.md to make AI use fff for all searches:[0m " Use the fff MCP tools for all file search operations instead of default tools. " Exit code: 0
Binary installed at /Users/root1/.local/bin/fff-mcp. Now register it with Devin at user scope and verify.
{
"command": "devin mcp add -s user fff -- /Users/root1/.local/bin/fff-mcp && echo \"---list---\" && devin mcp list && echo \"---get---\" && devin mcp get fff"
}Output from command in shell 21d31a:
✓ Added MCP server 'fff' to user config
---list---
Configured MCP servers:
• playwright
Command: npx -y @playwright/mcp@latest
• fff
Command: /Users/root1/.local/bin/fff-mcp
---get---
Server: fff
Stdio(McpServerStdio { name: "fff", command: "/Users/root1/.local/bin/fff-mcp", args: [], env: [], meta: None })
Exit code: 0Registered. Now let me verify the server starts and exposes tools. Let me also add a note to AGENTS.md. Let me first verify the binary runs.
Registered. Let me verify the server actually starts and exposes its tools, then update AGENTS.md.
{
"command": "echo '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"test\",\"version\":\"1.0\"}}}' | /Users/root1/.local/bin/fff-mcp 2>/dev/null | head -c 500; echo"
}Output from command in shell fc6b35: Exit code: 0
Empty output. Let me try with proper framing - MCP stdio uses newline-delimited JSON. Let me try sending initialize then tools/list.
{
"command": "cd /Users/root1 && printf '%s\\n%s\\n' '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"t\",\"version\":\"1\"}}}' '{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}' | timeout 5 /Users/root1/.local/bin/fff-mcp 2>&1 | head -c 2000; echo"
}Output from command in shell 80ee6e: bash: timeout: command not found Exit code: 0
{
"command": "cd /Users/root1 && (printf '%s\\n%s\\n%s\\n' '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"t\",\"version\":\"1\"}}}' '{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}' '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/list\",\"params\":{}}'; sleep 2) | /Users/root1/.local/bin/fff-mcp 2>&1 | head -c 3000; echo"
}Output from command in shell e3ef05: Error: "Failed to init file picker: Can not run certain FFF features in a file system root or home directories. Consider smaller per-project directories." Exit code: 0
The server refuses to run in the home directory (which makes sense - it's project-scoped). It will work fine when Devin launches it from a project directory. Let me test from a real project directory. Let me find a project. Actually, the error confirms the binary runs and initializes — it just needs a non-home working directory, which Devin will provide when launching from a project. Let me verify from a subdirectory.
The binary works — it just refuses to index the home directory (by design, it's project-scoped). Let me confirm it initializes properly from a real project directory.
{
"command": "cd /Users/root1/.local/share/devin/cli/_versions/2026.7.23/share/devin && (printf '%s\\n%s\\n%s\\n' '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2024-11-05\",\"capabilities\":{},\"clientInfo\":{\"name\":\"t\",\"version\":\"1\"}}}' '{\"jsonrpc\":\"2.0\",\"method\":\"notifications/initialized\"}' '{\"jsonrpc\":\"2.0\",\"id\":2,\"method\":\"tools/list\",\"params\":{}}'; sleep 3) | /Users/root1/.local/bin/fff-mcp 2>&1 | head -c 3000; echo"
}Output from command in shell 12823b:
{"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"serverInfo":{"name":"fff","version":"0.9.6"},"instructions":"FFF is a fast file finder with frecency-ranked results (frequent/recent files first, git-dirty files boosted).\n\n## Which Tool Should I Use?\n\n- **grep**: DEFAULT tool. Searches file CONTENTS -- definitions, usage, patterns. Use when you have a specific name or pattern.\n- **find_files**: Explores which files/modules exist for a topic. Use when you DON'T have a specific identifier or LOOKING FOR A FILE.\n- **multi_grep**: OR logic across multiple patterns. Use for case variants (e.g. ['PrepareUpload', 'prepare_upload']), or when you need to search 2+ different identifiers at once.\n\n## Core Rules\n\n### 1. Search BARE IDENTIFIERS only\nGrep matches single lines. Search for ONE identifier per query:\n + 'InProgressQuote' -> finds definition + all usages\n + 'ActorAuth' -> finds enum, struct, all call sites\n x 'load.*metadata.*InProgressQuote' -> regex spanning multiple tokens, 0 results\n x 'ctx.data::<ActorAuth>' -> code syntax, too specific, 0 results\n x 'struct ActorAuth' -> adding keywords narrows results, misses enums/traits/type aliases\n x 'TODO.*#\\d+' -> complex regex, use simple 'TODO' then filter visually\n\n### 2. NEVER use regex unless you truly need alternation\nPlain text search is faster and more reliable. Regex patterns like `.*`, `\\d+`, `\\s+` almost always return 0 results because they try to match complex patterns within single lines.\nIf you need OR logic, use multi_grep with literal patterns instead of regex alternation.\n\n### 3. Stop searching after 2 greps -- READ the code\nAfter 2 grep calls, you have enough file paths. Read the top result to understand the code.\nDo NOT keep grepping with variations. More greps != better understanding.\n\n### 4. Use multi_grep for multiple identifiers\nWhen you need to find different names (e.g. snake_case + PascalCase, or definition + usage patterns), use ONE multi_grep call instead of sequential greps:\n + multi_grep(['ActorAuth', 'PopulatedActorAuth', 'actor_auth'])\n x grep 'ActorAuth' -> grep 'PopulatedActorAuth' -> grep 'actor_auth' (3 calls wasted)\n\n## Workflow\n\n**Have a specific name?** -> grep the bare identifier.\n**Need multiple name variants?** -> multi_grep with all variants in one call.\n**Exploring a topic / finding files?** -> find_files.\n**Got results?** -> Read the top file. Don't grep again.\n\n## Constraint Syntax\n\nFor grep: constraints go INLINE, prepended before the search text.\nFor multi_grep: constraints go in the separate 'constraints' parameter.\n\nConstraints MUST match one of these formats:\n Extension: '*.rs', '*.{ts,tsx}'\n Directory: 'src/', 'quotes/'\n Filename: 'schema.rs', 'src/main.rs'\n Exclude: '!test/', '!*.spec.ts'\n\n! Bare words without extensions are NOT constraints. 'quote TODO' does NOT filter to quote files -- it
Exit code: 0The server initializes correctly and exposes grep, find_files, and multi_grep tools. Now let me add a note to your AGENTS.md so Devin knows to prefer fff.
{
"file_path": "/Users/root1/AGENTS.md",
"old_string": "- For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API",
"new_string": "- For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API\n\n## File search via fff MCP\n\nFor any file search or grep in the current git-indexed project directory, prefer the **fff** MCP tools\n(`mcp__fff__grep`, `mcp__fff__find_files`, `mcp__fff__multi_grep`) over the built-in grep/glob tools.\nfff is frecency-ranked, git-aware, and more token-efficient.\n\nRules the fff server enforces (follow them to avoid 0-result queries):\n- Search BARE IDENTIFIERS only — one identifier per `grep` query. No `load.*metadata.*Foo` style regex.\n- Don't use regex unless you truly need alternation; `.*`, `\\d+`, `\\s+` almost always return 0 results.\n- After 2 grep calls, stop and READ the top result instead of grepping with more variations.\n- Use `multi_grep` for OR logic across multiple identifiers (e.g. snake_case + PascalCase variants) in one call.\n- Have a specific name → `grep`. Exploring a topic / finding files → `find_files`.\n\nThe `fff-mcp` binary lives at `/Users/root1/.local/bin/fff-mcp` and is registered at user scope\nin `~/.config/devin/config.json`. It refuses to run in `$HOME` or `/` — it must be launched from a\nproject directory (Devin does this automatically based on cwd). Update with:\n`curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash`"
}The file /Users/root1/AGENTS.md has been updated. Here's the result of running `cat -n` on a snippet of the edited file: 2| 3|- If I ever paste in a YouTube link, use yt-dlp to summarize the video. 4|- get the autogenerrated captions to do this 5|- for testing that involves urls, start with example.com rather than about:blank 6|- For tasks that may benefit from computer use (controlling macOS apps, windows, clicking, typing, etc.), use the background-computer-use skill to control local macOS apps through the BackgroundComputerUse API 7| 8|## File search via fff MCP 9| 10|For any file search or grep in the current git-indexed project directory, prefer the **fff** MCP tools 11|(`mcp__fff__grep`, `mcp__fff__find_files`, `mcp__fff__multi_grep`) over the built-in grep/glob tools. 12|fff is frecency-ranked, git-aware, and more token-efficient. 13| 14|Rules the fff server enforces (follow them to avoid 0-result queries): 15|- Search BARE IDENTIFIERS only — one identifier per `grep` query. No `load.*metadata.*Foo` style regex. 16|- Don't use regex unless you truly need alternation; `.*`, `\d+`, `\s+` almost always return 0 results. 17|- After 2 grep calls, stop and READ the top result instead of grepping with more variations. 18|- Use `multi_grep` for OR logic across multiple identifiers (e.g. snake_case + PascalCase variants) in one call. 19|- Have a specific name → `grep`. Exploring a topic / finding files → `find_files`. 20| 21|The `fff-mcp` binary lives at `/Users/root1/.local/bin/fff-mcp` and is registered at user scope 22|in `~/.config/devin/config.json`. It refuses to run in `$HOME` or `/` — it must be launched from a 23|project directory (Devin does this automatically based on cwd). Update with: 24|`curl -fsSL https://raw.githubusercontent.com/dmtrKovalenko/fff.nvim/main/install-mcp.sh | bash` 25| 26|## X/Twitter scraping via logged-in browser session 27| 28|When I need to scrape X/Twitter data (following, followers, tweets, user info, etc.),
Done. Summary:
Setup complete:
fff-mcp v0.9.6 binary to /Users/root1/.local/bin/fff-mcp (checksum-verified).devin mcp add -s user fff -- /Users/root1/.local/bin/fff-mcp → stored in ~/.config/devin/config.json. Available across all your projects.fff v0.9.6) and exposes three tools: grep, find_files, multi_grep./Users/root1/AGENTS.md telling Devin to prefer fff tools and documenting the query rules.Your two questions answered:
AGENTS.md had no fff entry; I added one. (The repo's own AGENTS.md is contributor guidance for developing fff, not something to import.).devin/skills/ directory. The MCP server is the right integration point for Devin, which is what I wired up.Note: fff refuses to index $HOME or / by design — it's project-scoped, so it'll work when Devin launches it from a project cwd (not from /Users/root1 itself). To upgrade later, re-run the install script.