Projects are for high-level assistance in turning
ideas into actionable next steps. No code is included
as context, instead it provides an isolated
perspective.
Chats are for assistance on specific code-related tasks.
Code is included as context where applicable.
Agents are limited to coding assistance to avoid
cluttering up the UI.
For long-term strategic planning, short-term note taking,
or performance monitoring, use external tools.
Furthermore, feel free to consult a third party chatbot,
a coworker, or a trusted source, to get an additional
opinion on a complex problem.
Agents are purposefully limited to making suggestions.
This allows for the benefits of using AI in coding,
without the loss of oversight. The speed decrease of
copy-and-pasting is largely negligable (if the human
plans and reviews, which might take up >95% of the time
whereas copy and pasting only takes a few seconds)
and can be seen as an excercise to encourage understanding.
Furthermore, output speed is increased if the review fails
and instead of the chaos of reversing an edit and then
making another, one simply request and adjustment in the
chat before manually inserting the new code.
The approach is a coding-first philosophy that targets
complex problems that require critical thinking that
involves understanding technology constraints (not
simple feature-repeating). The focus is on an AI-human
partnership. Outcomes are judged based on what
can be achieved by an expert, not on what the it
enables anyone to replicate.
The target audence involves developers who don't struggle
with coding, and who want to increase
performance (rather than decrease effort required).
Projects are visible to all
employees in the given organisation, however only
top level deployment employees may create new projects
and prompt the project agent.
Chats are employee specific. To see all your chats, log in with
all your employee accounts (e.g. if you have a storage employee acount
and a web app employee account log in to both to see chats related to
agents related to that employee type).
For authorisation, log in on other micro-UIs with the same
email address to receive authorisation in relation to
that micro-UI.
E.g. Log onto the web app editor micro-UI
to access the JS Operation chatbot.
See the landing page to check with which micro-UIs you
are logged in.
For 'full access' (e.g. to create a new project),
you must also log in to top level deployments micro-UI.
Token usage for rate limits is on a rolling 6 hour basis.
Even if you have not hit your limits system-wide limits
may at times result in rate limiting.
Sub-Agent:
The project name can be edited later.
Project Name:
The context title can be edited later.
Context Title:
about
Usage PatternsRate Limit:
Custom Resources
Filter:
| Project | Created By | Created At |
|---|
Filter:
| Title | Sub-Agent | Started At |
|---|