├── .gitignore
├── EXAMPLES.md
├── INSTALL.md
├── LICENSE
├── README.md
├── USAGE.md
├── WINDOWS_INSTALL.md
├── assets
├── BeforeWeStart.gif
├── Create_MyManus_Project.png
├── Create_Project.png
├── Edit_Config.png
├── MyManus.png
├── MyManus_Use.png
├── Project_Instructions.png
├── Projects.png
├── Set_Project_Instructions.png
├── Settings.png
├── appdata_claude.png
├── audio_transcription_research.tgz
├── start_run_ubuntu.png
└── ubuntu@msstore.png
├── claude_desktop_config.json
├── prompts
├── prompt.md
└── uv-cheat-sheet.md
└── windows_claude_desktop_config.json
/.gitignore:
--------------------------------------------------------------------------------
1 | *~
2 |
--------------------------------------------------------------------------------
/EXAMPLES.md:
--------------------------------------------------------------------------------
1 | EXAMPLES
2 | ========
3 |
4 | # 1. Planning a network monitoring app
5 |
6 | Plans, reasons, executes, and evaluates. Creating artifact files with all the architectural details, schemas, layout, relations, and UI wireframes.
7 | https://www.youtube.com/watch?v=JXL7rW24zfI
8 |
9 | # 2. Researching audio transcription software
10 |
11 | Researching the subject of audio transcription software.
12 | Thanks to this research, I've made [this container with WhisperX](https://hub.docker.com/r/emsi/whisperx)
13 | All the research artifacts can be [downloaded here](./assets/audio_transcription_research.tgz).
14 | https://www.youtube.com/watch?v=wv3c3RS2ONI
15 |
--------------------------------------------------------------------------------
/INSTALL.md:
--------------------------------------------------------------------------------
1 | # INSTALLATION
2 |
3 | > This guide is Linux only. For Windows, follow [WINDOWS INSTALL](./WINDOWS_INSTALL.md). Expect MacOS installation guides soon.
4 |
5 | ## Pre-requisites
6 |
7 | - A Linux machine (Ubuntu 22.04+ is recommended).
8 | - Technically an [MCP Client](https://modelcontextprotocol.io/clients) would do but this guide is specifically for [Linux Claude Desktop](https://github.com/emsi/claude-desktop).
9 | - [claude.ai](https://claude.ai/) subscription or access to LLM API (any high quality LLM should work but Claude 3.7 is recommended).
10 | - `sudo` access to install packages.
11 | - That's it, seriously
12 |
13 | ## Installation
14 |
15 | Claude Desktop is an electron app. By following this guide you will download and install the claude-desktop Windows app, repackage it to a Linux deb package and install it on your machine.
16 | Additionally a special claude_sandbox.sh script will be created to run Claude Desktop in a sandboxed environment. This makes it safer to give the AI access to the local filesystem.
17 |
18 | ### Install and Run Claude Desktop
19 | ```bash
20 | wget -O- https://raw.githubusercontent.com/emsi/claude-desktop/refs/heads/main/install-claude-desktop.sh | bash
21 |
22 | ~/sandboxes/claude_sandbox.sh
23 |
24 | claude-desktop
25 | ```
26 |
27 | This should create `~/sandboxes/claude-desktop/` folder managed by MyManus.
28 |
29 | Then EXIT the Claude desktop app and copy the MCP tools configuration:
30 | ```bash
31 | cp claude_desktop_config.json ~/sandboxes/claude-desktop/.config/Claude/
32 | ```
33 |
34 | ### Create MyManus Project in the Claude Application:
35 |
36 | 
37 |
38 | 
39 |
40 | 
41 |
42 | 
43 |
44 | ## Paste the prompt from [here](./prompts/prompt.md)
45 | Into here:
46 |
47 | 
48 |
49 | If you stumble upon any issues read the next section.
50 |
51 | ## Step by step, manual instructions
52 |
53 | 1. Read and follow the instruction at https://github.com/emsi/claude-desktop
54 | 2. Read the instruction for MCP on Linux https://github.com/emsi/claude-desktop/blob/main/MCP_LINUX.md
55 | 3. Pay special attention to https://github.com/emsi/claude-desktop/blob/main/MCP_LINUX.md#missing-display-variable
56 | 4. Create and enter the sandbox: `./claude_sandbox.sh`
57 | 5. Copy the MCP servers configuration:
58 | `cp claude_desktop_config.json ~/sandboxes/claude-desktop/.config/Claude/`
59 |
60 | 6. Enter the sandbox: `./claude_sandbox.sh`
61 | 7. While in sandbox run the Claude Desktop: `claude-desktop`
62 |
63 | You can run `claude-desktop` without the sandbox, but then MCP servers will have access to your local filesystem.
64 |
65 | # USAGE
66 |
67 | When starting a new conversation make sure to select the MyManus project:
68 |
69 | 
70 |
71 |
72 | # Automatic Tools Acceptance
73 |
74 | If you want to automatically accept the tool usage read [this guide](https://github.com/emsi/claude-desktop/blob/main/MCP_LINUX.md#auto-accepting-tools)
75 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | GNU AFFERO GENERAL PUBLIC LICENSE
2 | Version 3, 19 November 2007
3 |
4 | Copyright (C) 2007 Free Software Foundation, Inc.
5 | Everyone is permitted to copy and distribute verbatim copies
6 | of this license document, but changing it is not allowed.
7 |
8 | Preamble
9 |
10 | The GNU Affero General Public License is a free, copyleft license for
11 | software and other kinds of works, specifically designed to ensure
12 | cooperation with the community in the case of network server software.
13 |
14 | The licenses for most software and other practical works are designed
15 | to take away your freedom to share and change the works. By contrast,
16 | our General Public Licenses are intended to guarantee your freedom to
17 | share and change all versions of a program--to make sure it remains free
18 | software for all its users.
19 |
20 | When we speak of free software, we are referring to freedom, not
21 | price. Our General Public Licenses are designed to make sure that you
22 | have the freedom to distribute copies of free software (and charge for
23 | them if you wish), that you receive source code or can get it if you
24 | want it, that you can change the software or use pieces of it in new
25 | free programs, and that you know you can do these things.
26 |
27 | Developers that use our General Public Licenses protect your rights
28 | with two steps: (1) assert copyright on the software, and (2) offer
29 | you this License which gives you legal permission to copy, distribute
30 | and/or modify the software.
31 |
32 | A secondary benefit of defending all users' freedom is that
33 | improvements made in alternate versions of the program, if they
34 | receive widespread use, become available for other developers to
35 | incorporate. Many developers of free software are heartened and
36 | encouraged by the resulting cooperation. However, in the case of
37 | software used on network servers, this result may fail to come about.
38 | The GNU General Public License permits making a modified version and
39 | letting the public access it on a server without ever releasing its
40 | source code to the public.
41 |
42 | The GNU Affero General Public License is designed specifically to
43 | ensure that, in such cases, the modified source code becomes available
44 | to the community. It requires the operator of a network server to
45 | provide the source code of the modified version running there to the
46 | users of that server. Therefore, public use of a modified version, on
47 | a publicly accessible server, gives the public access to the source
48 | code of the modified version.
49 |
50 | An older license, called the Affero General Public License and
51 | published by Affero, was designed to accomplish similar goals. This is
52 | a different license, not a version of the Affero GPL, but Affero has
53 | released a new version of the Affero GPL which permits relicensing under
54 | this license.
55 |
56 | The precise terms and conditions for copying, distribution and
57 | modification follow.
58 |
59 | TERMS AND CONDITIONS
60 |
61 | 0. Definitions.
62 |
63 | "This License" refers to version 3 of the GNU Affero General Public License.
64 |
65 | "Copyright" also means copyright-like laws that apply to other kinds of
66 | works, such as semiconductor masks.
67 |
68 | "The Program" refers to any copyrightable work licensed under this
69 | License. Each licensee is addressed as "you". "Licensees" and
70 | "recipients" may be individuals or organizations.
71 |
72 | To "modify" a work means to copy from or adapt all or part of the work
73 | in a fashion requiring copyright permission, other than the making of an
74 | exact copy. The resulting work is called a "modified version" of the
75 | earlier work or a work "based on" the earlier work.
76 |
77 | A "covered work" means either the unmodified Program or a work based
78 | on the Program.
79 |
80 | To "propagate" a work means to do anything with it that, without
81 | permission, would make you directly or secondarily liable for
82 | infringement under applicable copyright law, except executing it on a
83 | computer or modifying a private copy. Propagation includes copying,
84 | distribution (with or without modification), making available to the
85 | public, and in some countries other activities as well.
86 |
87 | To "convey" a work means any kind of propagation that enables other
88 | parties to make or receive copies. Mere interaction with a user through
89 | a computer network, with no transfer of a copy, is not conveying.
90 |
91 | An interactive user interface displays "Appropriate Legal Notices"
92 | to the extent that it includes a convenient and prominently visible
93 | feature that (1) displays an appropriate copyright notice, and (2)
94 | tells the user that there is no warranty for the work (except to the
95 | extent that warranties are provided), that licensees may convey the
96 | work under this License, and how to view a copy of this License. If
97 | the interface presents a list of user commands or options, such as a
98 | menu, a prominent item in the list meets this criterion.
99 |
100 | 1. Source Code.
101 |
102 | The "source code" for a work means the preferred form of the work
103 | for making modifications to it. "Object code" means any non-source
104 | form of a work.
105 |
106 | A "Standard Interface" means an interface that either is an official
107 | standard defined by a recognized standards body, or, in the case of
108 | interfaces specified for a particular programming language, one that
109 | is widely used among developers working in that language.
110 |
111 | The "System Libraries" of an executable work include anything, other
112 | than the work as a whole, that (a) is included in the normal form of
113 | packaging a Major Component, but which is not part of that Major
114 | Component, and (b) serves only to enable use of the work with that
115 | Major Component, or to implement a Standard Interface for which an
116 | implementation is available to the public in source code form. A
117 | "Major Component", in this context, means a major essential component
118 | (kernel, window system, and so on) of the specific operating system
119 | (if any) on which the executable work runs, or a compiler used to
120 | produce the work, or an object code interpreter used to run it.
121 |
122 | The "Corresponding Source" for a work in object code form means all
123 | the source code needed to generate, install, and (for an executable
124 | work) run the object code and to modify the work, including scripts to
125 | control those activities. However, it does not include the work's
126 | System Libraries, or general-purpose tools or generally available free
127 | programs which are used unmodified in performing those activities but
128 | which are not part of the work. For example, Corresponding Source
129 | includes interface definition files associated with source files for
130 | the work, and the source code for shared libraries and dynamically
131 | linked subprograms that the work is specifically designed to require,
132 | such as by intimate data communication or control flow between those
133 | subprograms and other parts of the work.
134 |
135 | The Corresponding Source need not include anything that users
136 | can regenerate automatically from other parts of the Corresponding
137 | Source.
138 |
139 | The Corresponding Source for a work in source code form is that
140 | same work.
141 |
142 | 2. Basic Permissions.
143 |
144 | All rights granted under this License are granted for the term of
145 | copyright on the Program, and are irrevocable provided the stated
146 | conditions are met. This License explicitly affirms your unlimited
147 | permission to run the unmodified Program. The output from running a
148 | covered work is covered by this License only if the output, given its
149 | content, constitutes a covered work. This License acknowledges your
150 | rights of fair use or other equivalent, as provided by copyright law.
151 |
152 | You may make, run and propagate covered works that you do not
153 | convey, without conditions so long as your license otherwise remains
154 | in force. You may convey covered works to others for the sole purpose
155 | of having them make modifications exclusively for you, or provide you
156 | with facilities for running those works, provided that you comply with
157 | the terms of this License in conveying all material for which you do
158 | not control copyright. Those thus making or running the covered works
159 | for you must do so exclusively on your behalf, under your direction
160 | and control, on terms that prohibit them from making any copies of
161 | your copyrighted material outside their relationship with you.
162 |
163 | Conveying under any other circumstances is permitted solely under
164 | the conditions stated below. Sublicensing is not allowed; section 10
165 | makes it unnecessary.
166 |
167 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
168 |
169 | No covered work shall be deemed part of an effective technological
170 | measure under any applicable law fulfilling obligations under article
171 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or
172 | similar laws prohibiting or restricting circumvention of such
173 | measures.
174 |
175 | When you convey a covered work, you waive any legal power to forbid
176 | circumvention of technological measures to the extent such circumvention
177 | is effected by exercising rights under this License with respect to
178 | the covered work, and you disclaim any intention to limit operation or
179 | modification of the work as a means of enforcing, against the work's
180 | users, your or third parties' legal rights to forbid circumvention of
181 | technological measures.
182 |
183 | 4. Conveying Verbatim Copies.
184 |
185 | You may convey verbatim copies of the Program's source code as you
186 | receive it, in any medium, provided that you conspicuously and
187 | appropriately publish on each copy an appropriate copyright notice;
188 | keep intact all notices stating that this License and any
189 | non-permissive terms added in accord with section 7 apply to the code;
190 | keep intact all notices of the absence of any warranty; and give all
191 | recipients a copy of this License along with the Program.
192 |
193 | You may charge any price or no price for each copy that you convey,
194 | and you may offer support or warranty protection for a fee.
195 |
196 | 5. Conveying Modified Source Versions.
197 |
198 | You may convey a work based on the Program, or the modifications to
199 | produce it from the Program, in the form of source code under the
200 | terms of section 4, provided that you also meet all of these conditions:
201 |
202 | a) The work must carry prominent notices stating that you modified
203 | it, and giving a relevant date.
204 |
205 | b) The work must carry prominent notices stating that it is
206 | released under this License and any conditions added under section
207 | 7. This requirement modifies the requirement in section 4 to
208 | "keep intact all notices".
209 |
210 | c) You must license the entire work, as a whole, under this
211 | License to anyone who comes into possession of a copy. This
212 | License will therefore apply, along with any applicable section 7
213 | additional terms, to the whole of the work, and all its parts,
214 | regardless of how they are packaged. This License gives no
215 | permission to license the work in any other way, but it does not
216 | invalidate such permission if you have separately received it.
217 |
218 | d) If the work has interactive user interfaces, each must display
219 | Appropriate Legal Notices; however, if the Program has interactive
220 | interfaces that do not display Appropriate Legal Notices, your
221 | work need not make them do so.
222 |
223 | A compilation of a covered work with other separate and independent
224 | works, which are not by their nature extensions of the covered work,
225 | and which are not combined with it such as to form a larger program,
226 | in or on a volume of a storage or distribution medium, is called an
227 | "aggregate" if the compilation and its resulting copyright are not
228 | used to limit the access or legal rights of the compilation's users
229 | beyond what the individual works permit. Inclusion of a covered work
230 | in an aggregate does not cause this License to apply to the other
231 | parts of the aggregate.
232 |
233 | 6. Conveying Non-Source Forms.
234 |
235 | You may convey a covered work in object code form under the terms
236 | of sections 4 and 5, provided that you also convey the
237 | machine-readable Corresponding Source under the terms of this License,
238 | in one of these ways:
239 |
240 | a) Convey the object code in, or embodied in, a physical product
241 | (including a physical distribution medium), accompanied by the
242 | Corresponding Source fixed on a durable physical medium
243 | customarily used for software interchange.
244 |
245 | b) Convey the object code in, or embodied in, a physical product
246 | (including a physical distribution medium), accompanied by a
247 | written offer, valid for at least three years and valid for as
248 | long as you offer spare parts or customer support for that product
249 | model, to give anyone who possesses the object code either (1) a
250 | copy of the Corresponding Source for all the software in the
251 | product that is covered by this License, on a durable physical
252 | medium customarily used for software interchange, for a price no
253 | more than your reasonable cost of physically performing this
254 | conveying of source, or (2) access to copy the
255 | Corresponding Source from a network server at no charge.
256 |
257 | c) Convey individual copies of the object code with a copy of the
258 | written offer to provide the Corresponding Source. This
259 | alternative is allowed only occasionally and noncommercially, and
260 | only if you received the object code with such an offer, in accord
261 | with subsection 6b.
262 |
263 | d) Convey the object code by offering access from a designated
264 | place (gratis or for a charge), and offer equivalent access to the
265 | Corresponding Source in the same way through the same place at no
266 | further charge. You need not require recipients to copy the
267 | Corresponding Source along with the object code. If the place to
268 | copy the object code is a network server, the Corresponding Source
269 | may be on a different server (operated by you or a third party)
270 | that supports equivalent copying facilities, provided you maintain
271 | clear directions next to the object code saying where to find the
272 | Corresponding Source. Regardless of what server hosts the
273 | Corresponding Source, you remain obligated to ensure that it is
274 | available for as long as needed to satisfy these requirements.
275 |
276 | e) Convey the object code using peer-to-peer transmission, provided
277 | you inform other peers where the object code and Corresponding
278 | Source of the work are being offered to the general public at no
279 | charge under subsection 6d.
280 |
281 | A separable portion of the object code, whose source code is excluded
282 | from the Corresponding Source as a System Library, need not be
283 | included in conveying the object code work.
284 |
285 | A "User Product" is either (1) a "consumer product", which means any
286 | tangible personal property which is normally used for personal, family,
287 | or household purposes, or (2) anything designed or sold for incorporation
288 | into a dwelling. In determining whether a product is a consumer product,
289 | doubtful cases shall be resolved in favor of coverage. For a particular
290 | product received by a particular user, "normally used" refers to a
291 | typical or common use of that class of product, regardless of the status
292 | of the particular user or of the way in which the particular user
293 | actually uses, or expects or is expected to use, the product. A product
294 | is a consumer product regardless of whether the product has substantial
295 | commercial, industrial or non-consumer uses, unless such uses represent
296 | the only significant mode of use of the product.
297 |
298 | "Installation Information" for a User Product means any methods,
299 | procedures, authorization keys, or other information required to install
300 | and execute modified versions of a covered work in that User Product from
301 | a modified version of its Corresponding Source. The information must
302 | suffice to ensure that the continued functioning of the modified object
303 | code is in no case prevented or interfered with solely because
304 | modification has been made.
305 |
306 | If you convey an object code work under this section in, or with, or
307 | specifically for use in, a User Product, and the conveying occurs as
308 | part of a transaction in which the right of possession and use of the
309 | User Product is transferred to the recipient in perpetuity or for a
310 | fixed term (regardless of how the transaction is characterized), the
311 | Corresponding Source conveyed under this section must be accompanied
312 | by the Installation Information. But this requirement does not apply
313 | if neither you nor any third party retains the ability to install
314 | modified object code on the User Product (for example, the work has
315 | been installed in ROM).
316 |
317 | The requirement to provide Installation Information does not include a
318 | requirement to continue to provide support service, warranty, or updates
319 | for a work that has been modified or installed by the recipient, or for
320 | the User Product in which it has been modified or installed. Access to a
321 | network may be denied when the modification itself materially and
322 | adversely affects the operation of the network or violates the rules and
323 | protocols for communication across the network.
324 |
325 | Corresponding Source conveyed, and Installation Information provided,
326 | in accord with this section must be in a format that is publicly
327 | documented (and with an implementation available to the public in
328 | source code form), and must require no special password or key for
329 | unpacking, reading or copying.
330 |
331 | 7. Additional Terms.
332 |
333 | "Additional permissions" are terms that supplement the terms of this
334 | License by making exceptions from one or more of its conditions.
335 | Additional permissions that are applicable to the entire Program shall
336 | be treated as though they were included in this License, to the extent
337 | that they are valid under applicable law. If additional permissions
338 | apply only to part of the Program, that part may be used separately
339 | under those permissions, but the entire Program remains governed by
340 | this License without regard to the additional permissions.
341 |
342 | When you convey a copy of a covered work, you may at your option
343 | remove any additional permissions from that copy, or from any part of
344 | it. (Additional permissions may be written to require their own
345 | removal in certain cases when you modify the work.) You may place
346 | additional permissions on material, added by you to a covered work,
347 | for which you have or can give appropriate copyright permission.
348 |
349 | Notwithstanding any other provision of this License, for material you
350 | add to a covered work, you may (if authorized by the copyright holders of
351 | that material) supplement the terms of this License with terms:
352 |
353 | a) Disclaiming warranty or limiting liability differently from the
354 | terms of sections 15 and 16 of this License; or
355 |
356 | b) Requiring preservation of specified reasonable legal notices or
357 | author attributions in that material or in the Appropriate Legal
358 | Notices displayed by works containing it; or
359 |
360 | c) Prohibiting misrepresentation of the origin of that material, or
361 | requiring that modified versions of such material be marked in
362 | reasonable ways as different from the original version; or
363 |
364 | d) Limiting the use for publicity purposes of names of licensors or
365 | authors of the material; or
366 |
367 | e) Declining to grant rights under trademark law for use of some
368 | trade names, trademarks, or service marks; or
369 |
370 | f) Requiring indemnification of licensors and authors of that
371 | material by anyone who conveys the material (or modified versions of
372 | it) with contractual assumptions of liability to the recipient, for
373 | any liability that these contractual assumptions directly impose on
374 | those licensors and authors.
375 |
376 | All other non-permissive additional terms are considered "further
377 | restrictions" within the meaning of section 10. If the Program as you
378 | received it, or any part of it, contains a notice stating that it is
379 | governed by this License along with a term that is a further
380 | restriction, you may remove that term. If a license document contains
381 | a further restriction but permits relicensing or conveying under this
382 | License, you may add to a covered work material governed by the terms
383 | of that license document, provided that the further restriction does
384 | not survive such relicensing or conveying.
385 |
386 | If you add terms to a covered work in accord with this section, you
387 | must place, in the relevant source files, a statement of the
388 | additional terms that apply to those files, or a notice indicating
389 | where to find the applicable terms.
390 |
391 | Additional terms, permissive or non-permissive, may be stated in the
392 | form of a separately written license, or stated as exceptions;
393 | the above requirements apply either way.
394 |
395 | 8. Termination.
396 |
397 | You may not propagate or modify a covered work except as expressly
398 | provided under this License. Any attempt otherwise to propagate or
399 | modify it is void, and will automatically terminate your rights under
400 | this License (including any patent licenses granted under the third
401 | paragraph of section 11).
402 |
403 | However, if you cease all violation of this License, then your
404 | license from a particular copyright holder is reinstated (a)
405 | provisionally, unless and until the copyright holder explicitly and
406 | finally terminates your license, and (b) permanently, if the copyright
407 | holder fails to notify you of the violation by some reasonable means
408 | prior to 60 days after the cessation.
409 |
410 | Moreover, your license from a particular copyright holder is
411 | reinstated permanently if the copyright holder notifies you of the
412 | violation by some reasonable means, this is the first time you have
413 | received notice of violation of this License (for any work) from that
414 | copyright holder, and you cure the violation prior to 30 days after
415 | your receipt of the notice.
416 |
417 | Termination of your rights under this section does not terminate the
418 | licenses of parties who have received copies or rights from you under
419 | this License. If your rights have been terminated and not permanently
420 | reinstated, you do not qualify to receive new licenses for the same
421 | material under section 10.
422 |
423 | 9. Acceptance Not Required for Having Copies.
424 |
425 | You are not required to accept this License in order to receive or
426 | run a copy of the Program. Ancillary propagation of a covered work
427 | occurring solely as a consequence of using peer-to-peer transmission
428 | to receive a copy likewise does not require acceptance. However,
429 | nothing other than this License grants you permission to propagate or
430 | modify any covered work. These actions infringe copyright if you do
431 | not accept this License. Therefore, by modifying or propagating a
432 | covered work, you indicate your acceptance of this License to do so.
433 |
434 | 10. Automatic Licensing of Downstream Recipients.
435 |
436 | Each time you convey a covered work, the recipient automatically
437 | receives a license from the original licensors, to run, modify and
438 | propagate that work, subject to this License. You are not responsible
439 | for enforcing compliance by third parties with this License.
440 |
441 | An "entity transaction" is a transaction transferring control of an
442 | organization, or substantially all assets of one, or subdividing an
443 | organization, or merging organizations. If propagation of a covered
444 | work results from an entity transaction, each party to that
445 | transaction who receives a copy of the work also receives whatever
446 | licenses to the work the party's predecessor in interest had or could
447 | give under the previous paragraph, plus a right to possession of the
448 | Corresponding Source of the work from the predecessor in interest, if
449 | the predecessor has it or can get it with reasonable efforts.
450 |
451 | You may not impose any further restrictions on the exercise of the
452 | rights granted or affirmed under this License. For example, you may
453 | not impose a license fee, royalty, or other charge for exercise of
454 | rights granted under this License, and you may not initiate litigation
455 | (including a cross-claim or counterclaim in a lawsuit) alleging that
456 | any patent claim is infringed by making, using, selling, offering for
457 | sale, or importing the Program or any portion of it.
458 |
459 | 11. Patents.
460 |
461 | A "contributor" is a copyright holder who authorizes use under this
462 | License of the Program or a work on which the Program is based. The
463 | work thus licensed is called the contributor's "contributor version".
464 |
465 | A contributor's "essential patent claims" are all patent claims
466 | owned or controlled by the contributor, whether already acquired or
467 | hereafter acquired, that would be infringed by some manner, permitted
468 | by this License, of making, using, or selling its contributor version,
469 | but do not include claims that would be infringed only as a
470 | consequence of further modification of the contributor version. For
471 | purposes of this definition, "control" includes the right to grant
472 | patent sublicenses in a manner consistent with the requirements of
473 | this License.
474 |
475 | Each contributor grants you a non-exclusive, worldwide, royalty-free
476 | patent license under the contributor's essential patent claims, to
477 | make, use, sell, offer for sale, import and otherwise run, modify and
478 | propagate the contents of its contributor version.
479 |
480 | In the following three paragraphs, a "patent license" is any express
481 | agreement or commitment, however denominated, not to enforce a patent
482 | (such as an express permission to practice a patent or covenant not to
483 | sue for patent infringement). To "grant" such a patent license to a
484 | party means to make such an agreement or commitment not to enforce a
485 | patent against the party.
486 |
487 | If you convey a covered work, knowingly relying on a patent license,
488 | and the Corresponding Source of the work is not available for anyone
489 | to copy, free of charge and under the terms of this License, through a
490 | publicly available network server or other readily accessible means,
491 | then you must either (1) cause the Corresponding Source to be so
492 | available, or (2) arrange to deprive yourself of the benefit of the
493 | patent license for this particular work, or (3) arrange, in a manner
494 | consistent with the requirements of this License, to extend the patent
495 | license to downstream recipients. "Knowingly relying" means you have
496 | actual knowledge that, but for the patent license, your conveying the
497 | covered work in a country, or your recipient's use of the covered work
498 | in a country, would infringe one or more identifiable patents in that
499 | country that you have reason to believe are valid.
500 |
501 | If, pursuant to or in connection with a single transaction or
502 | arrangement, you convey, or propagate by procuring conveyance of, a
503 | covered work, and grant a patent license to some of the parties
504 | receiving the covered work authorizing them to use, propagate, modify
505 | or convey a specific copy of the covered work, then the patent license
506 | you grant is automatically extended to all recipients of the covered
507 | work and works based on it.
508 |
509 | A patent license is "discriminatory" if it does not include within
510 | the scope of its coverage, prohibits the exercise of, or is
511 | conditioned on the non-exercise of one or more of the rights that are
512 | specifically granted under this License. You may not convey a covered
513 | work if you are a party to an arrangement with a third party that is
514 | in the business of distributing software, under which you make payment
515 | to the third party based on the extent of your activity of conveying
516 | the work, and under which the third party grants, to any of the
517 | parties who would receive the covered work from you, a discriminatory
518 | patent license (a) in connection with copies of the covered work
519 | conveyed by you (or copies made from those copies), or (b) primarily
520 | for and in connection with specific products or compilations that
521 | contain the covered work, unless you entered into that arrangement,
522 | or that patent license was granted, prior to 28 March 2007.
523 |
524 | Nothing in this License shall be construed as excluding or limiting
525 | any implied license or other defenses to infringement that may
526 | otherwise be available to you under applicable patent law.
527 |
528 | 12. No Surrender of Others' Freedom.
529 |
530 | If conditions are imposed on you (whether by court order, agreement or
531 | otherwise) that contradict the conditions of this License, they do not
532 | excuse you from the conditions of this License. If you cannot convey a
533 | covered work so as to satisfy simultaneously your obligations under this
534 | License and any other pertinent obligations, then as a consequence you may
535 | not convey it at all. For example, if you agree to terms that obligate you
536 | to collect a royalty for further conveying from those to whom you convey
537 | the Program, the only way you could satisfy both those terms and this
538 | License would be to refrain entirely from conveying the Program.
539 |
540 | 13. Remote Network Interaction; Use with the GNU General Public License.
541 |
542 | Notwithstanding any other provision of this License, if you modify the
543 | Program, your modified version must prominently offer all users
544 | interacting with it remotely through a computer network (if your version
545 | supports such interaction) an opportunity to receive the Corresponding
546 | Source of your version by providing access to the Corresponding Source
547 | from a network server at no charge, through some standard or customary
548 | means of facilitating copying of software. This Corresponding Source
549 | shall include the Corresponding Source for any work covered by version 3
550 | of the GNU General Public License that is incorporated pursuant to the
551 | following paragraph.
552 |
553 | Notwithstanding any other provision of this License, you have
554 | permission to link or combine any covered work with a work licensed
555 | under version 3 of the GNU General Public License into a single
556 | combined work, and to convey the resulting work. The terms of this
557 | License will continue to apply to the part which is the covered work,
558 | but the work with which it is combined will remain governed by version
559 | 3 of the GNU General Public License.
560 |
561 | 14. Revised Versions of this License.
562 |
563 | The Free Software Foundation may publish revised and/or new versions of
564 | the GNU Affero General Public License from time to time. Such new versions
565 | will be similar in spirit to the present version, but may differ in detail to
566 | address new problems or concerns.
567 |
568 | Each version is given a distinguishing version number. If the
569 | Program specifies that a certain numbered version of the GNU Affero General
570 | Public License "or any later version" applies to it, you have the
571 | option of following the terms and conditions either of that numbered
572 | version or of any later version published by the Free Software
573 | Foundation. If the Program does not specify a version number of the
574 | GNU Affero General Public License, you may choose any version ever published
575 | by the Free Software Foundation.
576 |
577 | If the Program specifies that a proxy can decide which future
578 | versions of the GNU Affero General Public License can be used, that proxy's
579 | public statement of acceptance of a version permanently authorizes you
580 | to choose that version for the Program.
581 |
582 | Later license versions may give you additional or different
583 | permissions. However, no additional obligations are imposed on any
584 | author or copyright holder as a result of your choosing to follow a
585 | later version.
586 |
587 | 15. Disclaimer of Warranty.
588 |
589 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
590 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
591 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
592 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
593 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
594 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
595 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
596 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
597 |
598 | 16. Limitation of Liability.
599 |
600 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
601 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
602 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
603 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
604 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
605 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
606 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
607 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
608 | SUCH DAMAGES.
609 |
610 | 17. Interpretation of Sections 15 and 16.
611 |
612 | If the disclaimer of warranty and limitation of liability provided
613 | above cannot be given local legal effect according to their terms,
614 | reviewing courts shall apply local law that most closely approximates
615 | an absolute waiver of all civil liability in connection with the
616 | Program, unless a warranty or assumption of liability accompanies a
617 | copy of the Program in return for a fee.
618 |
619 | END OF TERMS AND CONDITIONS
620 |
621 | How to Apply These Terms to Your New Programs
622 |
623 | If you develop a new program, and you want it to be of the greatest
624 | possible use to the public, the best way to achieve this is to make it
625 | free software which everyone can redistribute and change under these terms.
626 |
627 | To do so, attach the following notices to the program. It is safest
628 | to attach them to the start of each source file to most effectively
629 | state the exclusion of warranty; and each file should have at least
630 | the "copyright" line and a pointer to where the full notice is found.
631 |
632 |
633 | Copyright (C)
634 |
635 | This program is free software: you can redistribute it and/or modify
636 | it under the terms of the GNU Affero General Public License as published
637 | by the Free Software Foundation, either version 3 of the License, or
638 | (at your option) any later version.
639 |
640 | This program is distributed in the hope that it will be useful,
641 | but WITHOUT ANY WARRANTY; without even the implied warranty of
642 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
643 | GNU Affero General Public License for more details.
644 |
645 | You should have received a copy of the GNU Affero General Public License
646 | along with this program. If not, see .
647 |
648 | Also add information on how to contact you by electronic and paper mail.
649 |
650 | If your software can interact with users remotely through a computer
651 | network, you should also make sure that it provides a way for users to
652 | get its source. For example, if your program is a web application, its
653 | interface could display a "Source" link that leads users to an archive
654 | of the code. There are many ways you could offer source, and different
655 | solutions will be better for different programs; see section 13 for the
656 | specific requirements.
657 |
658 | You should also get your employer (if you work as a programmer) or school,
659 | if any, to sign a "copyright disclaimer" for the program, if necessary.
660 | For more information on this, and how to apply and follow the GNU AGPL, see
661 | .
662 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
11 |
12 | **TL;DR: `wsl --install` then restart your machine.**
13 |
14 | ## Install Ubuntu 22.04 From MS Store
15 |
16 | Go to MS Store and install the latest version of Ubuntu 22.04 LTS.
17 | 
18 |
19 | ## Installation
20 |
21 | **Before installation make sure that you have run and closed the Claude Desktop app at least once.**
22 |
23 | ### Install and Run Claude Sandbox
24 | Open your Ubuntu 22.04 LTS from Start Menu and run the following commands:
25 |
26 | ```bash
27 | wget -O- https://raw.githubusercontent.com/emsi/claude-desktop/refs/heads/main/install-claude-desktop.sh | bash
28 |
29 | ~/sandboxes/claude_sandbox.sh
30 | ```
31 |
32 | Copy the `windows_claude_desktop_config.json` from this repo to `%APPDATA%\Claude\` folder **AND RENAME IT TO `claude_desktop_config.json`**.
33 |
34 | 
35 |
36 |
37 | ### Create MyManus Project in the Claude Application:
38 |
39 | 
40 |
41 | 
42 |
43 | 
44 |
45 | 
46 |
47 | ## Paste the prompt from [here](./prompts/prompt.md)
48 | Into here:
49 |
50 | 
51 |
52 | If you stumble upon any issues read the next section.
53 |
54 | # USAGE
55 |
56 | When starting a new conversation make sure to select the MyManus project:
57 |
58 | 
59 |
60 |
61 | # Automatic Tools Acceptance
62 |
63 | If you want to automatically accept the tool usage read [this guide](https://github.com/emsi/claude-desktop/blob/main/MCP_LINUX.md#auto-accepting-tools)
64 |
--------------------------------------------------------------------------------
/assets/BeforeWeStart.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/BeforeWeStart.gif
--------------------------------------------------------------------------------
/assets/Create_MyManus_Project.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Create_MyManus_Project.png
--------------------------------------------------------------------------------
/assets/Create_Project.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Create_Project.png
--------------------------------------------------------------------------------
/assets/Edit_Config.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Edit_Config.png
--------------------------------------------------------------------------------
/assets/MyManus.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/MyManus.png
--------------------------------------------------------------------------------
/assets/MyManus_Use.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/MyManus_Use.png
--------------------------------------------------------------------------------
/assets/Project_Instructions.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Project_Instructions.png
--------------------------------------------------------------------------------
/assets/Projects.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Projects.png
--------------------------------------------------------------------------------
/assets/Set_Project_Instructions.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Set_Project_Instructions.png
--------------------------------------------------------------------------------
/assets/Settings.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/Settings.png
--------------------------------------------------------------------------------
/assets/appdata_claude.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/appdata_claude.png
--------------------------------------------------------------------------------
/assets/audio_transcription_research.tgz:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/audio_transcription_research.tgz
--------------------------------------------------------------------------------
/assets/start_run_ubuntu.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/start_run_ubuntu.png
--------------------------------------------------------------------------------
/assets/ubuntu@msstore.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/emsi/MyManus/e22c00943ff478660e2c766ebba132b50fcb7fd4/assets/ubuntu@msstore.png
--------------------------------------------------------------------------------
/claude_desktop_config.json:
--------------------------------------------------------------------------------
1 | {
2 | "mcpServers": {
3 | "@automatalabs-mcp-server-playwright": {
4 | "runtime": "node",
5 | "command": "npx",
6 | "args": [
7 | "-y",
8 | "@automatalabs/mcp-server-playwright"
9 | ],
10 | "env": {
11 | "DISPLAY": ":0"
12 | }
13 | },
14 | "sandbox": {
15 | "command": "uvx",
16 | "args": [
17 | "mcp-server-shell @ git+https://github.com/emsi/mcp-server-shell"
18 | ],
19 | "env": {
20 | "DISPLAY": ":0"
21 | }
22 | },
23 | "filesystem": {
24 | "command": "npx",
25 | "args": [
26 | "-y",
27 | "@modelcontextprotocol/server-filesystem",
28 | "/home/agent"
29 | ]
30 | }
31 | }
32 | }
33 |
--------------------------------------------------------------------------------
/prompts/prompt.md:
--------------------------------------------------------------------------------
1 |
2 | You excel at the following tasks:
3 | 1. Information gathering, fact-checking, and documentation
4 | 2. Data processing, analysis, and visualization
5 | 3. Writing multi-chapter articles and in-depth research reports
6 | 4. Creating websites, applications, and tools
7 | 5. Using programming to solve various problems beyond development
8 | 6. Various tasks that can be accomplished using computers and the internet
9 |
10 |
11 |
12 | - Default working language: **English**
13 | - Use the language specified by user in messages as the working language when explicitly provided
14 | - All thinking and responses must be in the working language
15 | - Natural language arguments in tool calls must be in the working language
16 | - Avoid using pure lists and bullet points format in any language
17 |
18 |
19 |
20 | - Access a Linux sandbox environment with internet connection
21 | - Use shell, text editor, browser, and other software
22 | - Write and run code in Python and various programming languages
23 | - Independently install required software packages and dependencies via shell
24 | - Deploy websites or applications and provide public access
25 | - Suggest users to temporarily take control of the browser for sensitive operations when necessary
26 | - Utilize various tools to complete user-assigned tasks step by step
27 |
28 |
29 |
30 | You will be provided with a chronological event stream (may be truncated or partially omitted) containing the following types of events:
31 | 1. Message: Messages input by actual users
32 | 2. Action: Tool use (function calling) actions
33 | 3. Observation: Results generated from corresponding action execution
34 | 4. Plan: Task step planning and status updates provided by the Planner module
35 | 5. Knowledge: Task-related knowledge and best practices provided by the Knowledge module
36 | 6. Datasource: Data API documentation provided by the Datasource module
37 | 7. Other miscellaneous events generated during system operation
38 |
39 |
40 |
41 | You are operating in an agent loop, iteratively completing tasks through these steps:
42 | 1. Analyze Events: Understand user needs and current state through event stream, focusing on latest user messages and execution results
43 | 2. Select Tools: Choose next tool call based on current state, task planning, relevant knowledge and available data APIs
44 | 3. Wait for Execution: Selected tool action will be executed by sandbox environment with new observations added to event stream
45 | 4. Iterate: Choose only one tool call per iteration, patiently repeat above steps until task completion
46 | 5. Submit Results: Send results to user via message tools, providing deliverables and related files as message attachments
47 | 6. Enter Standby: Enter idle state when all tasks are completed or user explicitly requests to stop, and wait for new tasks
48 |
49 |
50 |
51 | - System is equipped with planner module for overall task planning
52 | - Task planning will be provided as events in the event stream
53 | - Task plans use numbered pseudocode to represent execution steps
54 | - Each planning update includes the current step number, status, and reflection
55 | - Pseudocode representing execution steps will update when overall task objective changes
56 | - Must complete all planned steps and reach the final step number by completion
57 |
58 |
59 |
60 | - System is equipped with knowledge and memory module for best practice references
61 | - Task-relevant knowledge will be provided as events in the event stream
62 | - Each knowledge item has its scope and should only be adopted when conditions are met
63 |
64 |
65 |
66 | - System is equipped with data API module for accessing authoritative datasources
67 | - Available data APIs and their documentation will be provided as events in the event stream
68 | - Only use data APIs already existing in the event stream; fabricating non-existent APIs is prohibited
69 | - Prioritize using APIs for data retrieval; only use public internet when data APIs cannot meet requirements
70 | - Data API usage costs are covered by the system, no login or authorization needed
71 | - Data APIs must be called through Python code and cannot be used as tools
72 | - Python libraries for data APIs are pre-installed in the environment, ready to use after import
73 | - Save retrieved data to files instead of outputting intermediate results
74 |
75 |
76 |
77 | - Create todo.md file as checklist based on task planning from the Planner module
78 | - Task planning takes precedence over todo.md, while todo.md contains more details
79 | - Update markers in todo.md via text replacement tool immediately after completing each item
80 | - Rebuild todo.md when task planning changes significantly
81 | - Must use todo.md to record and update progress for information gathering tasks
82 | - When all planned steps are complete, verify todo.md completion and remove skipped items
83 |
84 |
85 |
86 | - Reply immediately to new user messages before other operations
87 | - First reply must be brief, only confirming receipt without specific solutions
88 | - Events from Planner, Knowledge, and Datasource modules are system-generated, no reply needed
89 | - Notify users with brief explanation when changing methods or strategies
90 |
91 |
92 |
93 | - Use filesystem tools for reading, writing, appending, and editing to avoid string escape issues in shell commands
94 | - Actively save intermediate results and store different types of reference information in separate files
95 | - When merging text files, must use append mode of file writing tool to concatenate content to target file
96 | - When making small file edits (like updating todo.md), use edit_file tool with specific text replacement commands.
97 | - Strictly follow requirements in , and avoid using list formats in any files except todo.md
98 |
99 |
100 |
101 | - Information priority: authoritative data from datasource API > web search > model's internal knowledge
102 | - Prefer dedicated search tools over browser access to search engine result pages
103 | - Snippets in search results are not valid sources; must access original pages via browser
104 | - Access multiple URLs from search results for comprehensive information or cross-validation
105 | - Conduct searches step by step: search multiple attributes of single entity separately, process multiple entities one by one
106 |
107 |
108 |
109 | - Must use browser tools to access and comprehend all URLs provided by users in messages
110 | - Must use browser tools to access URLs from search tool results
111 | - Actively explore valuable links for deeper information, either by clicking elements or accessing URLs directly
112 | - Browser tools only return elements in visible viewport by default
113 | - Use message tools to suggest user to take over the browser for sensitive operations or actions with side effects when necessary
114 | - When intercating with a webpage make sure to first close all cookie banners and popups
115 |
116 |
117 |
118 | - Avoid commands requiring confirmation; actively use -y or -f flags for automatic confirmation
119 | - Avoid commands with excessive output; save (redirect >) to files when necessary
120 | - Chain multiple commands with && operator to minimize interruptions
121 | - Use pipe operator to pass command outputs, simplifying operations
122 | - Use non-interactive \`bc\` for simple calculations, Python for complex math; never calculate mentally
123 | - When interacting with docker use newer compose command: `docker compose`.
124 |
125 |
126 |
127 | - Must save code to files before execution; direct code input to interpreter commands is forbidden
128 | - Write Python code for complex mathematical calculations and analysis
129 | - Use search tools to find solutions when encountering unfamiliar problems
130 |
131 |
132 |
133 | - All services can be temporarily accessed by user on localhost
134 | - Users can directly access sandbox environment network
135 | - For web services, you may test access locally via browser
136 | - When starting services, listen on l127.0.0.1 for security, avoid binding to specific IP addresses to ensure user accessibility
137 |
138 |
139 |
140 | - Write content in continuous paragraphs using varied sentence lengths for engaging prose; avoid list formatting
141 | - Use prose and paragraphs by default; only employ lists when explicitly requested by users
142 | - All writing must be highly detailed with a minimum length of several thousand words, unless user explicitly specifies length or format requirements
143 | - When writing based on references, actively cite original text with sources and provide a reference list with URLs at the end
144 | - For lengthy documents, first save each section as separate draft files, then append them sequentially to create the final document
145 | - During final compilation, no content should be reduced or summarized; the final length must exceed the sum of all individual draft files
146 |
147 |
148 |
149 | - When errors occur, first verify tool names and arguments
150 | - Attempt to fix issues based on error messages; if unsuccessful, try alternative methods
151 | - When multiple approaches fail, report failure reasons to user and request assistance
152 |
153 |
154 |
155 | System Environment:
156 | - Ubuntu 22.04 (linux/amd64), with internet access
157 | - You can manage files in the /home/agent directory:
158 | ```
159 | $ tree /home/agent/
160 | /home/agent/
161 | |-- Documents
162 | | |-- CODE
163 | | `-- NOTES
164 | `-- Downloads
165 | ```
166 | - Store code and scripts in the CODE directory. Create decated subdirectories for each new coding project.
167 | - When creating notes, use the NOTES directory and store them in markdown files. Create subdirectories for different notes categories.
168 | - If there are notes assets like images, store them in the same directory as the markdown file.
169 |
170 |
171 |
172 | - Do not mention any specific tool names to users in messages
173 | - Carefully verify available tools; do not fabricate non-existent tools
174 | - Events may originate from other system modules; only use explicitly provided tools
175 |
--------------------------------------------------------------------------------
/prompts/uv-cheat-sheet.md:
--------------------------------------------------------------------------------
1 | # uv Cheat Sheet – Modern Python Environment & Dependency Manager
2 |
3 | ## Installation and Upgrading **uv**
4 | `curl -fsSL https://uv.dev/install.sh | bash`
5 | or
6 | `wget -qO- https://uv.dev/install.sh | bash`
7 |
8 | ## Initializing New Projects
9 | - **Create a new project:**
10 | ```bash
11 | uv init
12 | ```
13 | This command generates a new Python project in the current directory. By default this creates an *application* project with:
14 | - A `pyproject.toml` containing basic metadata (name, version, requires-python, etc.).
15 | - A sample Python file (e.g. `main.py`) and a `README.md`.
16 | - A `.python-version` file pinning the Python version for consistency.
17 | - **Library projects:** Use:
18 | ```bash
19 | uv init --lib
20 | ```
21 | for a library intended for distribution. This creates a `src/` layout with a package directory, an `__init__.py`, and a `py.typed` file for type hints. A build system is added to `pyproject.toml` so the project can be installed and published.
22 | - **Packaged CLI apps:** Use:
23 | ```bash
24 | uv init --package
25 | ```
26 | to create an application that will be packaged. This uses a `src/` layout and adds a `[project.scripts]` entry point in `pyproject.toml` (so it installs a console script). After initializing, you can run the app with:
27 | ```bash
28 | uv run
29 | ```
30 | - **Minimal project:** Use:
31 | ```bash
32 | uv init --bare
33 | ```
34 | to create only a `pyproject.toml` (no code, README, or VCS setup). This skips creating the `.python-version` file, README, sample code, and doesn’t init a git repo. You can combine `--bare` with other flags (like `--lib` or `--build-backend`) if you want a minimal layout with just the configuration.
35 |
36 | ## Adding and Removing Dependencies
37 | - **Add a dependency:**
38 | ```bash
39 | uv add
40 | ```
41 | This command adds a package to your project’s dependencies (in `pyproject.toml`), similar to doing a `pip install` plus updating your configuration. For example:
42 | ```bash
43 | uv add httpx
44 | ```
45 | This will install the latest compatible version of **httpx** and add it to `[project.dependencies]` in `pyproject.toml`.
46 | - You can specify version constraints, e.g., `uv add "requests<3"`.
47 | - **Dev or optional dependencies:** Use `--dev` to add to development dependencies or `--group ` for a custom dependency group. For example, `uv add --dev pytest` adds **pytest** to the dev group. Use `--optional` to add to optional dependencies (extras).
48 | - You can also add direct URLs or VCS references. For example:
49 | ```bash
50 | uv add "mypkg @ git+https://github.com/user/mypkg.git"
51 | ```
52 | adds **mypkg** and records its Git source in `pyproject.toml`.
53 | - **Remove a dependency:**
54 | ```bash
55 | uv remove
56 | ```
57 | This command removes the package from `pyproject.toml` and uninstalls it from the environment. If the package is part of a specific group (like dev), use `--dev` or `--group `.
58 |
59 | ## Installing & Syncing Dependencies
60 | - **Sync project environment:**
61 | ```bash
62 | uv sync
63 | ```
64 | After adding or removing dependencies, this command installs the exact dependency set into your project’s virtual environment. It ensures that your environment matches the locked requirements, similar to using a requirements file.
65 | - **Lockfile:** uv uses a lockfile (`uv.lock`) to record resolved dependency versions.
66 | - Running `uv lock` computes a fresh resolution of dependencies and updates the lockfile.
67 | - Use `uv lock --check` to verify that the lockfile is up-to-date with your project settings.
68 | - Use `uv lock --locked` to prevent automatic updates, and `uv lock --frozen` to use the lockfile without checking project metadata.
69 | - **Install optional/groups:** By default, `uv sync` installs main project dependencies and the **dev** group. To install other groups or extras:
70 | - Use `uv sync --extra ` to include a specific extra.
71 | - Use `--all-extras` to install all extras at once.
72 | - Use `--group ` to include a specific group, or `--no-group ` to exclude one. The special group `dev` is included by default but can be omitted with `--no-dev`.
73 |
74 | - **Export requirements:**
75 | ```bash
76 | uv export --format requirements-txt > requirements.txt
77 | ```
78 | This exports the lockfile to a pip-compatible `requirements.txt`.
79 |
80 | ## Running Code in the uv Environment
81 | - **Running project code:**
82 | ```bash
83 | uv run
84 | ```
85 | This command runs commands within the project’s environment, ensuring the correct Python interpreter and dependencies are used. For example:
86 | - `uv run python main.py` runs your **main.py** using the project’s Python.
87 | - `uv run pytest` runs **pytest** (if it’s a dev dependency) inside the environment.
88 | uv will auto-sync the environment before executing the command.
89 | - **Running any command:** You can pass any command (not just Python) to `uv run`. For example:
90 | ```bash
91 | uv run bash scripts/migrate.sh
92 | ```
93 | runs the **bash** script with the project’s dependencies available. If your project defines a console script in `[project.scripts]`, you can run it directly with `uv run `.
94 | - **Inline additional dependencies:**
95 | ```bash
96 | uv run --with example.py
97 | ```
98 | This temporarily installs a package (like **rich**) for that specific run without permanently adding it to your project. You can specify version constraints if needed. Use `--no-project` to run the script in a completely isolated environment.
99 |
100 | ## Running Single-File Scripts with Inline Dependencies
101 | uv supports self-contained Python scripts that declare their own dependencies:
102 | - **Initialize an inline script:**
103 | ```bash
104 | uv init --script --python
105 | ```
106 | This creates a new script file with a shebang and an inline dependency metadata header.
107 | - **Declare script dependencies:**
108 | ```bash
109 | uv add --script
110 | ```
111 | For example:
112 | ```bash
113 | uv add --script myscript.py requests<3 rich
114 | ```
115 | This adds **requests** and **rich** as dependencies, inserting a special commented TOML block at the top of the script.
116 | - **Run the script:**
117 | ```bash
118 | uv run myscript.py
119 | ```
120 | uv detects the inline metadata and automatically creates an isolated environment with the specified dependencies.
121 | - To run the script without using the project’s environment, use:
122 | ```bash
123 | uv run --no-project myscript.py
124 | ```
125 |
126 | ## Using CLI Tools (Package CLIs) with uv
127 | uv can manage Python CLI tools similar to pipx:
128 | - **Run a tool without installing (ephemeral environment):**
129 | ```bash
130 | uv tool run [args...]
131 | ```
132 | Alternatively, you can use the alias `uvx`. For example:
133 | ```bash
134 | uvx black --version
135 | ```
136 | The tool is downloaded (if not cached) and run; subsequent calls reuse the cached environment.
137 | - **Install a tool (persistent):**
138 | ```bash
139 | uv tool install
140 | ```
141 | This installs a tool persistently, making the executable available on your PATH. For example:
142 | ```bash
143 | uv tool install httpie
144 | ```
145 | List installed tools with `uv tool list` and remove one with `uv tool uninstall `. If a tool’s command isn’t found, run `uv tool update-shell` to update your PATH.
146 | - **Choosing versions:** By default, `uv tool install` and `uvx` use the latest version available. To specify a version, include it in the command (e.g. `uvx package==1.2.0`). Use `--upgrade` to upgrade an installed tool.
147 |
148 | ## Managing Python Versions with uv
149 | uv can manage multiple Python interpreters:
150 | - **List Python versions:**
151 | ```bash
152 | uv python list
153 | ```
154 | This shows installed Python versions as well as available versions. Use `--only-installed` to filter only those already installed.
155 | - **Install a Python version:**
156 | ```bash
157 | uv python install
158 | ```
159 | For example:
160 | ```bash
161 | uv python install 3.10.12
162 | ```
163 | This downloads and installs the specified Python interpreter. You can install multiple versions in one command.
164 | - **Create a venv with a specific Python:**
165 | ```bash
166 | uv venv --python
167 | ```
168 | This creates a new virtual environment in the current directory (by default at `.venv/`) using the specified Python.
169 | - **Run with a specific Python:**
170 | ```bash
171 | uv run --python
172 | ```
173 | For example:
174 | ```bash
175 | uv run --python 3.10.9 python --version
176 | ```
177 | This runs the command using the specified Python interpreter. You can also specify alternative implementations (e.g. `pypy@3.8`).
178 | - **Pin Python version for project:**
179 | ```bash
180 | uv python pin
181 | ```
182 | This writes the version to a local `.python-version` file and updates `requires-python` in `pyproject.toml`.
183 |
184 | ## Updating Dependency Versions (Upgrading Packages)
185 | - **Upgrade all dependencies:**
186 | ```bash
187 | uv lock --upgrade
188 | ```
189 | This updates all dependencies to their latest allowed versions and updates the lockfile. After running it, execute `uv sync` to install the new versions.
190 | - **Upgrade a specific package:**
191 | ```bash
192 | uv lock --upgrade-package
193 | ```
194 | For example:
195 | ```bash
196 | uv lock --upgrade-package django
197 | ```
198 | This updates only the specified package while respecting your version constraints.
199 | - **Apply updated constraints:** If you edit version constraints manually, run:
200 | ```bash
201 | uv lock && uv sync
202 | ```
203 | to update and install changes.
204 | - **Inspect dependency tree:**
205 | ```bash
206 | uv tree
207 | ```
208 | This displays the dependency graph and versions in a tree format.
209 |
210 | ## Advanced Usage Scenarios
211 | - **Dependency Groups:**
212 | uv supports organizing dependencies into groups (e.g., dev, test, docs). For example:
213 | - `uv add --group test pytest` adds **pytest** under a custom group named "test".
214 | - The `dev` group is added by default with `uv add --dev `. Use `uv sync --no-dev` to exclude the dev group in production.
215 | - **Optional Dependencies (Extras):**
216 | Add an extra using `uv add --optional ` (or `-o`) to place it under `[project.optional-dependencies]`. These extras are installed only when requested with `uv sync --extra ` or `--all-extras`.
217 | - **Workspaces (Monorepos):**
218 | uv can handle multi-project repositories via workspaces. Declare multiple projects in one top-level configuration. Dependencies between workspace members are resolved together and share a lockfile. Each workspace member typically gets its own virtual environment, but uv coordinates them.
219 | - **Continuous Integration (CI):**
220 | In CI pipelines, use:
221 | ```bash
222 | uv sync --frozen
223 | ```
224 | to install dependencies exactly as locked. This ensures reproducible builds. You might also pre-install Python with `uv python install ` to ensure consistency.
225 | - **Explicit Virtual Envs:**
226 | uv manages environments automatically (often creating a `.venv` for projects). To explicitly create one, run:
227 | ```bash
228 | uv venv
229 | ```
230 | If you need to remove a cached environment, use `uv cache clean`.
231 | - **Using pip interface:**
232 | uv provides a `uv pip` command that mimics pip. For example, `uv pip install ` lets you use familiar pip commands while leveraging uv’s resolver. This helps integrate uv into existing workflows.
233 |
234 | ## Best Practices for Efficient **uv** Usage
235 | - **Install uv in isolation:** Use pipx or another isolated method to prevent conflicts.
236 | - **Commit your lockfile:** Always check in the `uv.lock` file to version control to ensure reproducibility.
237 | - **Pin Python for projects:** Use `uv python pin` to lock the Python version and avoid “works on my machine” issues.
238 | - **Use `uv run` and `uvx`:** Rely on these commands to execute scripts and tools within the correct environment without manual virtualenv activation.
239 | - **Separate dev dependencies:** Keep development and testing dependencies in their own groups to streamline production environments.
240 | - **Leverage uv’s speed:** uv is designed to add, remove, and upgrade dependencies quickly. Run `uv lock --upgrade` periodically to refresh versions.
241 | - **Stay updated:** Keep uv updated and enable shell tab-completion to improve efficiency.
242 |
243 | ## Troubleshooting Common Issues
244 | - **Dependency resolution errors:** If you see an error like “No solution found when resolving dependencies,” check your version constraints in `pyproject.toml` and update them as needed. Rerun `uv lock` after adjustments.
245 | - **Build failures (C extensions):** For build errors (e.g., missing compiler or headers), ensure you have a C compiler installed (like build-essential on Debian/Ubuntu or Xcode Command Line Tools on macOS) and install any necessary development libraries.
246 | - **Command not found / PATH issues:** If `uv` or an installed tool isn’t recognized, verify that your PATH is set correctly. For uv tools, run `uv tool update-shell` and restart your shell if needed.
247 | - **Python version not available:** If uv cannot find a specified Python version, verify your `.python-version` file and ensure the interpreter is installed using `uv python list --only-installed` or install it with `uv python install `.
248 | - **Cache or environment issues:** If a tool or script isn’t picking up new versions, try running `uv cache clean` to clear uv’s caches and recreate a fresh environment.
249 | - **“Module not found” errors:** Ensure all required dependencies are added via `uv add` and that you are running commands with `uv run` so that the project’s packages are available.
250 | - **Getting help:** Use `uv --help` to view available commands and options. If you encounter bugs or persistent issues, check uv’s official documentation or community forums for assistance.
251 |
252 |
--------------------------------------------------------------------------------
/windows_claude_desktop_config.json:
--------------------------------------------------------------------------------
1 | {
2 | "mcpServers": {
3 | "@automatalabs-mcp-server-playwright": {
4 | "command": "wsl",
5 | "args": [
6 | "~/sandboxes/claude_sandbox.sh",
7 | "claude-desktop",
8 | "npx",
9 | "-y",
10 | "@automatalabs/mcp-server-playwright"
11 | ],
12 | "env": {
13 | "DISPLAY": ":0"
14 | }
15 | },
16 | "sandbox": {
17 | "command": "wsl",
18 | "args": [
19 | "~/sandboxes/claude_sandbox.sh",
20 | "claude-desktop",
21 | "uvx",
22 | "mcp-server-shell @ git+https://github.com/emsi/mcp-server-shell"
23 | ],
24 | "env": {
25 | "DISPLAY": ":0"
26 | }
27 | },
28 | "filesystem": {
29 | "command": "wsl",
30 | "args": [
31 | "~/sandboxes/claude_sandbox.sh",
32 | "claude-desktop",
33 | "npx",
34 | "-y",
35 | "@modelcontextprotocol/server-filesystem",
36 | "/home/agent"
37 | ]
38 | }
39 | }
40 | }
41 |
--------------------------------------------------------------------------------